- Success Criterion 4.1.3
- Conformance level AA
Cart Confirmation Toast With No Live Region Announcement
4.1.3 — Status Messages
Scenario
Setting
A video-conferencing app's meeting controls
What’s wrong
"Item added to cart" toast rendered with no role="status" (code that makes updates announced)/aria-live (code that makes screen readers announce updates) — screen reader users never informed.
Example
A video-conferencing app's meeting controls runs into this exact issue: "Item added to cart" toast rendered with no role="status" (code that makes updates announced)/aria-live (code that makes screen readers announce updates) — screen reader users never informed.
Why it matters
Screen-reader users who need spoken confirmation of saves, errors, and results. In this case (a video-conferencing app's meeting controls), they are excluded from part of the experience.
How to test
Add an item to the cart with a screen reader running, without looking at the screen: if the 'Added to cart' toast isn't announced, it fails.
How to fix
The status text must be wired as a live region (code that makes screen readers announce updates)/status role so screen readers announce it automatically without moving focus.
Outcome
Once corrected, a video-conferencing app's meeting controls lets them get the same outcome as everyone else.
Who is affected
Screen-reader users who need spoken confirmation of saves, errors, and results.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Status Update Shown Visually but Never Wired for Screen Readers
- Search Result Count That Updates Silently on Every Filter
- Autosave ‘Saved’ Indicator With No Live Announcement
- Loading Spinner With No Programmatic Busy or Status State
- Error Toast With No Alert Role and No Focus Movement
- Live Region Whose Content Loads Before It’s Ready to Announce