50 guidance statements support this individual ability:
- Appropriate challenging - For systems used to complete tasks or play games, people may need to set the complexity or difficulty at a level which is challenging and motivating but not discouraging to me.
- 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.
- Avoid excessive vibration - For systems that provide tactile content, people may need to limit the amount of vibration so that it does not interfere with their ability to perceive information.
- 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.
- Cognitive tests - For systems used to complete tasks, including authentication, people may need to do so without cognitive tests.
- Control timeout - For systems that time out, people may need to be able to adjust, extend or turn off any time out.
- 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.
- Goal & value reminder - For systems used to complete tasks, people may need to receive periodic reminders of the goal being worked on and its value.
- Human help - For systems that may require assistance, people may need easy access to trained human help.
- Information on task progress - For systems used to complete tasks, people may need to receive information regarding the progress of completing a task.
- 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.
- 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 organization - For systems that present content, people may need the content organized into logical, cohesive sections both sensorily and programmatically.
- 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.
- Preparing for tasks - For systems used to complete tasks, people may need to know what they will need to complete each task before they begin.
- 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.
- Redundant Entry - For systems that require data input, people may need to avoid entering data more than once.
- 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.
- 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 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 login - For systems with a login, people may need a simple way to log in.
- Successes acknowledged - For systems used to complete tasks, people may need to have even small successes acknowledged to increase self-esteem.
- 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.
- 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.
- 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.
- Unexpected movement - For systems with a visual interface, people may need content and controls to remain in the same relative location and not move unexpectedly.
- 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.
- Without fear of consequences - People may need to be able to use products without the fear of negative consequences if they make mistakes.