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?”
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!”
Share this with your team
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.