WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: best practice for success notifications?

for

From: Lucy Greco
Date: Aug 10, 2015 1:56PM

hello:
i think having it as a alert is good and also i like including
information in the title of the page. i.e. 10 search results or
registration is complete. at the beginning of the page title. its key that
the user know they did it write and that they here it quickly and some
times the only way to let them know this is by changing the page title. as
that is the first thing herd on reload.
do not remove the message as a user may wish to find it and or copy
that information as a backup to submitting a request. hope this helps
Lucy

On Fri, Aug 7, 2015 at 3:52 PM, Sean Keegan < <EMAIL REMOVED> > wrote:

> 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
> > > > >



--
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces