E-mail List Archives
Re: toast accessibility
From: Ugurcan Kutluoglu
Date: Nov 13, 2017 2:30PM
- Next message: Birkir R. Gunnarsson: "Re: toast accessibility"
- Previous message: Bourne, Sarah (MASSIT): "Re: toast accessibility"
- Next message in Thread: Birkir R. Gunnarsson: "Re: toast accessibility"
- Previous message in Thread: Bourne, Sarah (MASSIT): "Re: toast accessibility"
- View all messages in this Thread
Hi Jennison,
In addition to using an "assertive" live region and the other usual
techniques for screen reader users, we do the following on our toasts.
1- Avoiding using them, if possible. We prefer using an user dismissible
notification bar, with a close button, on top of the page.
2- Using text length for calculating the amount of time the toast remains
on screen. It's currently 3 seconds plus 60 milliseconds per character.
3- Toasts don't disappear if mouse pointer is hovering over them
4- Making sure we are not relying on color to convey different toast
states. i.e Error, Warning and Success toasts have different icons in
addition to different colors.
5- Making sure they have a visible border in Windows High Contrast mode.
6- No toast messages on page load. We wait at least 5 seconds before
showing a toast.
Ugi
On Mon, Nov 13, 2017 at 11:07 AM, Jennison Mark Asuncion <
<EMAIL REMOVED> > wrote:
> I'd like to hear from folks who have created accessible toasts,
> including for but not limited to screen reader users. I'm particularly
> interested in how you've dealt with the practical reality that the
> intent of the toast is to only briefly show a message and then have it
> disappear.
>
> Jennison
> > > > >
- Next message: Birkir R. Gunnarsson: "Re: toast accessibility"
- Previous message: Bourne, Sarah (MASSIT): "Re: toast accessibility"
- Next message in Thread: Birkir R. Gunnarsson: "Re: toast accessibility"
- Previous message in Thread: Bourne, Sarah (MASSIT): "Re: toast accessibility"
- View all messages in this Thread