- Success Criterion 4.1.3
- Conformance level AA
Quantity Stepper Value Change Never Announced to Screen Readers
4.1.3 — Status Messages
Scenario
Setting
A childcare-booking service's scheduling page
What’s wrong
Quantity stepper / value-adjustment feedback (cart quantity, computed totals reacting to input) not announced.
Example
<div id="cart-status">Item added</div> <!-- silent DOM update -->Why it matters
Screen-reader users who need spoken confirmation of saves, errors, and results.
How to test
Change a quantity stepper (cart quantity, computed total) with a screen reader running: if the updated value 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.
<div id="cart-status" role="status" aria-live="polite">Item added</div>role="status" with aria-live announces the update to screen reader users without moving their focus.
Outcome
On a childcare-booking service's scheduling page, this barrier is gone for screen-reader users who need spoken confirmation of saves, errors — they reach the same outcome without extra effort.
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
- Cart Confirmation Toast With No Live Region Announcement
- 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