47 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.
- Characters and punctuation - For systems that include language based content, people may need the characters, symbols, and punctuation required to understand ambiguous words and phrases.
- Clear control behavior - For systems that include interactive components, people may need to understand what a control does, how it relates to other content, and how to use it.
- Cognitive tests - For systems used to complete tasks, including authentication, people may need to do so without cognitive tests.
- Consistent help - For systems that provide help, people may need the help to be in a consistent location and use consistent interactions.
- Consistent identification - For systems that include interactive components, people may need interactive components with the same functionality to be labeled the same.
- Consistent navigation - For systems with interactive components, people may need navigation and interactions to be internally consistent.
- Content segments - For systems that present content, people may need content presented in small segments of related content.
- Context sensitive help - For systems that provide help, people may need context sensitive help.
- Control distractions - For systems that include notifications or other interruptions to task completion, people may need to control interruptions.
- 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
- 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.
- Familiar interactions - People may need content and interfaces that follow familiar user interface interaction behavior and feedback conventions.
- Findable - People may need to easily locate interactive components and important content.
- Flexible input format - For systems with inputs, people may need inputs to accept different formats.
- Human help - For systems that may require assistance, people may need easy access to trained human help.
- Location in Context - People may need their current location within the larger structure to be presented visually and programmatically.
- 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 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.
- Non-visual instructions - For systems that prsent visually oriented instructions, people may need non-visual cues as well.
- Obvious, avoidable hazards - For systems that include hazards, people may need the hazards to be obvious, easy to avoid, and difficult to trigger.
- Preparing for tasks - For systems used to complete tasks, people may need to know what they will need to complete each task before they begin.
- 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.
- Redundant Entry - For systems that require data input, people may need to avoid entering data more than once.
- 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.
- Simple login - For systems with a login, people may need a simple way to log in.
- Text spacing - For systems that present text, people may need white space between segments of text.
- Timeout warning - For systems that time out, people may need to be notified when a timeout is about to occur and has occurred.
- 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.
- Unexpected movement - For systems with a visual interface, people may need content and controls to remain in the same relative location and not move unexpectedly.
- Updating content - For systems with automatically updating content, people may need to be able to control it.
- Visual recall - For systems with visual content, people may need time to study visual stimuli that they must later recall, so they can store the relevant information non-visually.
- Visual recognition - For systems with visual content, people may need visual cues that they must recognize, such as icons and logos, to include other ways to distinguish them, such as labels.