WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: toast accessibility

for

From: Karl Brown
Date: Nov 14, 2017 3:51AM

https://ux.stackexchange.com/questions/11998/what-is-a-toast-notification

And here I was thinking toast was something I had for breakfast :-/

On Tue, Nov 14, 2017 at 10:29 AM, John Hicks < <EMAIL REMOVED> > wrote:

> The totp crowd were really grooving to that one !
>
>
>
> 2017-11-14 1:14 GMT+01:00 Steve Green < <EMAIL REMOVED> >:
>
> > This song about toast was a UK top 20 chart hit in 1978. They don't make
> > them like this anymore, which is perhaps no bad thing.
> >
> > https://www.youtube.com/watch?v=WJmKStqugMc
> >
> > Steve Green
> >
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> > Behalf Of Birkir R. Gunnarsson
> > Sent: 13 November 2017 22:15
> > To: WebAIM Discussion List < <EMAIL REMOVED> >
> > Subject: Re: [WebAIM] toast accessibility
> >
> > 1. Entirely unrelated to accessibility, but this song about toast has
> been
> > a household favorite for years:
> > https://www.youtube.com/watch?v=SHptn_3RyYE
> > 2. Could you create an example of the type of goast messages you describe
> > (or are they accessible on a public facing site you are working on)?
> Short
> > of not using toasts at all, your list looks really good (it looks like
> you
> > guys took care of all the accessibility implications).
> >
> >
> >
> > On 11/13/17, Ugurcan Kutluoglu < <EMAIL REMOVED> > wrote:
> > > 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
> > >> > > >> > > >> archives at http://webaim.org/discussion/archives
> > >> > > >>
> > > > > > > > > archives at http://webaim.org/discussion/archives
> > > > > >
> >
> >
> > --
> > Work hard. Have fun. Make history.
> > > > > > at http://webaim.org/discussion/archives
> > > > > > > > > > > >
> > > > >



--
Karl Brown
Twitter: @kbdevelops
Skype: kbdevelopment

Professional Certificate Web Accessibility Compliance (Distinction),
University of South Australia, 2015