4.1 Compatible · SC 4.1.3

AA2 min read

Status Messages

In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

In plain language

When something on the page changes and a message like "3 items added to cart" or "Your changes were saved" appears, screen readers must announce it automatically, without the user moving focus to find it.

Why it matters

A sighted user notices a confirmation banner or error message as soon as it appears on screen. A screen reader user only hears it if the message is marked up correctly. Otherwise, they can complete an action with no idea whether it worked, failed, or changed anything.

In practice

Fails this criterion

A user submits a form and a green "Your changes were saved" message appears, but it's a plain <div> with no ARIA attributes. A screen reader user who submits the same form hears nothing and can't tell that it succeeded.

Meets this criterion

The same message is placed in a container with role="status" or aria-live="polite". As soon as it appears, the screen reader announces "Your changes were saved" without the user having to look for it.

Test it yourself

Turn on a screen reader and trigger an action that produces a status message: submit a form, add an item to a cart, or apply a filter. Without moving your focus, the screen reader should announce the result automatically. If it stays silent, this criterion is failing.

Read SC 4.1.3 on the official WCAG 2.2 specification ↗