51 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.
- Avoid auditory distractions - For systems with auditory output, people may need to avoid auditory distractions that may prevent them from focusing on a task.
- Avoid cognitive overloads - For system the presents content and other stimuli, people may need to avoid cognitive overloads?
- Avoid interruptions - For systems that include notifications, advertisements, browser pop-ups, or other interruptions to task completion, people may need to avoid the unnecessary interruptions.
- Avoid olfactory distractions - For systems with olfactory output, people may need to avoid olfactory distractions that may prevent them from focusing on a task.
- Avoid tactile distractions - For systems with tactile output, people may need to avoid tactile distractions that may prevent them from focusing on a task.
- Avoid visual distractions - For systems with visual output, people may need to avoid visual distractions that may prevent them from focusing on a task.
- 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.
- Consistent help - For systems that provide help, people may need the help to be in a consistent location and use consistent interactions.
- Consistent identification - For systems that include interactive components, people may need interactive components with the same functionality to be labeled the same.
- Consistent layout - For systems that present content, people may need consistent layouts and hierarchies using familiar conventions.
- Consistent navigation - For systems with interactive components, people may need navigation and interactions to be internally consistent.
- Consistent visual design - For systems with visual content, people may need content that uses consistent and familiar visual conventions.
- Context sensitive help - For systems that provide help, people may need context sensitive help.
- Control distractions - For systems that include notifications or other interruptions to task completion, people may need to control interruptions.
- Familiar icons - For systems with icons, people may need familiar icons or symbols that help them understand meaning.
- Familiar interactions - People may need content and interfaces that follow familiar user interface interaction behavior and feedback conventions.
- Flexible input format - For systems with inputs, people may need inputs to accept different formats.
- 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.
- Hide accessibility features - For systems that provide specific accessibility functions, people may need to temporarily hide them.
- 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.
- Location in Context - People may need their current location within the larger structure to be presented visually and programmatically.
- 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.
- 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.
- Sequence of task steps - For systems used to complete tasks, people may need prompts identifying the appropriate next step to perform for a task.
- 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.
- Turn off tactile output - For systems with tactile output, people may need to turn off the tactile output from a system.
- Unchanging button functionality - For systems that require physical operation, people may need each button or key to have its own functionality rather than functionality that changes depending on context.
- 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.