33 guidance statements support this user need:
- Alternate versions - For systems that present language based content, may need alternative versions of the content (iconography, simplified, summarized, etc.)
- Assistive technology-compatible - For systems with user interfaces, people may need content and operable elements to be accessed and presented through assistive technology.
- Background noise - For systems that present content, people may need to be able to distinguish information in the foreground from background noise (noise which may be of any modality).
- Change to cultural conventions, words, and symbols - For systems that present text and images, people may need to change input and user interface components to use text or symbols with which they familiar.
- 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.
- Clear numbers - For systems that present numeric information, people may need familiar, unambiguous numbers.
- 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 layout - For systems that present content, people may need consistent layouts and hierarchies using familiar conventions.
- Consistent navigation - For systems with interactive components, people may need navigation and interactions to be internally consistent.
- Consistent visual design - For systems with visual content, people may need content that uses consistent and familiar visual conventions.
- 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.
- 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.
- 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 icons - For systems with icons, people may need familiar icons or symbols that help them understand meaning.
- Familiar interactions - People may need content and interfaces that follow familiar user interface interaction behavior and feedback conventions.
- Hide accessibility features - For systems that provide specific accessibility functions, people may need to temporarily hide them.
- Human help - For systems that may require assistance, people may need easy access to trained human help.
- Identify speaker - For systems with auditory content, people may need to easily identify the relationship between caption text and speaker.
- Implied content - For systems that present implied content, people may need explanations for implied information.
- Large scale layout - For systems with large scale display modes, people may need the visual relationship aspects of the layout to be preserved, and content not to be clipped.
- Location in Context - People may need their current location within the larger structure to be presented visually and programmatically.
- Multiple simultaneous modalities - For systems that present information, people may need the information presented simultaneously in multiple preferred modalities (visual and audio; tactile and audio; visual and tactile; or visual, audio, and tactile).
- Non-visual instructions - For systems that prsent visually oriented instructions, people may need non-visual cues as well.
- Number alternatives - For systems that present numbers or numeric content, people may need alternative ways to understand what the numbers mean.
- Plain language - For systems that present language based content, I need a version that follows plain language principles.
- 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.
- Speech with visual highlighting - For systems that provide captions, people may need individual words highlighted synchronously with the text that is being spoken.
- Text spacing - For systems that present text, people may need white space between segments of text.
- Use cultural conventions, words, and symbols - For systems that present text and images, people may need content and interfaces that use standard conventions, words, and symbols for the culture, with which they are familiar.
- 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.