How accessible is your website?Start free check
WCAG 4.1.3Level AARobust

Status Messages: Announce Updates Without Focus

Also called: Status updates, Live announcements, Toast messages

Definition

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 (Level AA, 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"

The criterion mainly helps blind and low vision people using a screen reader. W3C also notes that assistive technologies for some cognitive disabilities can use these roles to delay or suppress messages.

Examples

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.

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.

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

    What is a status message in WCAG?

    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.

    What is the difference between role="status" and role="alert"?

    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.

    Do error messages count as status messages?

    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.

    Why does my screen reader not read the toast?

    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.

    Is WCAG 4.1.3 part of the European Accessibility Act?

    The European Accessibility Act 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.

    • ARIA Live Regions: Announce Status Messages

      An ARIA live region is a part of the page marked with aria-live or a live role such as status or alert. When its content changes, screen readers announce the new text without the user having to move focus to it.

      Read definition: ARIA Live Regions: Announce Status Messages
    • Screen Reader: How It Reads Websites and What It Needs

      A screen reader is assistive software that reads the content and controls of a screen aloud or outputs them on a braille display. It relies on the names, roles and states that a website exposes through the browser's accessibility tree.

      Read definition: Screen Reader: How It Reads Websites and What It Needs
    • Error Identification: Clear Form Error Messages

      Error identification means that when a website detects an input error automatically, it points out the field in error and describes the problem to the user in text. It is required by WCAG 3.3.1 at Level A.

      Read definition: Error Identification: Clear Form Error Messages
    • Error Prevention: Safe Orders, Payments and Data

      Error prevention means that pages which create legal commitments or financial transactions, change or delete user data, or submit test answers give users a safety net: the submission is reversible, checked for errors, or can be reviewed and confirmed first. WCAG 3.3.4 requires it at Level AA.

      Read definition: Error Prevention: Safe Orders, Payments and Data

    Let AI Handle Website Accessibility

    Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

    1. 1Choose your plan
    2. 2Install in 2 min
    3. 3AI fixes your website
    4. Done