• Success Criterion 4.1.3
  • Conformance level AA

Live Region Whose Content Loads Before It’s Ready to Announce

4.1.3 — Status Messages

Scenario

Setting

A used-car marketplace's listing filter

What’s wrong

Live region present but broken: injected with content simultaneously with creation (missed by assistive technology), aria-live (code that makes screen readers announce updates) on element replaced wholesale, or display:none toggling that suppresses announcement.

Example

Open a used-car marketplace's listing filter and this is what you'll see: live region present but broken: injected with content simultaneously with creation (missed by assistive technology), aria-live (code that makes screen readers announce updates) on element replaced wholesale, or display:none toggling that suppresses announcement.

Why it matters

Screen-reader users who need spoken confirmation of saves, errors, and results. On a used-car marketplace's listing filter specifically, they have to work around the barrier just to continue.

How to test

Inspect the live region in DevTools: if content is injected into the element at the same moment the element itself is created, some screen readers miss the announcement — check the region exists in the DOM before content is added.

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

Fixed, a visitor to a used-car marketplace's listing filter can complete the task without extra help.

Who is affected

Screen-reader users who need spoken confirmation of saves, errors, and results.

Learn more

Related scenarios