Make sure that all non-text content, such as images, videos, and audio, has a text alternative. This helps people who cannot see or hear the content to understand and interact with it.
Ensure that prerecorded audio-only and prerecorded video-only content has a text alternative so that people who cannot hear or see the content can still understand it.
• Prerecorded Audio-Only: Provide a text alternative that conveys the same information as the audio.
• Prerecorded Video-Only: Provide either a text alternative or an audio description that conveys the same information as the video.
Ensure that all prerecorded videos include captions so that people who are deaf or hard of hearing can understand the audio content.
• Captions Required: Provide captions for all prerecorded video content that includes audio.
Ensure that prerecorded videos include audio descriptions or a media alternative so that people who are blind or cannot understand the visual content can access the information.
• Audio Description: Provide an audio track that describes the visual content of the video.
• Media Alternative: Offer an alternative form of media that conveys the same information as the video.
• Exceptions: An audio description or media alternative is not required if the video is a media alternative for text and is clearly labeled as such.
Ensure that all live audio content in videos includes captions so that people who are deaf or hard of hearing can follow along in real time.
• Live Captions: Provide real-time captions for all live audio content in synchronized media.
• Scope: Captions should be available for all live audio broadcasts, including webcasts and live streams.
Ensure that all prerecorded videos include an audio description that provides a spoken description of the visual content, so that people who are blind or have low vision can understand the visual aspects of the video.
• Audio Description Required: Provide an audio description for all prerecorded video content.
• Synchronized Media: The audio description should be synchronized with the video, describing visual elements and actions as they occur.
Ensure that all prerecorded videos include sign language interpretation for audio content, so that people who are deaf or hard of hearing can access the content in their preferred mode of communication.
• Sign Language Interpretation Required: Provide a sign language interpretation for all prerecorded audio content in synchronized media.
• Scope: Sign language interpretation should be available for all prerecorded audio in time-based media.
Ensure that prerecorded videos include extended audio descriptions that offer detailed spoken descriptions of visual content, especially when standard audio descriptions are not sufficient.
• Extended Audio Description Required: Provide extended audio descriptions for prerecorded videos where regular pauses in the audio are insufficient to describe the visual content adequately.
• Alternative Version: Offer an alternative version of the video that includes extended audio descriptions. This version should temporarily pause the main audio (and video) to allow detailed descriptions to be provided between dialogue.
Provide a text-based alternative for all prerecorded video content to ensure that people who are deaf-blind or prefer reading can access the information at their own pace.
• Text Alternative Required: Offer a text equivalent for all prerecorded synchronized media and prerecorded video-only content.
• Scope: The text alternative must be different from captions or a transcript and should fully convey the information presented in the video.
Ensure that live audio-only content includes a text-based alternative so that people who are deaf or hard of hearing can access the information in real time.
• Text Alternative Required: Provide a text equivalent for all live audio-only content.
• Scope: The text alternative should deliver the same information as the live audio, making it accessible for individuals who cannot hear or understand the audio.
Use appropriate coding techniques to clearly define and reinforce the structure and relationships of content. This allows people using assistive technologies to understand the information, regardless of how it is styled visually.
• Programmatic Structure: Use the correct HTML elements (e.g., headings, lists, tables) to define the content’s structure and relationships.
• Consistent Meaning: Ensure that the meaning and relationships of content are preserved even when visual styling changes.
• Assistive Technology: Screen readers and other assistive technologies should be able to determine the content’s structure and relationships accurately without relying on visual presentation.
Ensure that the order in which content is presented is meaningful and correctly maintained, so that users, including those using assistive technologies, can understand the content as intended.
• Correct Reading Sequence: The sequence in which content is presented should reflect its logical and meaningful order.
• Programmatic Determination: The correct reading order can be programmatically determined and should be preserved even when visual styling changes.
• Assistive Technology: Screen readers and other assistive technologies should present content in the intended order, regardless of how it is styled or arranged visually.
Ensure that instructions for interacting with content do not rely solely on sensory characteristics (like color, shape, or sound) but provide clear, non-visual descriptions.
• Descriptive Instructions: Provide instructions for using controls and components based on their function or name, not just on their visual or sensory attributes.
• Non-Visual Guidance: Instructions should be understandable without relying on sensory characteristics such as color, shape, size, position, or sound.
Ensure that content can be accessed and used in both portrait and landscape orientations. This allows users to interact with the content regardless of how their device is positioned.
• Flexible Orientation: Content should not be restricted to a single display orientation (portrait or landscape) unless a specific orientation is essential for functionality.
• Orientation Adaptability: The content should remain accessible and functional when the device is rotated between portrait and landscape orientations.
Clearly indicate the purpose of each input field in forms to help users understand what information is required, especially for those with cognitive disabilities.
• Programmatic Identification: Ensure that the purpose of each input field can be programmatically determined using appropriate HTML elements or attributes.
• Field Types and Labels: Use clear labels and input types that specify what information is expected and enable features like autocomplete when appropriate.
Clearly define the purpose of all controls, icons, and key regions on a page using code. This helps users understand their function, especially those with cognitive disabilities who might find it challenging to interpret controls based on names alone.
• Programmatic Identification: Ensure that the purpose of user interface components, icons, and regions can be programmatically determined using appropriate code or attributes.
• Clear Meaning: Use ARIA roles, landmarks, or other markup techniques to describe the purpose and function of key elements on the page.
Do not rely solely on color to convey information, indicate actions, or distinguish visual elements. Use additional methods, such as text, shapes, or patterns, to ensure that all users can understand the information.
• Multimodal Communication: Use more than just color to convey information, indicate actions, or differentiate elements.
• Complementary Methods: Provide additional cues, such as text labels, patterns, or shapes, to ensure that information is accessible to those who may have color vision deficiencies or other visual impairments.
Ensure that content can be enlarged without requiring scrolling in both directions. This means text should reflow within the viewport, making it accessible to users who need larger text.
• Vertical Scrolling: Content must fit within a width of 320 CSS pixels without horizontal scrolling.
• Horizontal Scrolling: Content must fit within a height of 256 CSS pixels without vertical scrolling.
• Exceptions: Content requiring two-dimensional scrolling, like maps, diagrams, presentations, data tables, and games, is not subject to this requirement.
Ensure that important visual information, like user interface components and graphical objects, has sufficient contrast against its background. This helps users with low vision distinguish key elements.
• Contrast Ratio: Visual elements must have a contrast ratio of at least 3:1 against adjacent colors.
• User Interface Components: Contrast is required for elements necessary for understanding the interface, excluding inactive components or those whose appearance is not controlled by the author.
• Graphical Objects: Contrast is required for parts of graphics essential for understanding the content, except when specific presentation is crucial to convey information.
Ensure that text maintains readability when users adjust text spacing settings, including line height, paragraph spacing, letter spacing, and word spacing. This flexibility helps users with different reading needs.
• Line Height: At least 1.5 times the font size.
• Paragraph Spacing: At least 2 times the font size.
• Letter Spacing: At least 0.12 times the font size.
• Word Spacing: At least 0.16 times the font size.
• No Loss of Content: Content or functionality must not be lost when users adjust these settings.
Ensure that content triggered by hover or focus is predictable, dismissible, and does not disappear unexpectedly, to improve accessibility and usability.
• Dismissible: Users can dismiss additional content without changing hover or focus, unless it’s an input error or doesn’t obscure or replace other content.
• Hoverable: Additional content triggered by hover remains visible if the pointer moves over it.
• Persistent: Content remains visible until the trigger is removed, the user dismisses it, or the content is no longer valid.
Ensure that users can manage audio content on a page so that it does not disrupt their experience. This includes providing controls to pause, stop, or adjust the volume of audio that plays automatically.
• Control Mechanism: If audio plays automatically for more than 3 seconds, provide a control mechanism to pause or stop the audio.
• Volume Control: Alternatively, provide a way to adjust the audio volume independently from the system volume.
Make sure that text and images of text have enough contrast with their background so that they are readable by everyone, including those with visual impairments.
• Contrast Ratio: Text and images of text must have a minimum contrast ratio of 4.5:1 against their background.
• Large Text: For large text (18px or larger), the contrast ratio should be at least 3:1.
• Incidental Text: Text or images of text that are purely decorative, part of inactive user interface components, or not visible do not need to meet contrast requirements.
• Logotypes: Text that is part of a logo or brand name is exempt from contrast ratio requirements.
Ensure that text on your website can be resized up to 200% without losing any content or functionality. This helps users who need larger text to read comfortably.
• Resizing Capability: Text can be resized up to 200% from its original size without the need for assistive technology.
• Content and Functionality: When text is resized, all content and functionality must remain accessible and usable.
Whenever possible, use actual text rather than images of text. This allows users to adjust how the text is presented according to their needs.
Text vs. Images: Use text to convey information instead of using images of text, unless:
• Customizable: The image of text can be customized to meet user requirements.
• Essential: The specific presentation of the text is crucial to conveying the intended information (e.g., logotypes or brand names).
Provide strong contrast between text and its background to ensure readability for users who need higher contrast levels.
• Contrast Ratio: Text and images of text must have a contrast ratio of at least 7:1 against their background.
• Large Text: Large-scale text (18px or larger) must have a contrast ratio of at least 4.5:1.
• Incidental Text: Text or images of text that are decorative, part of inactive UI components, not visible, or part of a picture with significant other visual content are exempt from contrast requirements.
• Logotypes: Text within logos or brand names does not need to meet the enhanced contrast ratio.
Ensure that prerecorded audio primarily containing speech is clear and not disrupted by background sounds.
For prerecorded audio-only content that features primarily speech (excluding audio CAPTCHAs, audio logos, or musical vocalizations), one of the following must apply:
• No Background: The audio does not contain any background sounds.
• Turn Off: Background sounds can be turned off by the user.
• 20 dB Lower: Background sounds are at least 20 decibels lower than the foreground speech, except for brief, occasional sounds lasting only 1-2 seconds.
Allow users to adjust text appearance to meet their preferences or needs for better readability and accessibility.
For blocks of text, one or more of the following must be possible:
• Color Customization: Users can select foreground and background colors.
• Width Limitation: Text width is limited to no more than 80 characters or glyphs per line (40 characters for CJK languages).
• Text Alignment: Text is not justified (aligned to both left and right margins).
• Line and Paragraph Spacing:
• Line spacing (leading) is at least 1.5 times the font size within paragraphs.
• Paragraph spacing is at least 1.5 times larger than the line spacing.
• Text Resizing: Text can be resized up to 200% without requiring horizontal scrolling.
Ensure users can adjust text presentation by avoiding images of text unless essential for style or decoration. Use text whenever possible for content, as images cannot be resized or reformatted, limiting accessibility.
Use Images of Text only when:
• Decorative: The text is used purely for decoration and does not convey critical information.
• Essential Presentation: The specific presentation of text is essential for conveying meaning (e.g., logotypes or certain branding elements).
All functionalities must be operable using a keyboard without requiring specific timing for keystrokes, except for functions that inherently depend on user movement paths.
• Keyboard Accessibility: All features must be accessible through keyboard navigation.
• No Timing Restrictions: Keyboard actions should not require specific timing or sequences unless the function inherently needs user movement paths.
Ensure that users can navigate away from any component using only the keyboard, and provide guidance if non-standard methods are required.
• Keyboard Navigation: Users must be able to move focus away from any component using only the keyboard.
• Guidance for Non-Standard Methods: If non-standard keyboard methods are needed to exit a component, users should be informed.
Ensure that every action available with a mouse can also be performed using a keyboard, without needing specific timings for keystrokes.
• Keyboard Operation: All functionalities must be operable using a keyboard.
• No Timing Requirements: Functions should not require specific timing or sequences of keystrokes.
Ensure that keyboard shortcuts using only letters, numbers, or symbols can be either turned off, remapped, or are only active when the relevant component is focused.
• Turn Off: Provide a mechanism to disable the shortcut.
• Remap: Allow remapping the shortcut to include non-printable keys (e.g., Ctrl, Alt).
• Active on Focus: Ensure shortcuts are active only when the relevant component has focus.
Allow users to manage time limits by turning them off, adjusting them, or extending them when needed. This helps accommodate varying needs for completing tasks.
• Turn Off: Users can turn off the time limit before it starts.
• Adjust: Users can adjust the time limit to be at least ten times the default setting.
• Extend: Users are warned before time expires, given at least 20 seconds to extend the time limit with a simple action, and can extend it at least ten times.
• Exceptions: Time limits that are essential for real-time events, longer than 20 hours, or are crucial for the activity are exempt.
Allow users to pause, stop, or hide content that moves, blinks, scrolls, or auto-updates to avoid distractions and interruptions.
• Moving, Blinking, Scrolling: Provide a way to pause, stop, or hide content that moves, blinks, or scrolls automatically for more than 5 seconds when presented with other content.
• Auto-Updating: Provide a way to pause, stop, hide, or control the update frequency of auto-updating content that starts automatically when presented with other content.
Avoid using time limits for tasks and interactions, unless required for non-interactive media or real-time events.
• No time limits are imposed for tasks or interactions, except for synchronized media (e.g., video) or real-time events.
Allow users to postpone or suppress interruptions, except for emergencies, to avoid disruptions.
• Users can delay or turn off interruptions, except in emergencies.
Ensure that users do not lose their activity or data when their session expires and they need to re-authenticate. This helps users who may require more time to complete their tasks.
• Users can continue their activity and retain their data after re-authenticating if their session expires.
Notify users about the duration of inactivity before they risk losing data, unless data is preserved for more than 20 hours of inactivity. This ensures users are aware of how long they have to complete actions.
• Users are warned about the duration of inactivity that could lead to data loss, unless data is preserved for more than 20 hours.
Ensure content does not flash more than three times per second to prevent seizures and other health issues. Avoid using saturated red colors and high contrast in flashing content.
• Content does not flash more than three times per second.
• Flashes must be below the general flash and red flash thresholds.
Ensure content does not flash more than three times per second to prevent triggering seizures or other health issues, protecting users who are sensitive to rapid flashing.
• Content flashes no more than three times per second.
Allow users to disable or minimize motion and animations triggered by their interactions, based on their preferences. This helps prevent motion-induced discomfort and ensures a more comfortable experience for those sensitive to motion effects.
Provide mechanisms to skip repeated content blocks for easier keyboard navigation. This helps users, especially those relying on keyboard navigation, to move efficiently through pages without having to tab through repetitive elements like headers and navigation menus.
Users can skip repetitive content blocks that appear on multiple pages.
Provide headings to clearly delineate different sections of content. This helps users, especially those with cognitive or visual disabilities, to navigate and understand the structure of the content.
• Headings are used to separate and organize content into distinct sections.
• Headings can be titles or other forms of content labels.
When a user interface component receives keyboard focus, it must be at least partially visible on the screen. This ensures that users who rely on keyboard navigation can see and interact with the focused element, even if other content is on the page.
• Any element that receives keyboard focus must not be completely obscured by other content or off-screen.
• If content can be moved or repositioned by the user, ensure the initial position of the focusable component is not hidden.
When a user interface component receives keyboard focus, it must be completely visible without any part of it being obscured by other content or off-screen. This allows users who rely on keyboard navigation to see the entirety of the focused element and interact with it effectively.
• No part of the component that receives keyboard focus should be covered by other content or be out of view.
• Ensure that the component is fully visible within the viewport, without requiring the user to scroll or adjust the view to see it.
When an element receives keyboard focus, the focus indicator must be clearly visible. This makes it easier for users to locate and interact with the focused element, especially those with visual impairments or older adults.
• The focus indicator is at least as wide as a 2 CSS pixel thick border of the unfocused component.
• The focus indicator has a contrast ratio of at least 3:1 between its focused and unfocused states.
Ensure each web page has a descriptive title that clearly indicates its topic or purpose. This helps users identify and differentiate between pages, improving navigation and usability.
Web pages must have titles that clearly describe the content or purpose of the page.
Ensure that when navigating a web page using a keyboard, focusable elements (like links, buttons, and form fields) receive focus in a sequence that makes sense and maintains the intended meaning and functionality of the page. This helps users understand and interact with the content efficiently.
Focusable components must follow a logical order that preserves the intended meaning and functionality during keyboard navigation.
Ensure that the purpose of each link is clear from its text or the surrounding context, so users know what to expect when they activate it. This clarity helps users with visual or cognitive disabilities navigate and interact with content more effectively.
The purpose of each link is understandable from its text or from the context provided by nearby content.
Provide at least two different ways for users to navigate to the same content within a set of web pages. This ensures that users who have different navigation preferences or disabilities can still reach the desired information.
At least two methods are available to locate a web page within a set of pages, unless the page is a necessary step in a process or results from a specific action.
Ensure that all headings and labels effectively convey the topic or purpose of the content they describe. This helps users, particularly those with cognitive or visual disabilities, understand and navigate the page more easily.
Headings and labels accurately describe the content or functionality they represent.
Ensure that every interactive element on the page provides a visible indicator when it receives keyboard focus. This helps keyboard users, especially those with visual impairments, identify and interact with the currently focused element.
All keyboard-focusable elements display a visible indicator when in focus.
Provide clear indicators, such as breadcrumbs, site maps, or other navigation aids, to show users their location within a set of web pages. This helps users understand their context and navigate more effectively, especially those with cognitive disabilities.
Users can always identify their current location within the site’s structure through visible navigational aids.
Ensure that each link has descriptive text that clearly indicates where the link will lead or what action it will perform. This helps all users, particularly those using assistive technologies, understand link purposes without needing additional context.
The purpose of each link can be determined from the link text alone. The text should be clear and informative, avoiding ambiguity.
Functionality that requires complex or multi-touch gestures should also be operable with a single touch or pointer gesture. This ensures that users who cannot perform multi-point or path-based gestures have access to all functions. This requirement applies to web content but does not extend to actions necessary for the operation of the user agent or assistive technology.
• Any function that is activated by multi-touch or path-based gestures must also be operable with a single touch or pointer gesture, unless the complex gesture is essential to the functionality.
For actions that are triggered by a single pointer, ensure that users can easily cancel or undo unintended actions. This is important for preventing mistakes and ensuring that users can recover from accidental inputs. Functions should not rely solely on the initial pointer press to execute actions.
For functionality operated by a single pointer, at least one of the following must be true:
• No Down-Event: The action is not executed until the pointer is released.
• Abort or Undo: The function is completed on the up-event, and users have a way to cancel the action before completion or undo it afterward.
• Up Reversal: The up-event reverses any outcome of the preceding down-event.
• Essential: The function requires completion on the down-event due to its nature (e.g., emulating a keyboard key press).
Ensure that the text or images of text used for visual labels on controls match the accessibility name provided in the code. This alignment is crucial for users who rely on speech recognition or screen readers, as these tools use the accessibility name to interact with controls.
For user interface components with visual labels (text or images of text):
• The name in the code must include the text presented visually.
• Ideally, the text of the label should appear at the beginning of the accessibility name.
Functionality that relies on device motion should also be operable through other user interface components. Allow users to disable motion-based controls to avoid accidental activation, except in specific cases where motion is essential for the function.
• Functionality operable by device motion must also be operable through a non-motion-based interface.
• Users must be able to disable motion-based interactions to prevent accidental activation, unless:
• Supported Interface: The motion-based functionality is supported by an accessible interface.
• Essential: The motion-based functionality is crucial and cannot be replaced by another method without affecting the activity’s purpose.
Make custom interactive targets (such as buttons and links) at least 44 by 44 CSS pixels to accommodate users who have difficulty tapping small objects.
• Interactive targets must be at least 44 by 44 CSS pixels in size.
Allow users to use various input methods simultaneously and do not restrict them to just one type of input. This ensures everyone can interact with content using the input method that suits them best, whether it’s a mouse, keyboard, touch screen, voice commands, or assistive devices.
• Users can switch between different input methods (like mouse, keyboard, touch, or voice) without restrictions.
• Input methods should not be limited unless it is necessary for security reasons, to follow user settings, or if the restriction is essential for specific functionality.
Ensure that any functionality that requires dragging can also be performed using a simpler, single-point action. This helps users who cannot drag items or perform complex movements.
Make sure that all interactive controls (like buttons and links) are large enough or spaced adequately so that they are easy to activate, even for users with physical impairments who may struggle with small or closely placed targets.
• Targets must be at least 24 by 24 CSS pixels.
• If targets are smaller than 24 by 24 pixels, they should be spaced so that they do not overlap when a 24-pixel diameter circle is centered on each.
• Alternatives are provided if targets are smaller than the minimum size.
Ensure that the primary language of each web page is clearly defined so that assistive technology can present the content in the correct language.
• The default human language of the page is specified in the code.
Clearly identify when sections of text within a web page are in a language different from the default language, so assistive technology can present the information correctly.
• The language of each passage or phrase within the content is specified, except for proper names, technical terms, indeterminate words, and adopted vernacular phrases.
Ensure that definitions or explanations are available for technical terms, jargon, or unusual words used in content to help users understand them better.
• A clear mechanism is provided to access definitions for words or phrases that are used in an unusual way, including technical jargon, idioms, or specialized terms.
Ensure that users can easily find the full meaning of abbreviations used on a page.
A clear method is available to view the expanded form or full meaning of any abbreviations used in the content.
Ensure that content is accessible to users with lower reading skills by offering simplified versions or alternative formats.
• When text exceeds the reading level of lower secondary education (approximately 9 years of schooling), provide an alternative version that is easier to understand.
• Alternatively, offer supplemental content such as audio, illustrations, or a summary that conveys the same information in a simpler form.
Ensure users can understand how to pronounce words when their meaning is unclear from context alone.
• Provide a clear mechanism for users to learn the pronunciation of words when it is necessary to understand their meaning.
Ensure that navigating to or focusing on an element does not unexpectedly change the user’s current context.
When a user interface element gains focus, the context or page does not change unexpectedly.
Ensure that changing settings or inputting data into user interface components does not unexpectedly alter the context or navigation.
• Changes to a user interface component should not automatically result in a context change unless the user has been informed beforehand.
Ensure that navigation elements that repeat across multiple pages maintain the same order and placement to facilitate predictable user interaction.
• Navigation elements that appear on multiple pages should have a consistent order and location unless the user explicitly changes it.
Ensure that elements with the same function are identified consistently across all pages to make interactions predictable.
• Components with identical functions should have consistent labels, icons, and accessibility attributes across all pages.
Allow users to control when major changes to content or context occur, ensuring changes are not automatic.
• Major content or context changes should only occur in response to a user action or request.
• Provide a mechanism to turn off automatic changes if they are triggered by user actions.
Ensure help and support options are consistently located across multiple pages to make them easier to find.
• Help mechanisms (such as contact details, self-help options, and automated contact methods) should be in the same position on every page where they appear.
• The order of these help mechanisms relative to other page content should remain consistent unless the user initiates a change.
Ensure that when errors occur, they are clearly identified and explained to users.
• When an error is detected in user input, the affected item must be highlighted or indicated.
• A descriptive error message must be provided to explain what went wrong and how to correct it.
Ensure that all input fields or areas requiring user interaction have clear labels or instructions.
• Every input field, dropdown, or interactive element must have a descriptive label or instruction indicating what information is required.
• Instructions should be provided where the purpose of the input or action is not immediately clear.
When users make an error, offer suggestions on how to correct it to help them resolve issues quickly.
• When an error is detected, provide specific suggestions on how to fix the issue.
• Suggestions should be clear, actionable, and relevant to the error encountered.
• Avoid providing suggestions if it compromises security or the purpose of the content.
Ensure users have the ability to review, correct, or reverse important actions to prevent errors in legal, financial, or data-related submissions.
For actions that involve legal commitments, financial transactions, or data changes, implement at least one of the following measures:
• Reversible: Allow users to undo or reverse their actions.
• Checked: Validate user input for errors and provide options to correct them.
• Confirmed: Provide a mechanism to review, confirm, and correct information before finalizing the submission.
Provide users with accessible and relevant help based on their current task to assist them in completing their actions accurately.
• Context-sensitive help is available for users while they are performing tasks, offering relevant information or guidance.
Ensure users have the ability to review, correct, and undo their submissions to prevent mistakes and ensure accurate information entry.
At least one of the following mechanisms must be available for pages where users submit information:
• Reversible: Submissions can be undone.
• Checked: Data entered by the user is validated for errors, and users can correct these errors.
• Confirmed: Users can review and confirm their information before finalizing the submission.
Prevent users from having to re-enter the same information multiple times within a single session to make multi-step processes easier to complete.
Information that has already been provided should be:
• Auto-Populated: Automatically filled in when needed again.
• Available for Selection: Presented to the user as an option to select from previously entered data.
Ensure that authentication processes do not rely on cognitive tasks, like solving puzzles or remembering complex information, to make login easier for everyone.
Authentication processes must not require users to solve puzzles, remember passwords, or transcribe codes unless:
• Alternative Method: An alternative authentication method is provided that does not rely on cognitive tasks.
• Assistance Mechanism: There is a mechanism to assist users in completing the cognitive task.
• Object Recognition: The cognitive task involves recognizing objects.
• Personal Content: The task involves identifying non-text content that the user has previously provided.
Ensure authentication processes avoid requiring users to recognize objects or media, making it easier for those with cognitive disabilities.
If cognitive function tests (CAPTCHA's for example) are used, they must be accompanied by:
Ensure that all user interface components, such as form elements and links, have correct names, roles, and states that can be detected by assistive technologies, and notify users of any changes.
• Name and Role: All user interface components must have a clear and correct name and role that can be programmatically determined.
• States and Values: User-set states, properties, and values must be programmatically accessible and update notifications must be provided.
• Notification: Assistive technologies should receive updates when component states or values change.
Ensure that important status messages are communicated to users through assistive technologies even when they do not receive focus, so all users are aware of content updates.
• Programmatically Determined: Status messages must be programmatically detectable through roles or properties.
• Assistive Technology Notification: Status updates should be announced to users by assistive technologies without requiring focus to be shifted.
Make sure that all non-text content, such as images, videos, and audio, has a text alternative. This helps people who cannot see or hear the content to understand and interact with it.
Ensure that prerecorded audio-only and prerecorded video-only content has a text alternative so that people who cannot hear or see the content can still understand it.
• Prerecorded Audio-Only: Provide a text alternative that conveys the same information as the audio.
• Prerecorded Video-Only: Provide either a text alternative or an audio description that conveys the same information as the video.
Ensure that all prerecorded videos include captions so that people who are deaf or hard of hearing can understand the audio content.
• Captions Required: Provide captions for all prerecorded video content that includes audio.
Ensure that prerecorded videos include audio descriptions or a media alternative so that people who are blind or cannot understand the visual content can access the information.
• Audio Description: Provide an audio track that describes the visual content of the video.
• Media Alternative: Offer an alternative form of media that conveys the same information as the video.
• Exceptions: An audio description or media alternative is not required if the video is a media alternative for text and is clearly labeled as such.
Use appropriate coding techniques to clearly define and reinforce the structure and relationships of content. This allows people using assistive technologies to understand the information, regardless of how it is styled visually.
• Programmatic Structure: Use the correct HTML elements (e.g., headings, lists, tables) to define the content’s structure and relationships.
• Consistent Meaning: Ensure that the meaning and relationships of content are preserved even when visual styling changes.
• Assistive Technology: Screen readers and other assistive technologies should be able to determine the content’s structure and relationships accurately without relying on visual presentation.
Ensure that the order in which content is presented is meaningful and correctly maintained, so that users, including those using assistive technologies, can understand the content as intended.
• Correct Reading Sequence: The sequence in which content is presented should reflect its logical and meaningful order.
• Programmatic Determination: The correct reading order can be programmatically determined and should be preserved even when visual styling changes.
• Assistive Technology: Screen readers and other assistive technologies should present content in the intended order, regardless of how it is styled or arranged visually.
Ensure that instructions for interacting with content do not rely solely on sensory characteristics (like color, shape, or sound) but provide clear, non-visual descriptions.
• Descriptive Instructions: Provide instructions for using controls and components based on their function or name, not just on their visual or sensory attributes.
• Non-Visual Guidance: Instructions should be understandable without relying on sensory characteristics such as color, shape, size, position, or sound.
Do not rely solely on color to convey information, indicate actions, or distinguish visual elements. Use additional methods, such as text, shapes, or patterns, to ensure that all users can understand the information.
• Multimodal Communication: Use more than just color to convey information, indicate actions, or differentiate elements.
• Complementary Methods: Provide additional cues, such as text labels, patterns, or shapes, to ensure that information is accessible to those who may have color vision deficiencies or other visual impairments.
Ensure that users can manage audio content on a page so that it does not disrupt their experience. This includes providing controls to pause, stop, or adjust the volume of audio that plays automatically.
• Control Mechanism: If audio plays automatically for more than 3 seconds, provide a control mechanism to pause or stop the audio.
• Volume Control: Alternatively, provide a way to adjust the audio volume independently from the system volume.
All functionalities must be operable using a keyboard without requiring specific timing for keystrokes, except for functions that inherently depend on user movement paths.
• Keyboard Accessibility: All features must be accessible through keyboard navigation.
• No Timing Restrictions: Keyboard actions should not require specific timing or sequences unless the function inherently needs user movement paths.
Ensure that users can navigate away from any component using only the keyboard, and provide guidance if non-standard methods are required.
• Keyboard Navigation: Users must be able to move focus away from any component using only the keyboard.
• Guidance for Non-Standard Methods: If non-standard keyboard methods are needed to exit a component, users should be informed.
Ensure that keyboard shortcuts using only letters, numbers, or symbols can be either turned off, remapped, or are only active when the relevant component is focused.
• Turn Off: Provide a mechanism to disable the shortcut.
• Remap: Allow remapping the shortcut to include non-printable keys (e.g., Ctrl, Alt).
• Active on Focus: Ensure shortcuts are active only when the relevant component has focus.
Allow users to manage time limits by turning them off, adjusting them, or extending them when needed. This helps accommodate varying needs for completing tasks.
• Turn Off: Users can turn off the time limit before it starts.
• Adjust: Users can adjust the time limit to be at least ten times the default setting.
• Extend: Users are warned before time expires, given at least 20 seconds to extend the time limit with a simple action, and can extend it at least ten times.
• Exceptions: Time limits that are essential for real-time events, longer than 20 hours, or are crucial for the activity are exempt.
Allow users to pause, stop, or hide content that moves, blinks, scrolls, or auto-updates to avoid distractions and interruptions.
• Moving, Blinking, Scrolling: Provide a way to pause, stop, or hide content that moves, blinks, or scrolls automatically for more than 5 seconds when presented with other content.
• Auto-Updating: Provide a way to pause, stop, hide, or control the update frequency of auto-updating content that starts automatically when presented with other content.
Ensure content does not flash more than three times per second to prevent seizures and other health issues. Avoid using saturated red colors and high contrast in flashing content.
• Content does not flash more than three times per second.
• Flashes must be below the general flash and red flash thresholds.
Provide mechanisms to skip repeated content blocks for easier keyboard navigation. This helps users, especially those relying on keyboard navigation, to move efficiently through pages without having to tab through repetitive elements like headers and navigation menus.
Users can skip repetitive content blocks that appear on multiple pages.
Ensure each web page has a descriptive title that clearly indicates its topic or purpose. This helps users identify and differentiate between pages, improving navigation and usability.
Web pages must have titles that clearly describe the content or purpose of the page.
Ensure that when navigating a web page using a keyboard, focusable elements (like links, buttons, and form fields) receive focus in a sequence that makes sense and maintains the intended meaning and functionality of the page. This helps users understand and interact with the content efficiently.
Focusable components must follow a logical order that preserves the intended meaning and functionality during keyboard navigation.
Ensure that the purpose of each link is clear from its text or the surrounding context, so users know what to expect when they activate it. This clarity helps users with visual or cognitive disabilities navigate and interact with content more effectively.
The purpose of each link is understandable from its text or from the context provided by nearby content.
Functionality that requires complex or multi-touch gestures should also be operable with a single touch or pointer gesture. This ensures that users who cannot perform multi-point or path-based gestures have access to all functions. This requirement applies to web content but does not extend to actions necessary for the operation of the user agent or assistive technology.
• Any function that is activated by multi-touch or path-based gestures must also be operable with a single touch or pointer gesture, unless the complex gesture is essential to the functionality.
For actions that are triggered by a single pointer, ensure that users can easily cancel or undo unintended actions. This is important for preventing mistakes and ensuring that users can recover from accidental inputs. Functions should not rely solely on the initial pointer press to execute actions.
For functionality operated by a single pointer, at least one of the following must be true:
• No Down-Event: The action is not executed until the pointer is released.
• Abort or Undo: The function is completed on the up-event, and users have a way to cancel the action before completion or undo it afterward.
• Up Reversal: The up-event reverses any outcome of the preceding down-event.
• Essential: The function requires completion on the down-event due to its nature (e.g., emulating a keyboard key press).
Ensure that the text or images of text used for visual labels on controls match the accessibility name provided in the code. This alignment is crucial for users who rely on speech recognition or screen readers, as these tools use the accessibility name to interact with controls.
For user interface components with visual labels (text or images of text):
• The name in the code must include the text presented visually.
• Ideally, the text of the label should appear at the beginning of the accessibility name.
Functionality that relies on device motion should also be operable through other user interface components. Allow users to disable motion-based controls to avoid accidental activation, except in specific cases where motion is essential for the function.
• Functionality operable by device motion must also be operable through a non-motion-based interface.
• Users must be able to disable motion-based interactions to prevent accidental activation, unless:
• Supported Interface: The motion-based functionality is supported by an accessible interface.
• Essential: The motion-based functionality is crucial and cannot be replaced by another method without affecting the activity’s purpose.
Ensure that the primary language of each web page is clearly defined so that assistive technology can present the content in the correct language.
• The default human language of the page is specified in the code.
Ensure that navigating to or focusing on an element does not unexpectedly change the user’s current context.
When a user interface element gains focus, the context or page does not change unexpectedly.
Ensure that changing settings or inputting data into user interface components does not unexpectedly alter the context or navigation.
• Changes to a user interface component should not automatically result in a context change unless the user has been informed beforehand.
Ensure help and support options are consistently located across multiple pages to make them easier to find.
• Help mechanisms (such as contact details, self-help options, and automated contact methods) should be in the same position on every page where they appear.
• The order of these help mechanisms relative to other page content should remain consistent unless the user initiates a change.
Ensure that when errors occur, they are clearly identified and explained to users.
• When an error is detected in user input, the affected item must be highlighted or indicated.
• A descriptive error message must be provided to explain what went wrong and how to correct it.
Ensure that all input fields or areas requiring user interaction have clear labels or instructions.
• Every input field, dropdown, or interactive element must have a descriptive label or instruction indicating what information is required.
• Instructions should be provided where the purpose of the input or action is not immediately clear.
Prevent users from having to re-enter the same information multiple times within a single session to make multi-step processes easier to complete.
Information that has already been provided should be:
• Auto-Populated: Automatically filled in when needed again.
• Available for Selection: Presented to the user as an option to select from previously entered data.
Ensure that all user interface components, such as form elements and links, have correct names, roles, and states that can be detected by assistive technologies, and notify users of any changes.
• Name and Role: All user interface components must have a clear and correct name and role that can be programmatically determined.
• States and Values: User-set states, properties, and values must be programmatically accessible and update notifications must be provided.
• Notification: Assistive technologies should receive updates when component states or values change.
Ensure that all live audio content in videos includes captions so that people who are deaf or hard of hearing can follow along in real time.
• Live Captions: Provide real-time captions for all live audio content in synchronized media.
• Scope: Captions should be available for all live audio broadcasts, including webcasts and live streams.
Ensure that all prerecorded videos include an audio description that provides a spoken description of the visual content, so that people who are blind or have low vision can understand the visual aspects of the video.
• Audio Description Required: Provide an audio description for all prerecorded video content.
• Synchronized Media: The audio description should be synchronized with the video, describing visual elements and actions as they occur.
Ensure that content can be accessed and used in both portrait and landscape orientations. This allows users to interact with the content regardless of how their device is positioned.
• Flexible Orientation: Content should not be restricted to a single display orientation (portrait or landscape) unless a specific orientation is essential for functionality.
• Orientation Adaptability: The content should remain accessible and functional when the device is rotated between portrait and landscape orientations.
Clearly indicate the purpose of each input field in forms to help users understand what information is required, especially for those with cognitive disabilities.
• Programmatic Identification: Ensure that the purpose of each input field can be programmatically determined using appropriate HTML elements or attributes.
• Field Types and Labels: Use clear labels and input types that specify what information is expected and enable features like autocomplete when appropriate.
Ensure that content can be enlarged without requiring scrolling in both directions. This means text should reflow within the viewport, making it accessible to users who need larger text.
• Vertical Scrolling: Content must fit within a width of 320 CSS pixels without horizontal scrolling.
• Horizontal Scrolling: Content must fit within a height of 256 CSS pixels without vertical scrolling.
• Exceptions: Content requiring two-dimensional scrolling, like maps, diagrams, presentations, data tables, and games, is not subject to this requirement.
Ensure that important visual information, like user interface components and graphical objects, has sufficient contrast against its background. This helps users with low vision distinguish key elements.
• Contrast Ratio: Visual elements must have a contrast ratio of at least 3:1 against adjacent colors.
• User Interface Components: Contrast is required for elements necessary for understanding the interface, excluding inactive components or those whose appearance is not controlled by the author.
• Graphical Objects: Contrast is required for parts of graphics essential for understanding the content, except when specific presentation is crucial to convey information.
Ensure that text maintains readability when users adjust text spacing settings, including line height, paragraph spacing, letter spacing, and word spacing. This flexibility helps users with different reading needs.
• Line Height: At least 1.5 times the font size.
• Paragraph Spacing: At least 2 times the font size.
• Letter Spacing: At least 0.12 times the font size.
• Word Spacing: At least 0.16 times the font size.
• No Loss of Content: Content or functionality must not be lost when users adjust these settings.
Ensure that content triggered by hover or focus is predictable, dismissible, and does not disappear unexpectedly, to improve accessibility and usability.
• Dismissible: Users can dismiss additional content without changing hover or focus, unless it’s an input error or doesn’t obscure or replace other content.
• Hoverable: Additional content triggered by hover remains visible if the pointer moves over it.
• Persistent: Content remains visible until the trigger is removed, the user dismisses it, or the content is no longer valid.
Make sure that text and images of text have enough contrast with their background so that they are readable by everyone, including those with visual impairments.
• Contrast Ratio: Text and images of text must have a minimum contrast ratio of 4.5:1 against their background.
• Large Text: For large text (18px or larger), the contrast ratio should be at least 3:1.
• Incidental Text: Text or images of text that are purely decorative, part of inactive user interface components, or not visible do not need to meet contrast requirements.
• Logotypes: Text that is part of a logo or brand name is exempt from contrast ratio requirements.
Ensure that text on your website can be resized up to 200% without losing any content or functionality. This helps users who need larger text to read comfortably.
• Resizing Capability: Text can be resized up to 200% from its original size without the need for assistive technology.
• Content and Functionality: When text is resized, all content and functionality must remain accessible and usable.
Whenever possible, use actual text rather than images of text. This allows users to adjust how the text is presented according to their needs.
Text vs. Images: Use text to convey information instead of using images of text, unless:
• Customizable: The image of text can be customized to meet user requirements.
• Essential: The specific presentation of the text is crucial to conveying the intended information (e.g., logotypes or brand names).
When a user interface component receives keyboard focus, it must be at least partially visible on the screen. This ensures that users who rely on keyboard navigation can see and interact with the focused element, even if other content is on the page.
• Any element that receives keyboard focus must not be completely obscured by other content or off-screen.
• If content can be moved or repositioned by the user, ensure the initial position of the focusable component is not hidden.
Provide at least two different ways for users to navigate to the same content within a set of web pages. This ensures that users who have different navigation preferences or disabilities can still reach the desired information.
At least two methods are available to locate a web page within a set of pages, unless the page is a necessary step in a process or results from a specific action.
Ensure that all headings and labels effectively convey the topic or purpose of the content they describe. This helps users, particularly those with cognitive or visual disabilities, understand and navigate the page more easily.
Headings and labels accurately describe the content or functionality they represent.
Ensure that every interactive element on the page provides a visible indicator when it receives keyboard focus. This helps keyboard users, especially those with visual impairments, identify and interact with the currently focused element.
All keyboard-focusable elements display a visible indicator when in focus.
Ensure that any functionality that requires dragging can also be performed using a simpler, single-point action. This helps users who cannot drag items or perform complex movements.
Make sure that all interactive controls (like buttons and links) are large enough or spaced adequately so that they are easy to activate, even for users with physical impairments who may struggle with small or closely placed targets.
• Targets must be at least 24 by 24 CSS pixels.
• If targets are smaller than 24 by 24 pixels, they should be spaced so that they do not overlap when a 24-pixel diameter circle is centered on each.
• Alternatives are provided if targets are smaller than the minimum size.
Clearly identify when sections of text within a web page are in a language different from the default language, so assistive technology can present the information correctly.
• The language of each passage or phrase within the content is specified, except for proper names, technical terms, indeterminate words, and adopted vernacular phrases.
Ensure that navigation elements that repeat across multiple pages maintain the same order and placement to facilitate predictable user interaction.
• Navigation elements that appear on multiple pages should have a consistent order and location unless the user explicitly changes it.
Ensure that elements with the same function are identified consistently across all pages to make interactions predictable.
• Components with identical functions should have consistent labels, icons, and accessibility attributes across all pages.
When users make an error, offer suggestions on how to correct it to help them resolve issues quickly.
• When an error is detected, provide specific suggestions on how to fix the issue.
• Suggestions should be clear, actionable, and relevant to the error encountered.
• Avoid providing suggestions if it compromises security or the purpose of the content.
Ensure users have the ability to review, correct, or reverse important actions to prevent errors in legal, financial, or data-related submissions.
For actions that involve legal commitments, financial transactions, or data changes, implement at least one of the following measures:
• Reversible: Allow users to undo or reverse their actions.
• Checked: Validate user input for errors and provide options to correct them.
• Confirmed: Provide a mechanism to review, confirm, and correct information before finalizing the submission.
Ensure that authentication processes do not rely on cognitive tasks, like solving puzzles or remembering complex information, to make login easier for everyone.
Authentication processes must not require users to solve puzzles, remember passwords, or transcribe codes unless:
• Alternative Method: An alternative authentication method is provided that does not rely on cognitive tasks.
• Assistance Mechanism: There is a mechanism to assist users in completing the cognitive task.
• Object Recognition: The cognitive task involves recognizing objects.
• Personal Content: The task involves identifying non-text content that the user has previously provided.
Ensure that important status messages are communicated to users through assistive technologies even when they do not receive focus, so all users are aware of content updates.
• Programmatically Determined: Status messages must be programmatically detectable through roles or properties.
• Assistive Technology Notification: Status updates should be announced to users by assistive technologies without requiring focus to be shifted.
Ensure that all prerecorded videos include sign language interpretation for audio content, so that people who are deaf or hard of hearing can access the content in their preferred mode of communication.
• Sign Language Interpretation Required: Provide a sign language interpretation for all prerecorded audio content in synchronized media.
• Scope: Sign language interpretation should be available for all prerecorded audio in time-based media.
Ensure that prerecorded videos include extended audio descriptions that offer detailed spoken descriptions of visual content, especially when standard audio descriptions are not sufficient.
• Extended Audio Description Required: Provide extended audio descriptions for prerecorded videos where regular pauses in the audio are insufficient to describe the visual content adequately.
• Alternative Version: Offer an alternative version of the video that includes extended audio descriptions. This version should temporarily pause the main audio (and video) to allow detailed descriptions to be provided between dialogue.
Provide a text-based alternative for all prerecorded video content to ensure that people who are deaf-blind or prefer reading can access the information at their own pace.
• Text Alternative Required: Offer a text equivalent for all prerecorded synchronized media and prerecorded video-only content.
• Scope: The text alternative must be different from captions or a transcript and should fully convey the information presented in the video.
Ensure that live audio-only content includes a text-based alternative so that people who are deaf or hard of hearing can access the information in real time.
• Text Alternative Required: Provide a text equivalent for all live audio-only content.
• Scope: The text alternative should deliver the same information as the live audio, making it accessible for individuals who cannot hear or understand the audio.
Clearly define the purpose of all controls, icons, and key regions on a page using code. This helps users understand their function, especially those with cognitive disabilities who might find it challenging to interpret controls based on names alone.
• Programmatic Identification: Ensure that the purpose of user interface components, icons, and regions can be programmatically determined using appropriate code or attributes.
• Clear Meaning: Use ARIA roles, landmarks, or other markup techniques to describe the purpose and function of key elements on the page.
Provide strong contrast between text and its background to ensure readability for users who need higher contrast levels.
• Contrast Ratio: Text and images of text must have a contrast ratio of at least 7:1 against their background.
• Large Text: Large-scale text (18px or larger) must have a contrast ratio of at least 4.5:1.
• Incidental Text: Text or images of text that are decorative, part of inactive UI components, not visible, or part of a picture with significant other visual content are exempt from contrast requirements.
• Logotypes: Text within logos or brand names does not need to meet the enhanced contrast ratio.
Ensure that prerecorded audio primarily containing speech is clear and not disrupted by background sounds.
For prerecorded audio-only content that features primarily speech (excluding audio CAPTCHAs, audio logos, or musical vocalizations), one of the following must apply:
• No Background: The audio does not contain any background sounds.
• Turn Off: Background sounds can be turned off by the user.
• 20 dB Lower: Background sounds are at least 20 decibels lower than the foreground speech, except for brief, occasional sounds lasting only 1-2 seconds.
Allow users to adjust text appearance to meet their preferences or needs for better readability and accessibility.
For blocks of text, one or more of the following must be possible:
• Color Customization: Users can select foreground and background colors.
• Width Limitation: Text width is limited to no more than 80 characters or glyphs per line (40 characters for CJK languages).
• Text Alignment: Text is not justified (aligned to both left and right margins).
• Line and Paragraph Spacing:
• Line spacing (leading) is at least 1.5 times the font size within paragraphs.
• Paragraph spacing is at least 1.5 times larger than the line spacing.
• Text Resizing: Text can be resized up to 200% without requiring horizontal scrolling.
Ensure users can adjust text presentation by avoiding images of text unless essential for style or decoration. Use text whenever possible for content, as images cannot be resized or reformatted, limiting accessibility.
Use Images of Text only when:
• Decorative: The text is used purely for decoration and does not convey critical information.
• Essential Presentation: The specific presentation of text is essential for conveying meaning (e.g., logotypes or certain branding elements).
Ensure that every action available with a mouse can also be performed using a keyboard, without needing specific timings for keystrokes.
• Keyboard Operation: All functionalities must be operable using a keyboard.
• No Timing Requirements: Functions should not require specific timing or sequences of keystrokes.
Avoid using time limits for tasks and interactions, unless required for non-interactive media or real-time events.
• No time limits are imposed for tasks or interactions, except for synchronized media (e.g., video) or real-time events.
Allow users to postpone or suppress interruptions, except for emergencies, to avoid disruptions.
• Users can delay or turn off interruptions, except in emergencies.
Ensure that users do not lose their activity or data when their session expires and they need to re-authenticate. This helps users who may require more time to complete their tasks.
• Users can continue their activity and retain their data after re-authenticating if their session expires.
Notify users about the duration of inactivity before they risk losing data, unless data is preserved for more than 20 hours of inactivity. This ensures users are aware of how long they have to complete actions.
• Users are warned about the duration of inactivity that could lead to data loss, unless data is preserved for more than 20 hours.
Ensure content does not flash more than three times per second to prevent triggering seizures or other health issues, protecting users who are sensitive to rapid flashing.
• Content flashes no more than three times per second.
Allow users to disable or minimize motion and animations triggered by their interactions, based on their preferences. This helps prevent motion-induced discomfort and ensures a more comfortable experience for those sensitive to motion effects.
Provide headings to clearly delineate different sections of content. This helps users, especially those with cognitive or visual disabilities, to navigate and understand the structure of the content.
• Headings are used to separate and organize content into distinct sections.
• Headings can be titles or other forms of content labels.
When a user interface component receives keyboard focus, it must be completely visible without any part of it being obscured by other content or off-screen. This allows users who rely on keyboard navigation to see the entirety of the focused element and interact with it effectively.
• No part of the component that receives keyboard focus should be covered by other content or be out of view.
• Ensure that the component is fully visible within the viewport, without requiring the user to scroll or adjust the view to see it.
When an element receives keyboard focus, the focus indicator must be clearly visible. This makes it easier for users to locate and interact with the focused element, especially those with visual impairments or older adults.
• The focus indicator is at least as wide as a 2 CSS pixel thick border of the unfocused component.
• The focus indicator has a contrast ratio of at least 3:1 between its focused and unfocused states.
Provide clear indicators, such as breadcrumbs, site maps, or other navigation aids, to show users their location within a set of web pages. This helps users understand their context and navigate more effectively, especially those with cognitive disabilities.
Users can always identify their current location within the site’s structure through visible navigational aids.
Ensure that each link has descriptive text that clearly indicates where the link will lead or what action it will perform. This helps all users, particularly those using assistive technologies, understand link purposes without needing additional context.
The purpose of each link can be determined from the link text alone. The text should be clear and informative, avoiding ambiguity.
Make custom interactive targets (such as buttons and links) at least 44 by 44 CSS pixels to accommodate users who have difficulty tapping small objects.
• Interactive targets must be at least 44 by 44 CSS pixels in size.
Allow users to use various input methods simultaneously and do not restrict them to just one type of input. This ensures everyone can interact with content using the input method that suits them best, whether it’s a mouse, keyboard, touch screen, voice commands, or assistive devices.
• Users can switch between different input methods (like mouse, keyboard, touch, or voice) without restrictions.
• Input methods should not be limited unless it is necessary for security reasons, to follow user settings, or if the restriction is essential for specific functionality.
Ensure that definitions or explanations are available for technical terms, jargon, or unusual words used in content to help users understand them better.
• A clear mechanism is provided to access definitions for words or phrases that are used in an unusual way, including technical jargon, idioms, or specialized terms.
Ensure that users can easily find the full meaning of abbreviations used on a page.
A clear method is available to view the expanded form or full meaning of any abbreviations used in the content.
Ensure that content is accessible to users with lower reading skills by offering simplified versions or alternative formats.
• When text exceeds the reading level of lower secondary education (approximately 9 years of schooling), provide an alternative version that is easier to understand.
• Alternatively, offer supplemental content such as audio, illustrations, or a summary that conveys the same information in a simpler form.
Ensure users can understand how to pronounce words when their meaning is unclear from context alone.
• Provide a clear mechanism for users to learn the pronunciation of words when it is necessary to understand their meaning.
Allow users to control when major changes to content or context occur, ensuring changes are not automatic.
• Major content or context changes should only occur in response to a user action or request.
• Provide a mechanism to turn off automatic changes if they are triggered by user actions.
Provide users with accessible and relevant help based on their current task to assist them in completing their actions accurately.
• Context-sensitive help is available for users while they are performing tasks, offering relevant information or guidance.
Ensure users have the ability to review, correct, and undo their submissions to prevent mistakes and ensure accurate information entry.
At least one of the following mechanisms must be available for pages where users submit information:
• Reversible: Submissions can be undone.
• Checked: Data entered by the user is validated for errors, and users can correct these errors.
• Confirmed: Users can review and confirm their information before finalizing the submission.
Ensure authentication processes avoid requiring users to recognize objects or media, making it easier for those with cognitive disabilities.
If cognitive function tests (CAPTCHA's for example) are used, they must be accompanied by: