
Success criterion 4.1.3 · Level AA
Status Messages

“A little heads-up would be nice, you know! Did my form go through or not?”
Success criterion 4.1.3 · Level AA
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.
Principle 4: Robust · Guideline 4.1: Compatible
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!”