22 guidance statements support this individual 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.
- 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 features - For systems with assistive technology built into the platform, people may need a way to activate or deactivate individualization features.
- Manage individualization functions - For systems with assistive technology built into the platform, people may need a way to perform, undo, and redo individualization actions.
- 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.
- 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.
- 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 login - For systems with a login, people may need a simple way to log in.
- 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.