WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: UI toasts, notifications and conforming to time limits (2.2.1)

for

From: Jonathan Avila
Date: Jul 11, 2018 9:38AM

Matt, giving the user the option to keep them up or disappear on their own, prevent them from appearing, and the duration of appearance are likely preferences/personalization that you will want to build into the settings for your app. No one method will work best for all people.

Jonathan

Jonathan Avila
Chief Accessibility Officer
Level Access
<EMAIL REMOVED>
703.637.8957 office

Visit us online:
Website | Twitter | Facebook | LinkedIn | Blog

Looking to boost your accessibility knowledge? Check out our free webinars!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Matt Gregg
Sent: Wednesday, July 11, 2018 11:34 AM
To: <EMAIL REMOVED>
Subject: [WebAIM] UI toasts, notifications and conforming to time limits (2.2.1)

Many design systems for web applications (e.g., Google's Material, Salesforce Lightning, IBM's Carbon) include UI components such as toasts or notifications that are configured to disappear after a period of time (typically 3-10 second range). My interpretation of success criteria 2.2.1 would be that these would fail and thus wouldn't conform to WCAG 2.0 in use. The content of the message could disappear before someone could read it for a variety of circumstances. 

https://www.linkedin.com/redir/redirect?url=https://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-required-behaviors.html&urlhash=qEiL&_t=tracking_anet

A similar topic had been discussed previously in a list thread https://webaim.org/discussion/mail_thread?thread„68
It lists out some criteria for toasts which includes having them disappear after a time duration as well.

I'm wondering if there is some other interpretation or way to consider this success criteria that I'm missing where these disappearing messages would conform and be highly accessible to the all users? Or, is this scenario not covered by this success criteria for some reason? 

We're working on a design system and have been discussing if we should include this capability for these type of components to disappear after a time period or only support a user having to dismiss them explicitly. 

Thanks,
Matt




Matt Gregg
Manager, User Experience

Blackbaud, Inc.
2000 Daniel Island Drive, Charleston, SC 29492
Phone: 843.654.2979
<EMAIL REMOVED> | blackbaud.com <http://www.blackbaud.com>;