Should all status updates be an alert?
Question
Answer
A temporary update like “Please wait” or “Processing” informs users of what's currently happening. For these kind of updates, Success Criterion 4.1.3: Status Messages applies and the alert message should be coded so it can be automatically announced by assistive technology.
The intention for this criterion is that users have access to equivalent information. If visual users are informed about a status update, then non-visual users need access to the same update, even if only briefly presented. Status updates like this can be valuable for all users by indicating that the system is working on their request, and not just frozen or nonfunctional.
For a status message that’s not critical, we recommend coding the message as a polite alert (as opposed to an assertive alert). Polite alerts communicate their relative importance to the accessibility tree, and with certain technologies users can modify how polite alerts are announced or even suppress them. Coding the status as a polite alert makes the information available, and users can control how they prefer to receive this type of information.
To learn more about coding accessible alerts, explore the Forms: Labels, Cues, and Errors course from Accessible Web Academy.
Free Tools to Continue Learning
Accessible Web RAMP
Monitor your website and manage your progress towards WCAG conformance.
Accessible Web Academy
Career specific courses to help power up your accessibility knowledge.
Newest Questions
What are some special cases where custom markup is recommended over HTML? Also, how do I know the correct ARIA label if the element is unavailable in HTML?
- aria
- custom widgets
How should third-party accessibility issues be included in Accessibility Conformance Reports (ACRs) or other documentation?
- acces
- accessibility conformance report
- third party
- vpat