For users who can’t rely on sight, Status Messages ensures these updates are announced by assistive technologies, keeping everyone informed in real-time.
Who this impacts
- Screen reader users: Without coded status messages, screen readers can miss important updates like “Item added to cart” or “Search completed.”
- Users with cognitive impairments: Clear, immediate updates reduce anxiety and help users understand what’s happening on the page.
- Everyone: Feedback like “Item added to cart” or “Payment processed” reassures all users during important interactions.
How to meet Status Messages
- Implement ARIA live regions: Use attributes like aria-live=”polite” or aria-live=”assertive” to announce messages appropriately.
- Update dynamically without focus changes: Ensure status messages are delivered seamlessly without moving the user’s focus.
- Test for assistive technology compatibility: Verify that screen readers and other tools can detect and announce updates correctly.
Practical example
Meowcation’s “Add to Itinerary” feature announces “Activity added to itinerary” both visually and via screen readers, so users never miss an update while planning their dream trip.
Exceptions
Status messages apply only to updates that users need to know. Non-critical updates or purely decorative changes aren’t included.
Top tips
- Use live regions wisely: Tailor aria-live attributes to the urgency of the message—assertive for critical updates, polite for minor ones.
- Make it non-intrusive: Ensure updates don’t disrupt focus or interrupt the user’s workflow.
- Be specific and clear: Status messages should convey exactly what happened, like “3 search results found” instead of just “Done.”
- Test with multiple devices: Ensure status messages work well across different platforms and assistive technologies.