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.
Checklist – Components
Alerts and Messaging
| Test | Priority | Automated test? |
|---|---|---|
| Do status messages representing sequential messages have the aria role=”log” attribute | High | None |
| Do status messages (other than errors) have the role of status? | High | None |
Dialogs
| Test | Priority | Automated test? |
|---|---|---|
| Is the (wizard) back button present and working? | High | None |
Additional resources
- “It’s Alive!”: Apps That Feed Back Accessibly by Heydon Pickering at Smashing Magazine
- How to create a simple CSS loading spinner & make it accessible by Stuart Nelson
- Best practice for animated progress indicators by Nick Babich at Smashing Magazine
- Response Times: The 3 Important Limits by Jakob Nielsen on Nielsen Norman Group