42 guidance statements support this functional need:
- Adaptable captions - As a person who uses captions or subtitles to access spoken content, and who also has moderate visual impairment, I need to be able to customize the presentation of captions and subtitles so I can read them effectively.
- 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.
- Auditory equivalents - For systems with auditory content, people may need that content presented programmatically or need equivalent visual and tactile versions.
- 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.
- 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
- Identify speaker - For systems with auditory content, people may need to easily identify the relationship between caption text and speaker.
- 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.
- 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
- Noticeable non-auditory alert - For systems that present auditory, time-sensitive alerts, people may need the alerts to be in a format that they will notice immediately, such as flashing lights or insistent vibration.
- Notifications in auditory alternatives - For systems that present auditory notifications, people may need visual or tactile equivalents.
- 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.
- 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.
- Sign language characteristics - For systems with sign language, people may need sign language presented with sufficient size, resolution, magnification, speed, and contrast.
- Sign language characteristics - For systems that present auditory content, people may need sign language content in a sign language that they understand.
- Signposts - People may need clear signposts to indicate specific locations where functionalities can be found.
- Speaker location - For a 3D interface like XR with auditory content, people may need to identify where in space the speaker being captioned is located.
- Status indicators - For systems with toggle controls that have states, people may need the state of the system available to them.
- Supplement auditory location cues - For systems that present auditory cues to location in space, people may need the location represented in other forms, such as visual, textual, or haptic cues.
- 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.
- 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 presentation control - For systems that present text, people may need to be able to control the visual presentation of the content including color, orientation, formatting, spacing, justification, and size.