Success Criterion 4.1.3
Conformance level AA

Countdown Timer Update Shown Visually but Never Announced

4.1.3 — Status Messages

Scenario

Setting

A budget airline's flight search results

What’s wrong

Countdown/timer status text (resend-one-time password (OTP) timers, session countdowns) updating visually only.

Example

Here's a real case from a budget airline's flight search results: countdown/timer status text (resend-one-time password (OTP) timers, session countdowns) updating visually only.

Why it matters

Screen-reader users who need spoken confirmation of saves, errors, and results. In this case (a budget airline's flight search results), they are excluded from part of the experience.

How to test

Watch a countdown/timer (e.g., resend-OTP, session countdown) with a screen reader running: if the changing time 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 budget airline's flight search results 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)