49 guidance statements support this functional need:
- Adjustable parts - For systems with physical input or output devices, people may need to adjust the location and position of the devices to have all of them within easy view and reach.
- Alternative to holding - For systems that use buttons to input data, people may need an alternative input to holding a button down.
- 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.
- 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
- 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.
- Interface access - For systems used to play games, people may need to access all areas of the interface with the same input method as the gameplay.
- 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.
- 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.
- 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.
- 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.
- Obvious, avoidable hazards - For systems that include hazards, people may need the hazards to be obvious, easy to avoid, and difficult to trigger.
- Pointer errors - For systems that allow pointer input, people may need to correct or undo pointer mistakes.
- 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.
- 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.
- Reconfigure controls - For system that have physical input or output devices, people may need to remap and reconfigure my controls.
- Redundant Entry - For systems that require data input, people may need to avoid entering data more than once.
- Room for use - For stationary or installed systems, people may need adequate room to approach a device that fits them and any assistive technology they use (such as mobility devices).
- 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.
- 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.
- 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.
- 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)
- Within reach - For systems with physical controls, people may need to have all controls and other operable parts located within easy view and reach.