Success Criterion 4.1.3
Conformance level AA

Multi-Step Progress Update Never Exposed to Screen Readers

4.1.3 — Status Messages

Scenario

Setting

A coworking-space booking app

What’s wrong

Multi-step progress ("Step 2 of 4 complete") status changes not exposed.

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

Advance a multi-step process ('Step 2 of 4 complete') with a screen reader running: if the step change 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 coworking-space booking app, this barrier is gone for screen-reader users who need spoken confirmation of saves, errors — they can finish what they came here to do.

Who is affected