23 guidance statements support this functional need:
- Appropriate safety level - People may need the system to provide an appropriate level of safety (including physical safety, and safety of my data, finances, legally, etc.).
- Assistive technology-compatible - For systems with user interfaces, people may need content and operable elements to be accessed and presented through assistive technology.
- Control timeout - For systems that time out, people may need to be able to adjust, extend or turn off any time out.
- 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.
- 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
- Input modality choice - For systems that accept input, people may need to be able to choose modalities to be used for inputs to the system.
- 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 disruption when activating access feature - People may need to be able to activate their desired modality without a serious disruption such as restarting the computer, closing and restarting an app, or leaving an active task in progress.
- Obvious, avoidable hazards - For systems that include hazards, people may need the hazards to be obvious, easy to avoid, and difficult to trigger.
- 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.
- Recognize human - For systems that use biometrics, people may need human-detection tools that recognize that people who do not look like everyone else are human and are present with equal reliability, for purpose of obstacle avoidance, non-bot verification, etc. This includes tools operated by other people.
- Recognize individual - For systems that use biometric verification tools such as facial appearance, iris pattern, or finger presence, people with atypical biometric factors may need ways to verify their identity with equal reliability to other people.
- Safe without reliance on alerts - For systems that present alerts, people may need to use the system safely even if I miss an alert or hazard warning.
- Separate output control - For systems with assistive technology built into the platform or that work with assistive technology, people may need to be able to control output of assistive technology separate from output of content.
- Signposts - People may need clear signposts to indicate specific locations where functionalities can be found.
- Timing - People may need no time limit on systems OR for systems that time out, people may need to continue their task without data loss when they log back in after time out occurs.
- Unexpected change of context - For systems with interactive components, people may need to be able to input content without unexpected changes in context.
- Unexpected change of focus - For systems with interactive components, people may need to focus on an element without unexpected changes in context.
- Updating content - For systems with automatically updating content, people may need to be able to control it.