Marcelo Paiva

All criteriaPresent as slides

A young man in headphones looks away with a doubtful face while the phone in his hand shows a large tick.Meant to show: A young man with dyslexia who has pages read aloud to him, and was never told his form went through

Success criterion 4.1.3

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.

  • Level AA
  • Principle 4: Robust
  • Guideline 4.1: Compatible

In a user’s words

“A little heads-up would be nice, you know! Did my form go through or not?”

Who this helps: Screen reader users, Dyslexia, Cognitive Impairments

What each role can do

Product manager
Incorporate clear status messages for actions taken on the website.
Designer
Design non-intrusive but clear status messages that do not require user interaction to disappear.
Developer
Use ARIA roles to make status messages accessible to assistive technologies.
Tester
Test the accessibility and clarity of status messages with screen readers and other assistive devices.

Once it is fixed

“Now I know what's happening instead of sitting here guessing. You've made my life easier!”

The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 4.1.3 in the W3C quick reference for WCAG 2.2 (opens in a new tab).

Or press the left arrow.

A success criterion

This is one page of a phrase book. It takes one success criterion and tells it from the side of the person it helps.

From top to bottom

  1. At the top, the site header: my name, which goes home, then links to Writing, Work, Signal, Tools and Resume, then Settings, where you choose the drawings, light or dark, and movement.
  2. Links back to all the criteria, and to present this one as slides.
  3. A drawing, the criterion’s number and name, what it requires in one sentence, and its level.
  4. In a user’s words: a quote from the person who meets the barrier.
  5. What each role can do: one task each for the product manager, the designer, the developer and the tester.
  6. Once it is fixed: the same person again.
  7. Share this with your team: post to LinkedIn, download the slides as a PDF, or copy a link.
  8. Some criteria then have a t-shirt to order.
  9. Links to the previous and next criterion. The left and right arrow keys go there too.
  10. At the bottom, the footer: a note on how this site is built, links to Illustrations, Pens, Concepts and Accessibility, this Describe this page button, then GitHub, LinkedIn and email.

What you can do here

Learn what this criterion asks, and what your part of the fix is.

Also here

The quotes are written to illustrate the criterion. They are not from real people.