55 guidance statements support this functional need:
- Accessible routes - For stationary or installed systems, people may need tools to provide a route that is accessible to me, or information about barriers on the way.
- 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.
- Audio control - For systems that present auditory content, people must be able to control the content ' s auditory content volume independently from the overall system volume level.
- Avoid interruptions - For systems that include notifications, advertisements, browser pop-ups, or other interruptions to task completion, people may need to avoid the unnecessary interruptions.
- Changing content alternatives - For systems that provide changes in content (including state, role or value), people may need visual, auditory, and tactile indications of the change.
- Changing content programmatic - For systems that provide changes in content (including state, role or value), people may need programmatic indcations of the change.
- Clean accessible name - Relates to interactive equivalent
- Consistent layout - For systems that present content, people may need consistent layouts and hierarchies using familiar conventions.
- Consistent visual design - For systems with visual content, people may need content that uses consistent and familiar visual conventions.
- Control timeout - For systems that time out, people may need to be able to adjust, extend or turn off any time out.
- Description of operable parts layout - For systems that require physical operation, people may need to have the location and arrangement of operable parts given to them.
- Distinguish auditory components - For systems with multiple auditory components or channels (potentially including assistive technology or accessibility features), people may need to clearly perceive and distinguish the various auditory components and not have them interfere with each other.
- 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
- Familiar interactions - People may need content and interfaces that follow familiar user interface interaction behavior and feedback conventions.
- Focus indicators - People may need visible and programmatic focus indicators with high contrast/luminosity against adjacent colors that are not visually obscured by other content.
- 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.
- Language of content - For systems that present language based content, people may need the language of content to be programmatically determinable.
- Meaningful focus order - For systems with interactive components, people may need those components to be available in a meaningful sequence that facilitates operation.
- Meaningful sequence - For systems that present content, people may need the content to be available in a meaningful sequence 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.
- Name, role, value, state - Overlap with programmatic structure and relationships.
- 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.
- No reliance on specific sense to avoid injury - For system the presents content and other stimuli, people may need alternative versions of content that do not rely on a specific sense to avoid injury.
- Nonauditory instruction references - For systems that provide instructions, people may need instructions that reference auditory information to include an additional programmatic reference or provide equivalent visual or tactile references.
- Nonvisual and Auditory Alternate Intruction References - As a user with no vision and no hearing, I need instructions that reference auditory or visual information to include an additional programmatic reference or provide equivalent tactile references
- Nonvisual instruction references - For systems that provide instructions, people may need instructions that reference visual information to include an additional programmatic reference or provide equivalent auditory or tactile references.
- Noticeable non-visual alert - For systems that present visual, time-sensitive alerts, people may need the alerts to be in a format that they will notice immediately, such an auditory alert or insistent vibration.
- Obvious, avoidable hazards - For systems that include hazards, people may need the hazards to be obvious, easy to avoid, and difficult to trigger.
- Output modality choice - As a user with limited or no vision or with limited or no hearing, I need to be able to choose modalities to be used for outputs from the system.
- 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.
- Private data entry - For systems that collect private information, people need positive assurance that sensitive information they enter, such as password or national ID, is not displayed on the screen.
- Programmatic structure and relationships - For systems that present content, people may need structure and relationships (title, labels, section headings) presented sensorily and programmatically.
- 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.
- Select audio stream - For a system with multiple audio streams, people may need to select and deselect different audio streams.
- 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.
- Status indicators - For systems with toggle controls that have states, people may need the state of the system available to them.
- Tactile symbol clarity - As someone who feels tactile symbols, I need to have tactile symbols with an appropriate level of clarity so that I can easily perceive, differentiate, or read them.
- Tactile text speed - As someone who reads tactile text, I need to have tactile text at an appropriate reading speed.
- 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.
- Title - For systems with pages or page-like groups of content, people may need the page or screen to have a visual and programmatic title that describes the purpose of the page.
- Turn off visual output - For systems with visual content, people may need to turn off the visual output from a system.
- Unchanging button functionality - For systems that require physical operation, people may need each button or key to have its own functionality rather than functionality that changes depending on context.
- 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.
- Visual equivalents - For systems with media content, people may need audio descriptions or a text transcript available.