Published October 30, 2026

WCAG 4.1.3 Status Messages, Level AA

Does WCAG require status messages to be announced?

Yes at Level AA. Success criterion 4.1.3 Status Messages requires that status messages in content be programmatically determinable through role or properties so that assistive technology can present them to the user without receiving focus. A toast that says “Saved,” a live “Searching…,” or “3 results found” that only changes on screen fails if nothing in the accessibility tree marks it as a status. The text is in the W3C WCAG 2.2 Recommendation.

What counts as a status message?

Content that provides information on the success or results of an action, on the waiting state of an application, on the progress of a process, or on the existence of errors, and that is not delivered through a change of context. The W3C explanation is in Understanding Success Criterion 4.1.3. Common patterns use role="status", role="alert", or an aria-live region. How accessible names are built for controls is on the accessible names page. Error text that also relies on color alone is a separate check on the use of color page.

Do status messages have to move keyboard focus?

No. 4.1.3 is about presenting the message without moving focus. Moving focus into an error summary can still help keyboard users find the problem fields, but that pattern is not what 4.1.3 requires by itself. Labels and instructions that stay visible while someone fills a form are covered under 3.3.2 on the accessible forms page.

Does the Title II web rule include status messages?

Yes. The Department of Justice rule for state and local government websites names WCAG 2.1 Level AA. Criterion 4.1.3 was added in WCAG 2.1, so Title II includes Status Messages. Governments with a population of 50,000 or more have until April 26, 2027. Smaller governments and special districts have until April 26, 2028. Who must comply is on the Title II web rule page. The version comparison is on the WCAG 2.1 vs 2.2 page.

How do you check status messages?

Trigger a save, search, or validation error with a screen reader running and listen for the message without tabbing to it. A scanner can sometimes flag a missing live region. It often cannot tell that a visual toast is the only cue. A person has to hear it, which is why a passing score is not conformance, as covered on the scanner page. The fix belongs in the templates, which is remediation.