Guidance statements

202 guidance statements:

• 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.
• Adaptable captions - As a person who uses captions or subtitles to access spoken content, and who also has moderate visual impairment, I need to be able to customize the presentation of captions and subtitles so I can read them effectively.
• Adjustable parts - For systems with physical input or output devices, people may need to adjust the location and position of the devices to have all of them within easy view and reach.
• Adjustable volume - For systems that present auditory content, people may need to adjust the volume of the system to a suitable level.
• Alternate versions - For systems that present language based content, may need alternative versions of the content (iconography, simplified, summarized, etc.)
• Alternative to auditory alerts - For systems that provide auditory alerts regarding critically important information, people may need to receive visual or tactile alerts instead.
• Alternative to holding - For systems that use buttons to input data, people may need an alternative input to holding a button down.
• Alternative to tactile alerts - For systems that provide visual alerts regarding critically important information, people may need to receive auditory or visual alerts instead.
• Alternative to visual alerts - For systems that provide visual alerts regarding critically important information, people may need to receive auditory or tactile alerts instead.
• Alternatives to motion-based input - For systems that use motion or multi-dimensional movement for input, people may need alternatives to motion-based input.
• Appropriate brightness - For systems that present visual content, people may need to change the brightness based on the viewing environment and situation.
• 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.).
• Appropriate speed - For systems that present dynamic images, people may need adjust the presentation speed to enable them to perceive and track them.
• Appropriate tactile settings - As someone who uses tactile output, I need to have control over tactile settings so that they better fit my needs (including adjustment of vibration amplitude, and choosing vibration patterns instead of frequency or strength attributes).
• 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.
• Auditory equivalents - For systems with auditory content, people may need that content presented programmatically or need equivalent visual and tactile versions.
• 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 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 excessive heat - For systems that require physical operation, people may need to limit the amount of heat (or other radiation) on controls so that it does not cause discomfort or injury.
• Avoid excessive heat - For systems that provide tactile content, people may need to limit the amount of heat (or other radiation) felt at touch points so that it does not interfere with their ability to perceive tactile information
• 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.
• Avoid glare - For stationary or installed systems, people may need to avoid reflective and environmental glare.
• 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 overwhelming audio - For systems with audio content, people may need to avoid audio events that may overload their perception.
• Avoid overwhelming haptics - For systems with tactile content, people may need to avoid haptic effects events that may overload their perception or prevent them from completing a tactile task.
• Avoid overwhelming visuals - For systems with visual content, people may need to avoid visual events that may overload their perception.
• 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.
• 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).
• Change to cultural conventions, words, and symbols - For systems that present text and images, people may need to change input and user interface components to use text or symbols with which they familiar.
• 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.
• 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.
• Clean accessible name - Relates to interactive equivalent
• 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.
• Concurrent input - For systems that take input, people may need to use concurrent input mechanisms.
• 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.
• Control distractions - For systems that include notifications or other interruptions to task completion, people may need to control interruptions.
• Control sensitivity - For systems that require physical operation, people may need to be able to adjust the sensitivity of controls.
• Control timeout - For systems that time out, people may need to be able to adjust, extend or turn off any time out.
• 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.
• Digital-Accessibility-Framework - The Digital Accessibilty Framework is an effort to help inform standards development in accessibility going forward. This repository works together with a matrix mapping currently tracked in a spreadsheet . The spreadsheet lists combinations of functional needs, user needs, and user need relevance, for which we may make statements describing the specific accessibility issue. The statements themselves are developed in this repository, and imported into an offline database. The middle- and front-end connection to the database is in a web application . A static copy of the data from the database is in another repository, which also includes the schema for the database. To document an accessibility statement: It will be most useful if links to the same resource use the same pattern. For the following resources, links should come from the base URI provided.
• Distinguish auditory components - People may need to use assistive technology or accessibility features without interference from other devices.
• 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 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 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.
• Game speed - For system used to play games, people may need to be able to adjust the speed of game play.
• 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.
• Haptic control - For systems with tactile content, people may need to be able to control haptic output.
• Harmful triggering content - For systems with potentially triggering content, people may need to identify sensitive content in advance and avoid it.
• 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.
• Hide accessibility features - For systems that provide specific accessibility functions, people may need to temporarily hide them.
• Hover content - For systems that present hover content, people may need hover content to be dismissible, hoverable, and persistent.
• Human help - For systems that may require assistance, people may need easy access to trained human help.
• 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.
• 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.
• 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.
• 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.
• Location in Context - People may need their current location within the larger structure to be presented visually and programmatically.
• Magnification - For systems that present visual content, people may need to magnify or resize content.
• 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.
• 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.
• Modified motion-based input - For systems that uses motion based input tools, people may need reduced or slowed motion and rest breaks.
• Monoaural information - For systems that present multi-channel audio information, including directional information, people may need the same information available in a monoaural form.
• Motion errors - For systems that use motion based input, people may need to turn it off.
• 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.
• 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.
• 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 audio seizure triggers - For systems with audio output, people may need to to avoid auditory patterns that cause seizures.
• No chemical harm - People may need to systems made of safe material, that do not give off chemicals to which they are sensitive or have an allergy.
• 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 electromagnetic harm - People may need to have systems that do not give off inappropriate electromagnetic radiation.
• 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 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.
• 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.
• Nonauditory instruction references - For systems that provide instructions, people may need instructions that reference auditory information to include an additional programmatic reference or provide equivalent visual or tactile references.
• Nongustatory nonolfactory alternate instruction references - For systems that provide instructions, people may need instructions that reference smell or taste to include an additional programmatic reference or provide equivalent visual, auditory, and tactile references
• Nontactile alternate instruction references - For systems that provide instructions, people may need instructions that reference touch to include an additional programmatic reference or provide equivalent visual or auditory references
• Nontext contrast - For systems that present visual interface components and graphical objects, people may need these to have sufficient contrast with adjacent colors.
• Nonvisual and Auditory Alternate Intruction References - As a user with no vision and no hearing, I need instructions that reference auditory or visual information to include an additional programmatic reference or provide equivalent tactile references
• 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.
• Not cause fatigue or discomfort - People may need systems that do not cause fatigue or discomfort when used.
• Noticeable non-auditory alert - For systems that present auditory, time-sensitive alerts, people may need the alerts to be in a format that they will notice immediately, such as flashing lights or insistent vibration.
• 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.
• Notifications in auditory alternatives - For systems that present auditory notifications, people may need visual or tactile equivalents.
• Number alternatives - For systems that present numbers or numeric content, people may need alternative ways to understand what the numbers mean.
• Obvious, avoidable hazards - For systems that include hazards, people may need the hazards to be obvious, easy to avoid, and difficult to trigger.
• Olfactory equivalents - For systems with olfactory or gustatory content, people may need that content presented programmatically or need equivalent visual, auditory, and tactile versions.
• 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.
• 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.
• 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.
• 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.
• Reconfigure controls - For system that have physical input or output devices, people may need to remap and reconfigure my controls.
• Redundant Entry - For systems that require data input, people may need to avoid entering data more than once.
• Repetitive strain injuries - For systems that require that involve extensive repetitive actions for input, people may need alternate input devices or approaches.
• 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.
• 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.
• 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.
• 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 controls - For systems with complex input controls, people may need simple alternatives.
• Simple login - For systems with a login, people may need a simple way to log in.
• Single action - For systems that use fine motor control based input, some users may need an alternative input mechanism that requires only a single action and a single pointer to input information and navigate (alternative to multi-point gestures, dragging, pointer movements, etc)
• Software control - For systems that require physical operation, people may need to access functionality through software that is ordinarily controlled through hardware.
• 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.
• Stop moving targets - For systems with interactive elements that require accuracy, people may need to stop interactive elements from moving.
• Successes acknowledged - For systems used to complete tasks, people may need to have even small successes acknowledged to increase self-esteem.
• Supplement auditory location cues - For systems that present auditory cues to location in space, people may need the location represented in other forms, such as visual, textual, or haptic cues.
• Synchronized captions - For system with auditory content, people may need captions synchronized with the main content.
• Tactile symbol clarity - As someone who feels tactile symbols, I need to have tactile symbols with an appropriate level of clarity so that I can easily perceive, differentiate, or read them.
• Tactile text speed - As someone who reads tactile text, I need to have tactile text at an appropriate reading speed.
• 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.
• Turn off tactile output - For systems with tactile output, people may need to turn off the tactile output from a system.
• 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.
• 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.
• 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 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 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.
• 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.
• 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.
• build output - dist/ .astro/ node _ modules/ npm-debug.log * yarn-debug.log * yarn-error.log * pnpm-debug.log * .env .env.production .DS _ Store .vs/ .vscode/