18 guidance statements support this required ability:
- Control timeout - For systems that time out, people may need to be able to adjust, extend or turn off any time out.
- Distinguish auditory components - People may need to use assistive technology or accessibility features without interference from other devices.
- Distinguish if actionable - For systems that include static and interactive components, people may need interactive components to be clearly distinguishable visually and programmatically from static content.
- Encouragement on task progress - For systems used to complete tasks, people may need to receive encouragement that the I am progressing with a task.
- Equivalent privacy control - For systems that collect private information, people with disabilities may need the system to maintain my privacy and provide them the same amount of control of their personal information/privacy as other users.
- Error identification - For systems with possible errors, people may need errors to be identified sensorily and programmatically.
- Error prevention - For systems with possible errors, people may need submissions to be checked, confirmable or reversible
- Error suggestion - For systems with detectable errors, people may need error messages to suggest corrections or state that the system is at fault and the user is unable to fix the error.
- Findable - People may need to easily locate interactive components and important content.
- Meaningful organization - For systems that present content, people may need the content organized into logical, cohesive sections both sensorily and programmatically.
- Multiple Paths - People may need multiple paths through content with unnecessary distractions and interactions.
- Mute all audio - For systems with audio output, people may need the ability to silence or mute all audio output.
- No accessibility feature override - For systems with built-in accessibility features to access systems, people may need applications that do not override or defeat those built-in platform features.
- No navigation traps - For systems with interactive components, people may need to move to and away from any interactive element using any user agent or input modality.
- Obvious, avoidable hazards - For systems that include hazards, people may need the hazards to be obvious, easy to avoid, and difficult to trigger.
- Personalized Interface - People may need to be able to customize their interface.
- Privacy protection - For systems that collect private information, people with disabilities may need the system to protect their privacy, even when they are not doing things that other users might be expected to do to guard their own privacy.
- Recognizable signals - For systems that provide alerts, people may need recognizable signals (including feedback and cues) for different alerts or other messages that use signals.