Status Messages
Summary:
WCAG 4.1.3, "Status Messages," is about ensuring that status messages on websites can be programmatically determined without receiving focus, so they are accessible to users with screen readers or other assistive technologies. This guideline is crucial for users with visual impairments or cognitive disabilities.
What:
The guideline requires that status messages, such as success notifications, error messages, or progress updates, can be conveyed to users through assistive technologies without needing to move focus to those messages.
Why:
Screen reader and assistive technology users often rely on these technologies to interpret on-screen information. Status messages that are programmatically determined allow these users to receive important updates and notifications without disruption in their navigation.
Examples and Scenarios:
- Form Submission Feedback: Communicating a successful submission or error message without shifting user focus from the form.
- Loading Notifications: Announcing the loading status of content or processes in the background.
- Shopping Cart Updates: Alerting users when an item is added to the shopping cart without moving focus from the current browsing area.
How to Comply:
- Websites: Implement ARIA (Accessible Rich Internet Applications) roles and properties to define status messages so they are announced by screen readers.
- Mobile Apps: Ensure status updates within apps are accessible to assistive technologies.
- Software Applications: Similar to web content, make status messages in software accessible without requiring focus changes.
Exceptions:
- Minimal Impact Messages: Brief, non-essential messages that don't significantly impact the user's workflow might not need to be programmatically determined.
- Complex Application Interfaces: In some advanced applications, real-time status messages might be challenging to convey without focus changes due to technical constraints.