Required ability: Visual

87 guidance statements support this required ability:

• 2D alternative to 3D - For systems that provide three dimensional content, people may need three dimensional visual information presented using only two dimensions.
• 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.
• Alternative to visual alerts - For systems that provide visual alerts regarding critically important information, people may need to receive auditory or tactile alerts instead.
• Appropriate brightness - For systems that present visual content, people may need to change the brightness based on the viewing environment and situation.
• 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.).
• Appropriate speed - For systems that present dynamic images, people may need adjust the presentation speed to enable them to perceive and track them.
• Assistive technology-compatible - For systems with user interfaces, people may need content and operable elements to be accessed and presented through assistive technology.
• Audio characteristics - For systems that present auditory content, people may need to adjust specific characteristics of audio content, cues, and feedback.
• Audio control - For systems that present auditory content, people must be able to control the content ' s auditory content volume independently from the overall system volume level.
• Avoid contrast changes - For systems that present content, people may need to avoid changes to the foreground color that reduce the contrast with the background color.
• Avoid glare - For stationary or installed systems, people may need to avoid reflective and environmental glare.
• Avoid overwhelming visuals - For systems with visual content, people may need to avoid visual events that may overload their perception.
• Changing content alternatives - For systems that provide changes in content (including state, role or value), people may need visual, auditory, and tactile indications of the change.
• Changing content programmatic - For systems that provide changes in content (including state, role or value), people may need programmatic indcations of the change.
• Clean accessible name - Relates to interactive equivalent
• Consistent layout - For systems that present content, people may need consistent layouts and hierarchies using familiar conventions.
• Control timeout - For systems that time out, people may need to be able to adjust, extend or turn off any time out.
• 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 - 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.
• 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.
• 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.
• 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.
• 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.
• Harmful visual content - For systems that provide visual content, people may need to identify flashing, motion, and other visual effects that can harm them and avoid it.
• Hover content - For systems that present hover content, people may need hover content to be dismissible, hoverable, and persistent.
• 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.
• 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.
• Language of content - For systems that present language based content, people may need the language of content to be programmatically determinable.
• Large scale layout - For systems with large scale display modes, people may need the visual relationship aspects of the layout to be preserved, and content not to be clipped.
• Limited vision distinguish distractions - For systems that present content that is not related to a task or from a different source than the main content, people may need the secondary content to be clearly indicated programmatically, visually with high luminosity, or with equivalent auditory and tactile versions.
• Magnification - For systems that present visual content, people may need to magnify or resize content.
• 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 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.
• Meaningful sequence - For systems that present content, people may need the content to be available in a meaningful sequence both sensorily and programmatically.
• 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.
• Name, role, value, state - Overlap with programmatic structure and relationships.
• 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.
• No reliance on specific sense to avoid injury - For system the presents content and other stimuli, people may need alternative versions of content that do not rely on a specific sense to avoid injury.
• No visual seizure triggers - For systems with visual content, people may need to be able to avoid visual patterns that cause seizures or adjust the viewing of such visual patterns so that they are safe.
• No-color equivalents - For systems that use color to indicate meaning, people may need information provided through chromaticity to be available in another visual manner.
• Non-visual instructions - For systems that prsent visually oriented instructions, people may need non-visual cues as well.
• Nontext contrast - For systems that present visual interface components and graphical objects, people may need these to have sufficient contrast with adjacent colors.
• Nonvisual instruction references - For systems that provide instructions, people may need instructions that reference visual information to include an additional programmatic reference or provide equivalent auditory or tactile references.
• Noticeable non-visual alert - For systems that present visual, time-sensitive alerts, people may need the alerts to be in a format that they will notice immediately, such an auditory alert or insistent vibration.
• Obvious, avoidable hazards - For systems that include hazards, people may need the hazards to be obvious, easy to avoid, and difficult to trigger.
• Output modality choice - As a user with limited or no vision or with limited or no hearing, I need to be able to choose modalities to be used for outputs from the system.
• Personalized Interface - People may need to be able to customize their interface.
• 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.
• 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.
• 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.
• 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.
• 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.
• Status indicators - For systems with toggle controls that have states, people may need the state of the system available to them.
• 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.
• Turn off visual output - For systems with visual content, people may need to turn off the visual 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.
• 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.
• Visual equivalents - For systems with media content, people may need audio descriptions or a text transcript available.
• Visual presentation control - For systems that present text, people may need to be able to control the visual presentation of the content including color, orientation, formatting, spacing, justification, and size.
• Visual/tactile feedback at control location - As a user with a disability who might not be paying attention to other output devices, I need to have visual or tactile feedback occur at the same location as the control I am using.
• Without fear of consequences - People may need to be able to use products without the fear of negative consequences if they make mistakes.