Accommodation type: Default

92 guidance statements support this accommodation type:

• Accessible routes - For stationary or installed systems, people may need tools to provide a route that is accessible to me, or information about barriers on the way.
• 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.).
• Background noise - For systems that present content, people may need to be able to distinguish information in the foreground from background noise (noise which may be of any modality).
• Characters and punctuation - For systems that include language based content, people may need the characters, symbols, and punctuation required to understand ambiguous words and phrases.
• 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.
• Clear numbers - For systems that present numeric information, people may need familiar, unambiguous numbers.
• 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.
• Content segments - For systems that present content, people may need content presented in small segments of related content.
• Context sensitive help - For systems that provide help, people may need context sensitive help.
• Cool down - For systems that take input, people may need a .05 second period between inputs.
• Default fonts - For systems that present text, people may need text to be written using a font and style that supports readability (example: avoids all caps, italics, and very light weights).
• Description of operable parts layout - For systems that require physical operation, people may need to have the location and arrangement of operable parts given to them.
• Distinguish auditory components - For systems with multiple auditory components or channels (potentially including assistive technology or accessibility features), people may need to clearly perceive and distinguish the various auditory components and not have them interfere with each other.
• 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.
• Distinguish tactile components - For systems with multiple tactile components or channels, people may need to be able to clearly perceive and distinguish the various tactile components.
• Distinguish visual components - For systems with multiple visual components, people may need to be able to clearly perceive and distinguish the various visual components and not have them interfere with each other.
• Emotional coping - For systems with triggering content, people may need to to have assistance in coping with my emotional reactions to using the system.
• 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 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.
• 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.
• Findable - People may need to easily locate interactive components and important content.
• Flexible input format - For systems with inputs, people may need inputs to accept different formats.
• 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.
• 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.
• Hover content - For systems that present hover content, people may need hover content to be dismissible, hoverable, and persistent.
• Identify speaker - For systems with auditory content, people may need to easily identify the relationship between caption text and speaker.
• Implied content - For systems that present implied content, people may need explanations for implied information.
• Information on task progress - For systems used to complete tasks, people may need to receive information regarding the progress of completing a task.
• 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.
• Location in Context - People may need their current location within the larger structure to be presented visually and programmatically.
• 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.
• Modified motion-based input - For systems that uses motion based input tools, people may need reduced or slowed motion and rest breaks.
• Multi-frequency events - For systems that present audio alerts and other events, people may need them presented in multiple frequencies, including frequencies where their hearing may be better.
• Multiple Paths - People may need multiple paths through content with unnecessary distractions and interactions.
• 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.
• No tone differentiation - For systems that present audio alerts, notifications, and other events, people may need characteristics other than tone differentiation to distinguish between different audio events or obtain information from such audio events.
• Nontext contrast - For systems that present visual interface components and graphical objects, people may need these to have sufficient contrast with adjacent colors.
• Not cause fatigue or discomfort - People may need systems that do not cause fatigue or discomfort when used.
• Physical approach - For stationary or installed systems, people may need an accessible path of approach that fits them and any assistive technology they use use (such as mobility devices).
• Plain language - For systems that present language based content, I need a version that follows plain language principles.
• 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.
• 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.
• Private data entry - For systems that collect private information, people need positive assurance that sensitive information they enter, such as password or national ID, is not displayed on the screen.
• 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.
• 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.
• Scrolling - For systems that present enough content to go outside the viewport, people may need scrolling limited to a single direction.
• Select audio stream - For a system with multiple audio streams, people may need to select and deselect different audio streams.
• Sequence of task steps - For systems used to complete tasks, people may need prompts identifying the appropriate next step to perform for a task.
• Sign language characteristics - For systems with sign language, people may need sign language presented with sufficient size, resolution, magnification, speed, and contrast.
• Sign language characteristics - For systems that present auditory content, people may need sign language content in a sign language that they understand.
• 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 login - For systems with a login, people may need a simple way to log in.
• Speaker location - For a 3D interface like XR with auditory content, people may need to identify where in space the speaker being captioned is located.
• Speech variations - For voice input systems, people may need the system to recognize input with non-typical speech characteristics, such as from voice production difficulty or a Deaf accent, as well as it does mainstream accents.
• Speech with visual highlighting - For systems that provide captions, people may need individual words highlighted synchronously with the text that is being spoken.
• Status indicators - For systems with toggle controls that have states, people may need the state of the system available to them.
• Successes acknowledged - For systems used to complete tasks, people may need to have even small successes acknowledged to increase self-esteem.
• Target size - For systems with pointer inputs, people may need target sizes large enough to easily hit.
• Text alignment - For systems with text, I need text not to be set to full justify.
• Text contrast - For systems that present text, people may need text to have sufficient contrast with its background.
• Text spacing - For systems that present text, people may need white space between segments of text.
• 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.
• 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 movement - For systems with a visual interface, people may need content and controls to remain in the same relative location and not move unexpectedly.
• Use cultural conventions, words, and symbols - For systems that present text and images, people may need content and interfaces that use standard conventions, words, and symbols for the culture, with which they are familiar.
• User feedback - People may need an accessible way to provide user feedback.
• Visual recall - For systems with visual content, people may need time to study visual stimuli that they must later recall, so they can store the relevant information non-visually.
• Visual recognition - For systems with visual content, people may need visual cues that they must recognize, such as icons and logos, to include other ways to distinguish them, such as labels.
• 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.
• Within viewing range - For systems with physical output devices, people may need to have information and controls within their viewing range.
• Without fear of consequences - People may need to be able to use products without the fear of negative consequences if they make mistakes.