Success Criterion 4.1.3
Conformance level AA

Single-Page App Route Change With No Announcement at All

4.1.3 — Status Messages

Scenario

Setting

A professional networking site's profile editor

What’s wrong

single-page app route/page change producing no announcement and no focus-management signal that the view changed.

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

Navigate to a new view in a single-page app with a screen reader running: if there's no announcement and no focus-management signal that the page changed, 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 professional networking site's profile editor, 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