42 guidance statements support this support needed:
- 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.
- 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 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
- Concurrent input - For systems that take input, people may need to use concurrent input mechanisms.
- Distinguish auditory components - People may need to use assistive technology or accessibility features without interference from other devices.
- 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.
- Distinguish tactile components - For systems with multiple tactile components or channels, people may need to be able to clearly perceive and distinguish the various tactile components.
- Distinguish visual components - For systems with multiple visual components, people may need to be able to clearly perceive and distinguish the various visual components and not have them interfere with each other.
- Error identification - For systems with possible errors, people may need errors to be identified sensorily and programmatically.
- 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.
- Keyboard shortcuts - For systems that accept keyboard or voice input, people may need keyboard shortcuts to be predictable and not override existing keyboard shortcuts.
- Keypad entry - For systems that accept input beyond a single yes/no based process, people may need keypad style entry to be available. The type of keypad supported will vary based on functionality.
- Language of content - For systems that present language based content, people may need the language of content to be programmatically determinable.
- Limited vision distinguish distractions - For systems that present content that is not related to a task or from a different source than the main content, people may need the secondary content to be clearly indicated programmatically, visually with high luminosity, or with equivalent auditory and tactile versions.
- Location in Context - People may need their current location within the larger structure to be presented visually and programmatically.
- Magnification - For systems that present visual content, people may need to magnify or resize content.
- Manage individualization functions - For systems with assistive technology built into the platform, people may need a way to perform, undo, and redo individualization actions.
- Meaningful sequence - For systems that present content, people may need the content to be available in a meaningful sequence both sensorily and programmatically.
- Name, role, value, state - Overlap with programmatic structure and relationships.
- No accessibility feature override - For systems with built-in accessibility features to access systems, people may need applications that do not override or defeat those built-in platform features.
- 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.
- 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.
- Nongustatory nonolfactory alternate instruction references - For systems that provide instructions, people may need instructions that reference smell or taste to include an additional programmatic reference or provide equivalent visual, auditory, and tactile references
- Nontactile alternate instruction references - For systems that provide instructions, people may need instructions that reference touch to include an additional programmatic reference or provide equivalent visual or auditory 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.
- Olfactory equivalents - For systems with olfactory or gustatory content, people may need that content presented programmatically or need equivalent visual, auditory, and tactile versions.
- Programmatic structure and relationships - For systems that present content, people may need structure and relationships (title, labels, section headings) presented sensorily and programmatically.
- Reset accessibility functions - For systems with assistive technology built into the platform or that work with assistive technology, people may need a way to reset accessibility functions to their initial states.
- 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.
- Software control - For systems that require physical operation, people may need to access functionality through software that is ordinarily controlled through hardware.
- Speech variations - For voice input systems, people may need the system to recognize input with non-typical speech characteristics, such as from voice production difficulty or a Deaf accent, as well as it does mainstream accents.
- Synchronized captions - For system with auditory content, people may need captions synchronized with the main content.
- 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.
- Visual equivalents - For systems with media content, people may need audio descriptions or a text transcript available.
- Visual/tactile feedback at control location - As a user with a disability who might not be paying attention to other output devices, I need to have visual or tactile feedback occur at the same location as the control I am using.