Accessible Toast Messages: What Developers and Designers Need to Know | Webinar Video
Toast messages are built to stay out of the way. They slide in to confirm that your changes saved or your message sent, then disappear a few seconds later. For a sighted mouse user, that usually works. For screen reader users, a toast that’s never announced gives them no feedback at all, and for anyone who needs more time to read, a message that vanishes after three seconds is gone before it’s useful.
Kelsie Cleboski, CPWA (Certified Professional in Web Accessibility), sees these issues come up in real projects. As a Senior Digital Accessibility Specialist at Accessible Web, she works with teams on the small interface patterns that look fine in a design file but break down for people using assistive technology, keyboard navigation, or screen magnification. Toast messages are one of the most common.
What we’ll cover:
- Why toast messages so often fail accessibility checks, even when they look polished
- How to announce toasts to screen reader users with ARIA live regions and the status and alert roles, without pulling keyboard focus away from the user’s task
- Timing: how long a toast should stay visible, and when users need a way to pause or dismiss it
- What Web Content Accessibility Guidelines (WCAG) say, including 4.1.3 Status Messages and 2.2.1 Timing Adjustable
- When a toast is the wrong choice, such as error messages or anything the user has to act on
Recording
Watch on YouTube for the full transcript.
Webinar Q&A
-
If you use toast messages, treat them as a supplement to your main way of delivering notifications. Users get notifications and information more reliably from something permanent that lives in a consistent place, such as an inbox, a notification log, or inline messaging. Building that in from the start also prevents some of the barriers toasts can create.
-
The right amount of time depends on users’ needs and preferences. If a toast disappears on its own and it’s the only way users can get that information or complete that action, it has to meet WCAG 2.2.1 Timing Adjustable. That means at least one of these must be true:
- Turn off: Users can turn off the time limit before they encounter it.
- Adjust: Before they encounter it, users can adjust the time limit to at least 10 times the default. For example, a 3-second toast needs to be adjustable to at least 30 seconds.
- Extend: Users are warned before time runs out, get at least 20 seconds to extend it with a simple action, and can extend it at least 10 times.
Even 30 seconds isn’t long enough for some people. Those numbers are averages and estimates. The time someone needs to work with content is very individual, so the answer can’t come from a designer’s opinion, an accessibility reviewer’s opinion, or even general user testing. I recommend giving users control so they can use the amount of time that works for them, rather than trying to find the best time for a toast to disappear.
That control matters most in complex interfaces and in apps people use regularly. Letting users customize the timing makes the experience more efficient and reduces cognitive load.
Read the full requirements and exceptions in Understanding Success Criterion 2.2.1: Timing Adjustable.
-
My general advice is that inline error messages are better than toast messages. They’re simpler for users and easier to implement. Inline messages also avoid two common barriers that toast messages create: they don’t disappear on their own, and they don’t cover other content. The message sits with the existing content, and the content around it shifts to make room. Without those barriers, users also get a simpler experience.
As a user, I find it much more efficient when an error message sits right next to the task I’m working on. I spend less time moving around the page trying to find it.
One requirement applies no matter where the error appears, whether that’s a toast, an inline message, or a summary: screen reader users need to hear the message announced without their focus moving. That’s required by WCAG 4.1.3 Status Messages. We have other webinars about error messages that cover this in more detail.