# Status Messages: Announce Updates Without Focus

Source: https://allyway.ai/glossary/status-messages

Status messages are changes in content that tell users about the result of an action, a waiting state, the progress of a process or the existence of errors, without changing the context. WCAG 4.1.3 requires that they can be programmatically determined, so assistive technologies can present them without giving them focus.

Status messages are the short updates a page shows after something happens: "5 results returned", "Added to cart", "Your form was submitted". Sighted users see them pop up; screen reader users only hear them if the page marks them up correctly. Otherwise the message appears silently and the person is left wondering whether the click worked.

## What it means

[WCAG 4.1.3 Status Messages](https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html) (Level AA, [WCAG 2.2](https://allyway.ai/regulations/wcag-2-2)) requires that in content implemented using markup languages, status messages can be programmatically determined through role or properties, so that they can be presented to the user by assistive technologies without receiving focus.

W3C defines a status message as a change in content that is not a change of context and that informs the user about the success or results of an action, the waiting state of an application, the progress of a process, or the existence of errors. A dialog that receives focus or a new page is a change of context – and therefore not covered.

| Type of message | Example | Suitable ARIA |
|---|---|---|
| Result or success | "5 results returned", "Saved" | `role="status"` (ARIA22) |
| Error or warning | "3 fields need your attention" | `role="alert"` or a live region (ARIA19) |
| Sequential updates | Chat history, activity feed | `role="log"` (ARIA23) |
| Progress | "Upload 60 % complete" | Live region for the progress bar (ARIA25) |
| Waiting state | "Application busy" | `role="status"` |

> **Tip:** > **Polite by default**
> `role="status"` is announced when the screen reader is idle. Keep `role="alert"` for important, time-sensitive messages – W3C lists using it on unimportant content as a failure.

The criterion mainly helps blind and low vision people using a [screen reader](https://allyway.ai/glossary/screen-reader). W3C also notes that assistive technologies for some cognitive disabilities can use these roles to delay or suppress messages.

## Examples

```html title="Example"
<!-- The container exists when the page loads, empty -->
<div role="status" id="search-status"></div>

<script>
  // After filtering, only the text changes
  document.getElementById('search-status').textContent = '5 results returned';
</script>
```

The empty container is in the page from the start, and only its text changes. Many screen readers ignore a live region that is inserted together with its message. The basics of `aria-live` are explained in the entry on [ARIA live regions](https://allyway.ai/glossary/aria-live).

**Do:** Do

Put the message in a `role="status"` container that exists before it changes, keep the text short and complete ("Item added to cart"), and use `role="alert"` only for errors that need attention now, together with clear [error identification](https://allyway.ai/glossary/error-identification).

**Don't:** Don't

Show a toast that disappears without any role, move focus to every "Saved" message, mark the whole results list as a live region, or use `aria-live="assertive"` for minor news.

## How to check status messages



## Questions

Q: What is a status message in WCAG?
A: A change in content that tells the user about the success or result of an action, a waiting state, the progress of a process or the existence of errors – without changing the context, such as moving focus or opening a new window.

Q: What is the difference between role="status" and role="alert"?
A: `role="status"` is polite: the screen reader announces it when it has finished speaking. `role="alert"` is assertive and interrupts. Use alert only for important, time-sensitive information, such as an error that blocks the next step.

Q: Do error messages count as status messages?
A: Yes, if they appear without moving focus, for example "3 fields need your attention" above a form. An error shown in a dialog that receives focus is a change of context and not covered by 4.1.3.

Q: Why does my screen reader not read the toast?
A: Usually the live region is added to the page together with the message, or the toast has no role at all. Keep an empty `role="status"` container in the page and only change its text.

Q: Is WCAG 4.1.3 part of the European Accessibility Act?
A: The [European Accessibility Act](https://allyway.ai/regulations/eaa) points to EN 301 549, which takes over WCAG 2.1 Level AA for the web, including 4.1.3 as clause 9.4.1.3.
