Explore WCAG 3.0

Non-decorative images are detectable.

Applies when content includes non-decorative images.

Decorative images are programmatically hidden.

Text alternatives are available for non-decorative images.

Text alternatives for non-decorative images convey the equivalent purpose to the image.

All non-text content that is not decorative includes a programmatically determinable equivalent text alternative.

A text transcript is adjacent to audio and video content.

Except when

• The audio or video content has no spoken dialogue.
• The audio or video is decorative.
• The media is already a media alternative for text and is clearly labeled as such.

Dialogue transcripts are available for all prerecorded audio and video content.

Except when

• The audio or video content is an alternative for text and is clearly labeled as such.
• The audio or video has no spoken content and serves only as background.

Dialogue transcripts are available for all live audio and video content.

Except when

• The audio or video content is an alternative for text and is clearly labeled as such.
• The audio or video has no spoken content and serves only as background.

Equivalent transcripts are available for audio and video content.

Except when the audio or video has no spoken content and serves only as background.

Descriptive transcripts are provided for prerecorded audio and video content.

Except when

• The media is purely decorative.
• The media is already a media alternative for text and is clearly labeled as such.
• The visual track includes no information that is not already conveyed in the audio track (for example, a “talking head” video where only the speaker is visible against a static background).

Speakers are identified understandably within all transcripts.

Applies when there are multiple speakers in the video.

Except when

• The speaker has a hidden identity as part of narrative structure.
• Identity is identifiable within the context of use.

When more than one language is spoken in audio content, the language spoken by each speaker is identified in all transcripts.

Except when words are used incidentally.

Sounds needed to understand the media are identified or described in transcripts.

Applies when there is sound.

Except when the video is decorative.

Visual information needed to understand the media is described in transcripts.

[Title, role, or organization] asserts that:

• Our organization has a style guide that includes guidance on transcripts and a policy and/or processes that the style guide must be followed.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the style guide was published
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• summary of the needs of users involved
• identified issues and details of solutions applied
• copy or snapshot of the style guide

[Title, role, or organization] asserts that:

• We have conducted usability testing with users who need transcripts, and changes were made to fix or mitigate the issues found.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the usability testing was conducted
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• scope
• types of disabilities each user had
• number of users (for each type of disability)
• date of testing
• identified issues and details of solutions applied

[Title, role, or organization] asserts that:

• We have reviewed the transcripts.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of the review
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• role of the creator
• number of creators (for each Role)
• date (Period) of review
• examples of fixed issues based on the review

The appearance of captions, including associated visual indicators, is adaptable including font size, font weight, font style, font color, background color, background transparency, and placement.

Captions are available for all prerecorded audio content.

Except when the audio content is an alternative for text and is clearly labeled as such.

Equivalent captions are available for audio and video content.

Except when the audio or video has no spoken content and serves only as background.

Captions are available for all live audio content.

A mechanism is available that allows users to change the caption language if multiple languages are available.

A mechanism is available to turn captions on and off.

Except when captions are hard-coded into the video content.

Captions are placed on the screen so that they do not hide visual information needed to understand the video content.

Captions are synchronized with the audio content of synchronized media.

In 360-degree digital environments, captions remain directly in front of the user.

Applies when the position of the captions is controlled by the user.

In 360-degree digital environments, the direction of a sound or speech is indicated when audio is heard from outside the current view.

Speakers are identified understandably within all captions.

Applies when there are multiple speakers in the video.

Except when

• The speaker has a hidden identity as part of narrative structure.
• Identity is identifiable within the context of use.

When more than one language is spoken in audio content, the language spoken by each speaker is identified in all captions.

Except when words are used incidentally.

Sounds needed to understand the media are identified or described in captions.

Applies when there is sound.

Except when the video is decorative.

[Title, role, or organization] asserts that:

• Our organization has a style guide that includes guidance on captions and a policy and/or processes that the style guide must be followed.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the style guide was published
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• summary of the needs of users involved
• identified issues and details of solutions applied
• copy or snapshot of the style guide

[Title, role, or organization] asserts that:

• We have conducted usability testing with users who need captions, and changes were made to fix or mitigate the issues found.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the usability testing was conducted
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• scope
• types of disabilities each user had
• number of users (for each type of disability)
• date of testing
• identified issues and details of solutions applied

[Title, role, or organization] asserts that:

• We have reviewed the captions.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of the review
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• role of the creator
• number of creators (for each Role)
• date (Period) of review
• examples of fixed issues based on the review

Audio descriptions are available in prerecorded video for visual content needed to understand the media.

Except when the video content is an alternative for text and is clearly labeled as such.

The information conveyed by audio descriptions is equivalent to the visual content needed to understand the media.

Audio descriptions are synchronized with video content without overlapping dialogue and meaningful audio content.

Except when there are no audio descriptions.

Audio descriptions are available in live video for visual content needed to understand the media.

The video pauses to extend the audio track and provides an extended audio description to describe visual information needed to understand the media.

Applies when the existing pauses in a soundtrack are not long enough.

The information conveyed by extended audio descriptions is equivalent to the visual content needed to understand the media.

A mechanism is available that allows users to change the audio description language if multiple languages are available.

A mechanism is available to turn audio descriptions on and off.

Except when audio descriptions are hard-coded into the audio or video content.

Speakers are identified understandably within all audio descriptions.

Applies when there are multiple speakers in the video.

Except when

• The speaker has a hidden identity as part of narrative structure.
• Identity is identifiable within the context of use.

When more than one language is spoken in audio content, the language spoken by each speaker is identified in all audio descriptions.

Except when words are used incidentally.

Sounds needed to understand the media are identified or described in captions and transcripts.

Applies when there is sound.

Except when the video is decorative.

Visual information needed to understand the media is described in audio descriptions.

[Title, role, or organization] asserts that:

• Our organization has a style guide that includes guidance on audio descriptions and a policy and/or processes that the style guide must be followed.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the style guide was published
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• summary of the needs of users involved
• identified issues and details of solutions applied
• copy or snapshot of the style guide

[Title, role, or organization] asserts that:

• We have conducted usability testing with users who need audio descriptions, and changes were made to fix or mitigate the issues found.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the usability testing was conducted
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• scope
• types of disabilities each user had
• number of users (for each type of disability)
• date of testing
• identified issues and details of solutions applied

[Title, role, or organization] asserts that:

• We have reviewed the audio descriptions.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of the review
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• role of the creator
• number of creators (for each Role)
• date (Period) of review
• examples of fixed issues based on the review

Sign language interpretation is provided for all prerecorded audio content in the primary sign language that is most appropriate for each intended audience or region.

Except when

• The audio content is an alternative for visual content and is clearly labeled as such.
• The audio content is decorative background sound.
• The audio is an interface sound effect.

A mechanism is available to show and hide sign language interpretation.

Except when

• Sign language interpretation is hard-coded into the video content.
• A sign language interpreted version is provided as a separate video.

[Title, role, or organization] asserts that:

• Our organization has a policy to provide sign language interpretation for live in-person, hybrid, and fully online events/meetings.

Information that needs to be included publicly:

• title, role, or organization making the assertion (with contact information)
• date of assertion (if different from the date of the conformance claim)
• date the policy was last reviewed/updated
• how sign language interpretation can be requested
  • format: email, phone, contact form
  • timeline/deadline for requesting (maybe just the average timeline)

Recommended internal documentation (Informative):

• approved vendors and contact information
• steps for hosting on each platform used
• versioned communications guide for announcing sign language availability for each meeting/event

Information is not conveyed by hue alone.

Except when

• Content is artistic or expressive.
• Content is designed only for a device that is limited to presenting hues.

Parts of graphical objects required to understand the content meet a minimum contrast ratio test

Except when a particular presentation of graphical objects is essential to the information being conveyed.

Information is not conveyed through visual depth perception alone.

Information is not conveyed by sound alone.

Except when content is audio-based media.

Information is not conveyed by spatial audio alone.

[Title, role, or organization] asserts that:

• We provide a video player that supports appropriate media alternatives. The video player includes the following features [list all that apply]:
  • supports closed captions in a standard caption format
  • turning captions on and off
  • turning audio descriptions on and off
  • adjusting caption styles, including but not limited to: font size, font weight, font style, font color, background color, background transparency, and placement
  • changing the location of captions
  • changing the language of the audio descriptions

Applies when a video is used that does not play in standard browsers.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of assertion (if different from the date of the conformance claim)
• feature included from the list

Recommended internal documentation (Informative):

• video player documentation detailing functional support for media alternatives

[Title, role, or organization] asserts that:

• We provide an audio player that supports appropriate media alternatives. The audio player includes the following features [list all that apply]:
  • turning audio descriptions on and off
  • changing the language of the audio descriptions

Applies when an audio format is used that does not play in standard browsers.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of assertion (if different from the date of the conformance claim)
• feature included from the list

Recommended internal documentation (Informative):

• audio player documentation detailing functional support for media alternatives

The default/authored presentation of blocks of text meets the minimum @@ [values to be determined] for:

• inline margin
• block margin
• line length
• line height

The default/authored presentation of text style property meets the minimum @@ [values to be determined] for:

• typeface
• font size
• font width
• text decoration
• letter spacing
• capitalization
• end-of-line hyphenation

The default visual presentation of text meets @@[contrast measure to be determined].

Applies when text is presented, including text embedded in an image format.

Except when the text is:

• also present elsewhere in the page/view which meets the requirement
• part of an inactive interactive element
• pure decoration
• not visible to anyone
• part of a picture that includes significant other visual content
• part of a logo or brand name

The presentation of blocks of text can be adjusted, without loss of content or functionality, to meet the @@ [values to be determined] for:

• inline margin
• block margin
• line length
• line height
• justification

Except when the style attribute is hard-coded, such as raw text that is capitalized or hyphenated.

The presentation of text style properties can be adjusted, without loss of content or functionality, to meet the @@ [values to be determined] for:

• typeface
• font width
• text decoration
• capitalization
• automatic end-of-line hyphenation

Except when the text style property is hard-coded, such as raw text that is capitalized or hyphenated.

Text can be increased in size to at least 200% of the platform’s default body-text size.

Except when the same text is available elsewhere in the page/view which can be increased to at least 200% of the platform’s default body-text size.

The foreground and background color of text can be adjusted without losing content or functionality.

Applies when text is presented, including text embedded in an image format.

Except when the text is:

• also present elsewhere in the page/view which meets the requirement
• part of an inactive interactive element
• pure decoration
• not visible to anyone
• part of a picture that includes significant other visual content
• part of a logo

The default/authored presentation of blocks of text meets the enhanced @@ [values to be determined] for:

• inline margin
• block margin
• line length
• line height

The default/authored presentation of text style properties meets the enhanced @@ [values to be determined] for:

• typeface
• font size
• font width
• text decoration
• letter spacing
• capitalization
• end-of-line hyphenation

The default visual presentation of text meets @@[contrast measure to be determined, at a higher level than the core requirement for Text contrast sufficient (minimum)].

Applies when text is presented, including text embedded in an image format.

Except when the text is:

• also present elsewhere in the page/view which meets the requirement
• part of an inactive interactive element
• pure decoration
• not visible to anyone
• part of a picture that includes significant other visual content
• part of a logo

Content that is exported, saved, or printed retains user-applied text-appearance customizations.

Applies when the page/view can be exported, saved, or printed.

All visible text has a programmatically determinable equivalent.

Except when making visible text programmatically determinable would lead to duplication within the view.

The human language of all content within the view is programmatically determinable.

Except when

• A language tag is not available in [iso-639-2023], or
• The technology used to create the view does not support indicating languages.

Numerical information includes sufficient context in written text and a programmatic equivalent to avoid confusion when presenting dates, temperatures, time, and Roman numerals.

Explanations of abbreviations are available when first used.

Except when the abbreviation is:

• used so often it has become a word with its own dictionary entry, such as “scuba,” “info,” and “HTML”,
• used in a logo, or
• included in a longer phrase, such as “brand DNA,” whose meaning needs to be defined to meet the non-literal language requirement.

Explanations or unambiguous alternatives are available in text content for non-literal language, such as idioms and metaphors.

Except when text content is:

• poetic,
• scriptural,
• artistic, or
• expressive rather than informational.

A summary is available for long-form text content and:

• is identifiable visually and programmatically,
• uses concise sentences, and
• provides access to explanations of any uncommon words that are used in the summary.

Applies when a page/view with continuous long-form text content that is organized in paragraphs and has 300 or more words.

Except when long-form text content continues on multiple pages/views, only the first page/view requires a summary.

Common words are used, and definitions are available for uncommon words.

Applies when human languages have more than 1,500 words.

Except when

• the words are for names of people or places, or
• the language does not have a high-frequency corpus.

Diacritics required to identify the correct meaning of each word are available.

Applies when a human language has a version that removes diacritics for proficient readers.

Sentences do not include nested clauses.

Except when text content:

• is poetic, scriptural, artistic, or expressive rather than informational, or
• provides legal information.

Sentences do not include unnecessary words.

Except when text content is:

• poetic,
• scriptural,
• artistic, or
• expressive rather than informational.

[Title, role, or organization] asserts that:

• Our organization has a process and policy to review text content for clear language before publication. The process includes confirming:
  • All of the core requirements in the ‘Clear Language’ guideline are met.
  • Verb tense is chosen for ease of understanding.
  • Content uses short paragraphs.
  • Paragraphs that convey information begin with a sentence stating the main point or purpose (often called a topic sentence).
  • If a style guide is used by content authors, it must provide guidance on these aspects of clear language.
  • If author training is provided, it must provide guidance on these aspects of clear language.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the policy was implemented
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• copy of the policy implementing the clear language review
• date author training was provided (if any)
• number or proportion of authors who completed the training
• copy of the style guide (if any) where clear language review has been defined

[Title, role, or organization] asserts that:

• Our organization has a process and policy for reviewing text content to identify complex ideas such as processes, workflows, relationships, or chronological information, and adding visual aids to help readers understand them.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the policy was implemented
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• copy of the policy implementing the use of visual aids
• date author training was provided (if any)
• number or proportion of authors who completed the training
• copy of the style guide (if any) where visual aids have been defined

The focusable item uses the user agent default focus indicator.

If a custom focus indicator is used, it has sufficient adjacent contrast and change of contrast.

Applies when the user agent’s default focus indicator is replaced by a custom focus indicator.

If a custom focus indicator is used, it has sufficient size and adjacency.

Applies when the user agent’s default focus indicator is replaced by a custom focus indicator.

[Title, role, or organization] asserts that:

• Our organization has a style guide that includes guidance on focus indicators and a policy and/or processes that the style guide must be followed.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the design style guide was published
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• copy of the policy implementing the use of design style guide on focus style
• whether training was provided for authors
  • date training was provided
  • number or proportion of authors who completed the training
• copy of the design style guide (if any) where focus style has been defined

There is a visible indication of the activation of an interactive element when selected by the pointer.

Applies when the platform does not use a visible pointer indicator.

The user can choose to always have a visible pointer indicator.

Applies when the platform does not use a visible pointer indicator.

The default pointer meets the @@[non-text-contrast] requirement, and is at least as large as the platform default.

Applies when the pointer indicator appearance can be adjusted from the platform default.

The user can ensure that the appearance of the pointer is not overridden by the authored interface.

Except when changing the pointer appearance is essential.

There is a visible pointer indicator.

Except when

• The pointer is on a video - it can be hidden if there is a pointer mechanism to un-hide the pointer indicator.
• The pointer controls the direction of view in a virtual or real world environment.

The pointer indicator is always visible.

Except when

• The pointer is on a video and is not moving.
• The pointer controls the direction of view in a virtual or real world environment.

Provide a more visible pointer indicator than the platform default. The enhanced pointer indicator can be enabled in a setting, and be visible temporarily (for a few seconds) or permanently.

The focus order does not include hidden, static, or groups of repeated interactive elements.

A user can focus on a content “area”, such as a modal or popup, then resume their view of all content using a limited number of steps.

The keyboard focus moves sequentially through content in an order and way that preserves meaning and operability.

[Title, role, or organization] asserts that:

• A review has been conducted and changes made (when necessary) to ensure that Components with the same functionality behave consistently:
  • Components that perform the same function behave in the same way and use the same visual indicators.
  • Within the component, interactive elements with the same function have consistent labels.
  • Standard user interface designs for the platform are used when applicable.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the review was completed
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• results from the review
• process or policy for maintaining the review

Where an interactive element with the same purpose is used across pages/views, its visual position in the layout is maintained.

Except when

• The location changes due to a page variation or viewport change, or
• The layout changes due to being part of a process.

[Title, role, or organization] asserts that:

• A review has been conducted and changes made (when necessary) to ensure that Components follow established conventions:
  • Each component follows applicable platform conventions for how users interact with that type of component.
  • If a component library is used, then each component in the library:
    • is tested for accessibility before being used
    • follows applicable platform conventions for how users interact with that type of component

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the review was completed
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• results from the review
• process or policy for maintaining the review

Visual information required to identify interactive elements and states meet a minimum contrast ratio test.

Except when

• The interactive element is inactive, or
• The appearance of the component is determined by the user agent and not modified by the content author.

Persistent names (including labels) that identify the purpose of the interactive element are visually and programmatically available.

Changes to interactive element names, roles, values, or states are visually and programmatically indicated.

Field constraints and conditions are available.

The programmatic name includes the visual label.

Accurate names, roles, values, and states are available for interactive elements.

All components on the page/view that can be operated by pointer, audio (voice or other), gesture, camera, or other means can be operated using keyboard interface only.

All content that can be accessed by other input modalities can be accessed using keyboard interface only.

The keyboard interface can always move forward to the next interactive element and back to the previous interactive element.

Documentation for each custom keyboard command is actively available on the page/view to which it applies, or within the applicable process.

Custom keyboard commands do not conflict with standard platform keyboard commands or they can be remapped.

When keyboard focus moves from one context to another within a page/view, whether automatically or by user request, the keyboard focus is preserved so that, when the user returns to the previous context, the keyboard focus is restored to its previous location unless that location no longer exists.

Components that can be activated or entered using the keyboard interface, can be deactivated or exited using a standard keyboard navigation-operation technique, standard platform keyboard commands.

Except when the non-standard keyboard navigation technique is described in the page/view or earlier in the process.

The keyboard focus only moves as a result of user interaction.

Except when

• The keyboard focus automatically moves to the next interactive elements in keyboard navigation order on completion of some user action, such when the focus moves between the fields for a time-based one-time password (TOTP) code.
• The keyboard focus results from security or emergency situations, such as warning about an imminent session timeout that would cause the user to lose their work.
• The user is informed of the potential keyboard focus move before it happens and given the chance to avoid the move.

Except for skip links and other elements that are hidden but specifically added to aid keyboard navigation, tabbing does not move the keyboard focus onto content that was not visible before the tab action.

If any keyboard action needed to navigate, perceive, and operate the full content of the page/view is not a common keyboard navigation technique, then it is described in the page/view where it is required or on a page/view earlier in the process where it is used.

Adjacent interactive elements that achieve the same outcome are not included in the page/view.

Except when that outcome is a form of dismissal.

[Title, role, or organization] asserts that:

• A review has been conducted and changes made (when necessary) to ensure that there is minimal difference between the number of input commands required when using the keyboard interface only and the number of commands when using other input modalities.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the review was conducted
• date of assertion (if different from the date of the conformance claim)
• scope of assertion (if different from the conformance claim)

Recommended internal documentation (Informative):

• copy of the review implementing the use of user interface design principles that include minimizing the difference between the number of input commands required when using the keyboard interface only and the number of commands when using other input modalities
• whether training was provided for authors
• date training was provided
• number or proportion of authors who completed the training
• copy of the user interface design principles document

At least one of the following is true for functionality that can be activated using a simple pointer input:

No down event

The down event of the pointer is not used to execute any part of the function.

Cancel or undo

Completion of the function is on the up event and a mechanism is available to cancel the function before completion, or there is a mechanism to undo the function after completion.

Up reversal

The up event reverses any outcome of the preceding down event.

Except when completing the function on the down event is essential.

All functionality and content available using complex pointer inputs is also available using a simple pointer input, or a sequence of simple pointer inputs that do not require timing.

The method of pointer cancellation is consistent for each type of interaction within a set of pages/views.

Except when it is essential to be different.

Specific pointer pressure is not the only way of achieving any functionality.

Except when specific pressure is essential to the functionality.

Functionality does not rely solely on specific pointer speed.

Except when specific pointer speed is essential to the functionality.

Content or functionality does not rely on speech alone.

Except when speech input is essential to the functionality.

A real-time text option is available for real-time bidirectional voice communication.

[Title, role, or organization] asserts that:

• We have tested voice input and communication systems with generated speech to ensure the systems work with artificial speech as well as human speech.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the policy was implemented
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• systems tested
• accuracy rates

A mechanism is available to dismiss content that appears on pointer hover or keyboard focus without moving pointer hover or keyboard focus, unless the additional content does not obscure or replace other content.

Applies when receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, and the visual presentation of the additional content is controlled by the author and not by the user agent.

If pointer hover can trigger content, then the pointer can be moved over the additional content without the additional content disappearing.

Applies when receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, and the visual presentation of the additional content is controlled by the author and not by the user agent.

Content that appears on pointer hover or keyboard focus remains visible until the hover or keyboard focus trigger is removed, the user dismisses it, or its information is no longer valid.

Applies when receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, and the visual presentation of the additional content is controlled by the author and not by the user agent.

Path-based gestures are not the only way of achieving any functionality.

Except when a path-based gesture is essential to the functionality.

The ability to switch between input methods is available at any time.

Functionality does not rely solely on full or gross body movement.

Except when full or gross body movement is essential to the functionality.

Content and functionality does not rely solely on eye tracking.

Except when eye tracking is essential.

Pointer selection of elements moves the keyboard focus to that element, even if the user selects an interactive element and drags away from the element without activation.

Applies when content can interfere with pointer or keyboard focus behavior.

Biometric identification is not the only way to identify or authenticate.

Voice identification is not the only way to identify or authenticate.

Errors that are programmatically determined are identified and the problem is described to the user in text.

Error messages include suggestions for corrections.

Applies when errors require corrections by the user.

Except when including suggestions would jeopardize the security or purpose of the content.

Error messages are visually indicated using at least two of the following:

• a symbol that is consistent throughout the conformance scope
• color that differentiates the error message from surrounding content
• a textual indication

Error messages persist at least until the error is resolved or the user dismisses them.

When input validation fails, the errors are visually and programmatically associated with the element that caused the error or that can resolve it.

Error messages are visually collocated with the error source or the focus is moved to the error message and a mechanism is available to move to the input that is in error.

Applies when error messages relate to user input.

Data entry interfaces allow for users to do at least one of the following before submission:

• Review, confirm, and correct all information.
• Review and correct input errors found during validation.

Except when entered data is auto-saved and/or reversible.

Data entry interfaces notify users of submission status at the time of submission.

Applies when data submission has succeeded or failed.

Data entered is validated after the user enters data, either:

• when the user leaves the field, or
• when the form is submitted

[Title, role, or organization] asserts that:

• For each form in the conformance claim, we have reviewed the form designs to reduce the possibility of users making mistakes.

This review includes checking to make sure that we:

• Make the user enter as little information as possible.
• Clearly indicate required fields.
• For long numbers, divide input fields into chunks (supporting autocomplete across fields).
• Use an interface where only valid input can be selected.
• Use autocomplete and personalization of form controls.
• Use common words and metrics or units that users are likely to be familiar with.
• Automatically correct input errors when possible and reliable.
• Provide the user with known suggestions and corrections.

Information that needs to be included publicly:

• title, role, or organization making the assertion
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• documentation of which forms were reviewed
• documentation of any changes made as a result of the review
• date of usability testing, if applicable

Flashes are below the general flash and red flash thresholds.

Applies when content includes flashes.

Except when the flashing is essential.

Flashes are below the general flash and red flash thresholds without a minimum size.

Applies when content includes flashes.

Content does not include pseudo-motion or visual motion lasting longer than 5 seconds.

Except when the motion or pseudo-motion is essential.

Content does not include pseudo-motion or visual motion lasting longer than 5 seconds.

A warning is provided before users encounter triggers and a mechanism is available to access the same information without the triggering content.

Applies when triggers are present.

Haptic feedback can be reduced or turned off.

Applies when content triggers haptic feedback.

Except when the operating system or user agent converts non-haptic feedback to haptics at user request.

Audio shifting designed to create a perception of motion can be paused or turned off.

Applies when content includes audio shifting.

Except when operating system or user agent triggers audio shifting.

[Title, role, or organization] asserts that:

• We have reviewed content for violent, explicit, or troubling content and provided appropriate warnings before accessing the content.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the review was conducted
• date of assertion (if different from the date of the conformance claim)

[Title, role, or organization] asserts that:

• We have reviewed layout conventions for similar products or processes.
• The layout used follows a conventional pattern or a tested non-conventional pattern was used.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• report covering review of layouts for similar products or processes
• design log capturing decision to use specific layouts
• if a non-conventional layout is used, usability testing results that demonstrate the utility of the approach taken

The page/view has a title that describes its name, topic, or purpose.

Except when the technology has no way to include a title.

[Title, role, or organization] asserts that:

• We have reviewed conventions for presenting current location within the conformance scope.
• The presentation of current location within the conformance scope uses appropriate visually and programmatically patterns.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• design log capturing decision to use specific approaches to current location patterns used within the conformance scope
• if a non-conventional design pattern is used, usability testing results that demonstrate the utility of the design approach taken

A list of all steps in a multi-step process is visually and programmatically available at each step.

Except when the total number of steps is unknown, or the sequence of steps depends on user actions.

The current step within a multi-step process is visually and programmatically indicated.

When content triggers a change of page/view there is a visual change within the view and programmatic notification of the change.

A visual and programmatically available mechanism exists that allows users to return to the starting point of the conformance scope.

Except when

• The page/view is the starting point of the conformance scope.
• It is essential to the functionality not to provide this mechanism.

Mechanisms that return the user to the starting point of the conformance scope are available in prominent positions both programmatically and visually.

Relationships of meaning between elements are conveyed programmatically.

Meaningful blocks of content are programmatically determinable and visually presented with sufficient surrounding space.

Meaningful blocks of content have a semantically appropriate label that defines their purpose.

Except when a label is not needed to understand the purpose of the content within the context of use.

Meaningful blocks of content are organized with a logical hierarchy of headings.

Except when the technology does not support heading levels.

Ordered content includes programmatically determinable markers that indicate the position of each item.

Except when the nature of the ordering of the content is presented immediately prior.

Styling is used to enhance the visual separation between meaningful blocks of content.

[Title, role, or organization] asserts that:

• Our organization has a process and policy for reviewing written content for clear structure before publication. The process includes confirming:
  • all of the core requirements in the Structure guideline are met
  • content sections are as concise as possible
  • icons are considered as possible ways to help users understand the content structure and identify key parts
  • authors consider when to turn sentences into lists to make the information easier to understand and remember
• If a style guide is used by authors, it must provide guidance on these aspects of clear structure.
• If author training is provided, it must provide guidance on these aspects of clear structure.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the policy was implemented
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• copy of the policy implementing the clear structure review
• whether training was provided for authors:
  • date training was provided
  • number or proportion of authors who completed the training
• copy of the style guide (if any) where clear structure review has been defined

[Title, role, or organization] asserts that:

• We conducted usability testing to ensure that a diverse group of users, including people with cognitive and mental health challenges, understand the site’s information hierarchy and menu organization and are able to find key information.

Information that needs to be included publicly:

• title, role, or organization making the assertion
• date of assertion
• date of the testing

Recommended internal documentation (Informative):

• documentation of usability testing and results
• scope of testing
• number of participants and disabilities represented
• documentation of changes made as a result of usability findings

When new content becomes visible and covers the main content, a mechanism is available to dismiss the new content.

The relative order of structural components remains consistent throughout each variation of pages/views in the conformance scope.

Applies when in a set of pages/views.

The relative order of navigation items is consistent within blocks of navigation that are repeated on multiple pages/views of the conformance scope or process.

Applies when in a set of pages/views.

The labeling of navigation items within blocks of navigation that are repeated on multiple pages/views in the conformance scope or process is consistent.

Except when labels for navigation items that are marked as ‘current’ within the conformance scope or process.

Automated input of personal information from user agents, third-party tools, or paste is not prevented.

Processes can be completed without a cognitive function test.

A mechanism exists to extend the time limit before timeout, or the time limit can be disabled.

Applies when time limit(s) exist.

Except when the time limit is essential.

The completion of a process does not include time limits.

Except when the time limit is essential.

[Title, role, or organization] asserts that:

• Products and processes in scope have no non-essential time limits for engagement or completion.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of assertion

Users are informed at the start of the process or session that a time limit exists, its length, and that it can be adjusted.

Applies when pages/views within the conformance scope have a time limit.

Except when hiding the existence of the time limit is essential.

During the completion of a process, preselected options that impact finance, privacy or safety are visibly and programmatically available to the user by default.

[Title, role, or organization] asserts that:

• We conducted a usability test that included participants with cognitive disabilities and/or mental health based disabilities to evaluate content for misleading wording, artificial pressure, misdirection, and other deceptive practices.
• We removed any deceptive practices found.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of assertion

Recommended internal documentation (Informative):

• number of participants
• the deceptive practices evaluated
• maintained records of usability testing protocol, and results
• disabilities represented within the group of participants

[Title, role, or organization] asserts that:

• We conducted an expert review to evaluate content for misleading wording, artificial pressure, misdirection, and other deceptive practices.
• We removed any deceptive practices found.

Information that needs to be included publicly:

• title, role, or organization making the assertion
• date of assertion

Recommended internal documentation (Informative):

• the deceptive practices evaluated
• maintained records of deceptive practices found, and resolutions

In a multi-step process, the interface supports stepping backwards in a process and returning to the current point without data loss.

Except when it is essential that the user cannot step back in a process.

Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated, or available for the user to select.

Except when

• Re-entering the information is essential,
• The information is required to ensure the security of the content, or
• Previously entered information is no longer valid.

Data entry and other task completion processes allow saving and resuming from the current step in the task.

Except when the task completion is part of a real-time event, and no alternative to the time limit is possible.

The interface indicates when user input or action is required in order to proceed to the next step.

Applies when the user needs to complete an action in order to proceed to the next step.

Information and resources that are needed to complete a multi-step process are provided at the start of the process, including the:

• number of steps it might take (if known in advance),
• details of any resources needed to perform the task, and
• overview of the process and next step.

Applies when the user needs to complete a multi-step process.

The instructions needed to complete a multi-step process are available.

Applies when the user needs to complete a multi-step process.

[Title, role, or organization] asserts that:

• Usability testing has been conducted to review for unnecessary steps in the process or unnecessary information being requested.
• The sample of test participants included people with cognitive disabilities and/or mental health based disabilities.

Information that needs to be included publicly:

• title, role, or organization making the assertion
• date of assertion

Recommended internal documentation (Informative):

• maintained records of usability testing protocol, scope of the testing, and results
• number of participants and disabilities represented within the group of participants
• record of actions taken to address identified issues

Choices with legal, financial, privacy, or security consequences are accompanied by a description of the benefits, risks, and potential consequences when users make the choice.

Legal, financial, privacy, and security consequences are provided before finalizing an agreement.

Applies when entering an agreement is required.

[Title, role, or organization] asserts that:

• When considering the safety and security of our users, we considered use cases of people with diverse disabilities. For example, people with cognitive or learning disabilities are sometimes targeted on social media for sexual exploitation and other bad intent.
• Research has been conducted on risks to safety, wellbeing, and mental health for users with diverse disabilities and, when risks are found, all reasonable practical steps have been identified and taken to mitigate the risk.

Information that needs to be included publicly:

• title, role, or organization making the assertion
• date of assertion

Recommended internal documentation (Informative):

• list of steps that have been taken
• list of use cases used

[Title, role, or organization] asserts that:

• We have a policy and process to review — and have reviewed — the data set, results, and/or algorithm in order to minimize the possibility that algorithms are disadvantageous for people with disabilities.

Information that needs to be included publicly:

• title, role, or organization making the assertion
• date of assertion
• disabilities considered
• what was reviewed (data set, results, or algorithm itself)
• review scope

Recommended internal documentation (Informative):

• results
• copy of any process and policy
• copy of usability testing, if conducted
• steps taken to resolve the issues found

[Title, role, or organization] asserts that:

• Content author(s) train AI models using representative and unbiased disability-related information that is proportional to the general population.

[Title, role, or organization] asserts that:

• Content author(s) conduct usability testing and ethics reviews to minimize the possibility that algorithms disadvantage people with disabilities.

Help is labeled consistently and is available in a consistent location relative to other content.

Applies when human contact information, a human contact mechanism, a self-help option, or a fully automated contact mechanism is available.

Context-sensitive help is available.

Information explaining why a visible interactive element is disabled is available and, if the user can take action(s) to enable the element, those action(s) are described.

Instructions and help do not rely on sensory characteristics.

[Title, role, or organization] asserts that:

• We have conducted a review to identify when users need to make substantial decisions about money, privacy, or well-being. In these situations, additional support was provided, such as:
  • a clear layout of options advantages and disadvantages
  • aids for comprehension such as icons and graphics
  • reduced distractions

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the policy was implemented
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• results of review
• documentation of decisions and changes made as a result

[Title, role, or organization] asserts that:

• Help and training was added based on usability testing with people with cognitive and mental health disabilities to identify gaps.

Information that needs to be included publicly:

• title, role, or organization making the assertion (if different from the conformance claim)
• date of when the usability testing was conducted
• date of assertion (if different from the date of the conformance claim)

Recommended internal documentation (Informative):

• usability findings
• solutions added

A mechanism is available to provide feedback to authors.

Content can be controlled using assistive and adaptive technology.

Content responds to users’ platform and user agent accessibility-related settings.

Assistive technologies can access content and interactions when using mechanisms that convey alternative points of regard or focus.

The timing or positioning of notifications can be changed, suppressed, or saved.

Applies when notifications or other interruptions are present.

Except when the notification involves an emergency or is essential.

If the platform has a default orientation, content supports that orientation. If the platform does not have a default orientation, content supports both portrait and landscape orientations.

Except when

• Content is aligned with the physical world.
• The orientation is essential.

Content supports both portrait and landscape orientations.

Except when

• Content is aligned with the physical world.
• The orientation is essential.

Blocks of text are legible at 320 CSS pixels in the orientation of text, without the need to scroll in the orientation of text.

Except when the meaning of text relies on a two-dimensional structure.

All content fits within 320 CSS pixels in the default orientation of text without requiring scrolling in more than one direction. Sections of content within the page/view that scroll in a different direction to the page/view fit within 320 CSS pixels of the page-scrolling direction.

Except when

• 2D relationships (for example, tables or electronic program guides)
• canvases of presentational content (for example, slides)
• multiple palettes or panels that act on content (for example, Photoshop or an IDE)

A mechanism is available to pause, stop, and adjust the volume independently of the overall system volume level, of any automatically playing audio in a page/view.

Applies when notifications or other interruptions are present.

Alternatives for media can be searched and queried.

Closed captions and audio descriptions can be turned on and off.

Audio or video that lasts five minutes or longer can be navigated by chapters.

Except when the media is a piece of music that the composer has not divided into movements.

Meaningful changes in visual content are conveyed programmatically.

Applies when

• The changes appear before the user’s current position in reader order.
• The changes appear earlier in the process.
• Notifications, status messages, or error messages appear.
• The amount of content changes.
• The change affects the content’s meaning.
• The audience changes.

Except when changes are continuous, without pause.

When the focus changes on-focus or automatically, the user is notified visually and programmatically.

When content triggers a device change or an automatic user agent change, the user is notified before the change occurs.