60 guidance statements support this required ability:
- 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.
- Concurrent input - For systems that take input, people may need to use concurrent input mechanisms.
- Control sensitivity - For systems that require physical operation, people may need to be able to adjust the sensitivity of controls.
- Control timeout - For systems that time out, people may need to be able to adjust, extend or turn off any time out.
- Cool down - For systems that take input, people may need a .05 second period between inputs.
- Distinguish auditory components - People may need to use assistive technology or accessibility features without interference from other devices.
- 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.
- Encouragement on task progress - For systems used to complete tasks, people may need to receive encouragement that the I am progressing with a task.
- 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.
- Findable - People may need to easily locate interactive components and important content.
- 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.
- Game speed - For system used to play games, people may need to be able to adjust the speed of game play.
- 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 commands displayed - For systems that accept keyboard input, people may need the available keyboard commands clearly displayed.
- 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.
- 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 focus order - For systems with interactive components, people may need those components to be available in a meaningful sequence that facilitates operation.
- Meaningful organization - For systems that present content, people may need the content organized into logical, cohesive sections both sensorily and programmatically.
- Meaningful sequence - For systems that present content, people may need the content to be available in a meaningful sequence both sensorily and programmatically.
- Motion errors - For systems that use motion based input, people may need to turn it off.
- Multiple Paths - People may need multiple paths through content with unnecessary distractions and interactions.
- 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).
- Mute all audio - For systems with audio output, people may need the ability to silence or mute all audio output.
- 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.
- No navigation traps - For systems with interactive components, people may need to move to and away from any interactive element using any user agent or input modality.
- Obvious, avoidable hazards - For systems that include hazards, people may need the hazards to be obvious, easy to avoid, and difficult to trigger.
- Personalized Interface - People may need to be able to customize their interface.
- Pointer errors - For systems that allow pointer input, people may need to correct or undo pointer mistakes.
- Precise timing - For systems that support task completion or game play, people may need actions that do not require precise timing, can be carried out while paused, or skipped.
- 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.
- 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.
- Redundant Entry - For systems that require data input, people may need to avoid entering data more than once.
- Repetitive strain injuries - For systems that require that involve extensive repetitive actions for input, people may need alternate input devices or approaches.
- 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 identification & activation - For system with interactive components, people may need to have separate means of identifying and then activating controls.
- 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.
- Separate selection & activation - For system with interactive components, people may need to have separate means of selecting and then activating controls.
- Signposts - People may need clear signposts to indicate specific locations where functionalities can be found.
- Simple controls - For systems with input controls, people may need those controls to be simple.
- Simple controls - For systems with complex input controls, people may need simple alternatives.
- Single action - For systems that use fine motor control based input, some users may need an alternative input mechanism that requires only a single action and a single pointer to input information and navigate (alternative to multi-point gestures, dragging, pointer movements, etc)
- Software control - For systems that require physical operation, people may need to access functionality through software that is ordinarily controlled through hardware.
- Stop moving targets - For systems with interactive elements that require accuracy, people may need to stop interactive elements from moving.
- Target size - For systems with pointer inputs, people may need target sizes large enough to easily hit.
- 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.
- Updating content - For systems with automatically updating content, people may need to be able to control it.
- User feedback - People may need an accessible way to provide user feedback.
- Voice commands displayed - For systems with dictation and voice commands, people may need to have available voice commands clearly displayed.
- Voice input errors - For systems with dictation and voice commands, people may need to minimize mistakes that occur because of mistaken speech (e.g. operations are tied to a single letter shortcut)
- Without fear of consequences - People may need to be able to use products without the fear of negative consequences if they make mistakes.