E-mail List Archives
best practice for success notifications?
From: Sean Keegan
Date: Aug 7, 2015 4:52PM
- Next message: Maxability Accessibility for all: "Developers don't detect my screen reader"
- Previous message: Birkir R. Gunnarsson: "Re: tabpanel mark-up, possible effect of role=presentation"
- Next message in Thread: Lucy Greco: "Re: best practice for success notifications?"
- Previous message in Thread: None
- View all messages in this Thread
I am interested in what others identify as best practice as related to
success notifications. I have found a lot of information on error
notifications, but less about what should be part of an accessible success
message.
What are some features you feel should be part of an accessible success
message? Should success messages:
- use aria-live=polite or be treated as more of an alert (e.g, role=alert)?
- use a "close" icon, such as an X (with an appropriate aria-label) to
dismiss the message or have the message automatically fade after displaying
for several seconds?
- include a heading as part of the message?
- have focus set to the message region (i.e., use tabindex=-1)?
Granted, context is important and so some of these may/may not be
appropriate depending on the exact situation. Just looking for general best
practices.
Thanks,
sean
- Next message: Maxability Accessibility for all: "Developers don't detect my screen reader"
- Previous message: Birkir R. Gunnarsson: "Re: tabpanel mark-up, possible effect of role=presentation"
- Next message in Thread: Lucy Greco: "Re: best practice for success notifications?"
- Previous message in Thread: None
- View all messages in this Thread