W3C Accessibility Guidelines (WCAG) 3.0

W3C Accessibility Guidelines (WCAG) 3.0 will provide a wide range of recommendations for making web content more accessible to users with disabilities. Following these guidelines will address many of the needs of users with blindness, low vision and other vision impairments; deafness and hearing loss; limited movement and dexterity; speech disabilities; sensory disorders; cognitive and learning disabilities; and combinations of any of these disabilities. These guidelines address the accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other Web of Things devices. The guidelines apply to various types of web content, including static, dynamic, interactive, and streaming content; audiovisual media; virtual and augmented reality; and alternative access presentation and control. These guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

Each guideline in this standard provides information on accessibility practices that address documented user needs of people with disabilities. Guidelines are supported by multiple requirements and assertions to determine whether the need has been met. Guidelines are also supported by technology-specific methods to meet each requirement or assertion.

To keep pace with changing technology, this specification is expected to be updated regularly with updates to and new methods, requirements, and guidelines that address new needs as technologies evolve. For entities that make formal claims of conformance to these guidelines, several levels of conformance are available to address the diverse nature of digital content and the type of testing that is performed.

For an overview of WCAG 3 and links to WCAG technical and educational material, see WCAG 3 Introduction.

Guidelines

Summary

The following guidelines are being considered for WCAG 3. They are currently a list of topics which we expect to explore more thoroughly in future drafts. The list includes current WCAG 2 guidance and additional requirements. The list will change in future drafts.

Unless otherwise stated, requirements assume the content described is provided both visually and programmatically.

The individuals and organizations that use WCAG vary widely and include web designers and developers, policy makers, purchasing agents, teachers, and students. To meet the varying needs of this audience, several layers of guidance will be provided including guidelines written as outcome statements, requirements that can be tested, assertions, a rich collection of methods, resource links, and code samples.

The following list is an initial set of potential guidelines and requirements that the Working Group will be exploring. The goal is to guide the next phase of work. They should be considered drafts and should not be considered as final content of WCAG 3.0.

Ordinarily, exploratory content includes editor's notes listing concerns and questions for each item. Because this Guidelines section is very early in the process of working on WCAG 3, this editor's note covers most of the content in this section. Unless otherwise noted, all items in the list are exploratory at this point. It is a list of all possible topics for consideration. Not all items listed will be included in the final version of WCAG 3.0.

The guidelines and requirements listed below came from analysis of user needs that the Working Group has been studying, examining, and researching. They have not been refined and do not include essential exceptions or methods. Some requirements may be best addressed by authoring tools or at the platform level. Many requirements need additional work to better define the scope and to ensure they apply correctly to multiple languages, cultures, and writing systems. We will address these questions as we further explore each requirement.

Additional Research

One goal of publishing this list is to identify gaps in current research and request assistance filling those gaps.

Editor's notes indicate the requirements within this list where the Working Group has not found enough research to fully validate the guidance and create methods to support it or additional work is needed to evaluate existing research. If you know of existing research or if you are interested in conducting research in this area, please file a GitHub issue or send email to public-agwg-comments@w3.org (comment archive).

Images and media

Image alternatives

Users have equivalent alternatives for images.

Images detectable

Non-decorative images are detectable

Applies when

content includes non-decorative images.

Tests

This section is non-normative.

Procedure

For each non-decorative image:

Check the code to see if it has been marked up in a way that makes it detectable; or
For technologies where the code cannot be checked, use a screen reader to test that the image is detectable.

Expected results

#1 or #2 is true.

Decorative images hidden

Decorative images are programmatically hidden.

Tests

This section is non-normative.

(General) No accessible name

Procedure

Check for any images that add no information to the content.
Check that the image has no accessible name.

Expected results

#2 is true.

(HTML) Using an empty alt attribute for an image element

Procedure

For any image that adds no information to the content:

Check that title, aria-label, aria-labelledby etc. is either absent or empty.
Check that an alt attribute is present and empty.

Expected results

#1 is true.
#2 is true.

Image alternatives available

Equivalent text alternatives are available for images that convey content.

Tests

This section is non-normative.

Provide a text alternative for the image in a way that conveys the equivalent meaning or content that’s displayed visually.

(General) Equivalent text alternative

Procedure

For each non-decorative image:

Remove, hide, or mask the image.
Replace it with the text alternative.
Check that the meaningful content in the image is described by the text alternative.
If the image includes words that are important to understanding the content, check that those words are included in the text alternative.

Expected results

#3 is true.
#4 is also true, if the image includes words that are important to understanding the content.

Image types identified

The image types (photo, illustration, chart, etc.) are indicated.

Except when

An image is a link or a part of a link
An image is a button or a part of a button
An image is “purely” decorative (e.g. icon used alongside text, thumbnail image within a link)

Tests

This section is non-normative.

Procedure

For each image:

Check if the image is not a link, a button, any other interactive element nor purely decorative.
Check that the image type is described by the text alternative.

Expected results

#2 is true.

Alternative text editable

Needs additional research

Automatically generated text descriptions are editable by the content creator.

Tests

This section is non-normative.

Procedure

For each image that has automatically generated text descriptions, check that:

the image’s text description can be updated; and
the image can be marked as decorative.

Expected results

#1 is true, and
#2 is true,.

Image alternatives style guide

[Title, role, or organization] asserts that:

Our organization has a style guide that includes guidance on image text alternatives 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 assertion (if different from the date of the conformance claim).

Recommended internal documentation (Informative):

Section labels relevant to image alternatives, or
Copy or snapshot of the style guide

Media alternatives

Users have equivalent alternatives for audio and video content.

Transcripts available

Transcripts are available for all audio and video content.

Except when

The audio or video content is an alternative for text and clearly labelled as such.
It is a background video with no spoken content.

Tests

This section is non-normative.

(General) Transcript is available

Procedure

For each instance of audio or video:

Check that a transcript is available.

Expected results

#1 is true.

Media alternatives equivalent

Equivalent media alternatives are available for audio and video content.

Except when

It is a background video with no spoken content.

Tests

This section is non-normative.

Media alternative is equivalent

Procedure

For each instance of audio or video content:

Check that a media alternative is available for that content.
Check that the content of the media alternative is equivalent to the meaningful information in the media content.

Expected results

#1 and #2 are true.

Media alternatives findable

A mechanism is available within the page/view to access the media alternatives for audio and video.

Except when

It is a decorative audio or video.

Tests

This section is non-normative.

Link to text description of audio or video content

Procedure

For each instance of audio or video:

Check that a text description or link to a text description is provided for each audio or video.

Expected results

#1 is true.

Speakers identified

Speakers are identified understandably within all media alternatives.

Full name then use part of name
Hidden identity as part of narrative structure
Recognizable position within the context of use

Applies when

There are multiple speakers in the video.

Tests

This section is non-normative.

Consistent speaker name in transcript

Procedure

For each media alternative:

Check that each speaker in the audio or video is consistently identified.

Expected results

#1 is true.

Speaker language identified

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

Except when

Words are used incidentally.

Tests

This section is non-normative.

Language identified in transcripts

Procedure

For each transcript that includes multiple languages:

Check that part(s) using a language different from the original language is programmatically determined in the media alternatives.

Expected results

#2 is true.

Sounds identified

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

This includes sound effects and other non-spoken audio content.

Except when

it is a decorative video.

Applies when

there is sound.

Tests

This section is non-normative.

Meaningful sounds in captions

Procedure

For all audio content:

Identify meaningful non-verbal audio (sounds).
Check that captions include a description of the meaningful non-verbal audio.

Expected results

#2 is true.

Visual information identified

Visual information needed to understand the media is described in the transcript and audio description.

This includes actions, charts or informative visuals, scene changes, and on-screen text,

Tests

This section is non-normative.

Meaningful visual information in transcripts and audio descriptions

Procedure

For each transcript:

Check that the transcript includes a description of any visual information needed to understand the content of the audio or video.
Check that the audio description includes a description of any visual information needed to understand the content of the audio or video.

Expected results

#1 and #2 are true.

Non-verbal cues identified

Needs additional research

Nonverbal cues needed to understand the media are explained in media alternatives.

Tests

This section is non-normative.

Procedure

For each instance of audio content that includes nonverbal cues:

Check that the media alternatives explain audio nonverbal cues, such as tone of voice, facial expressions, body gestures, or music with emotional meaning.

Expected results

#1 is true.

Sign language available (prerecorded)

Sign language interpretation is provided for all prerecorded audio content in the primary sign language of the intended audience or region.

Except when

It is a decorative background sound.

Tests

This section is non-normative.

Sign language for audio only

Procedure

For each instance of prerecorded audio content:

Check that a sign language translation is available.
Check that the sign language translation conveys all the auditory information needed to understand the full context and meaning in the pre-recorded audio content.

Expected results

#1 and #2 are true.

Sign language available (live)

[Title, role, or organization] asserts that:

We provide Sign language interpretation for all live audio content in the primary sign language of the intended audience or region.

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).
Example recording of a signed live event.

Recommended internal documentation (Informative):

Procurement procedure for sign language interpreters.

Media alternatives style guide

[Title, role, or organization] asserts that:

Our organization has a style guide that includes guidance on media alternatives 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.
Section labels relevant to image alternatives, or
Copy or snapshot of the style guide

Accessible video player selected

[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; and
- 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.

Media alternatives usability testing

[Title, role, or organization] asserts that:

We have conducted usability testing with users who need media alternatives, 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.

Reviewed by content authors

[Title, role, or organization] asserts that:

We have reviewed the media alternatives.

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

Non-text alternatives

Users have alternatives available for non-text, non-image content that conveys context or meaning.

Non-text content not relied on

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

Tests

This section is non-normative.

HTML alternative text for images

Procedure

Examine the source code of the HTML document to identify all non-decorative img elements.
Each img element has an alt attribute.
The alt attribute provides a text alternative which conveys meaning or content that is displayed visually.
If the image includes words that are important to understanding the content, the words are included in the text alternative.

Expected results

#2, #3 and #4 are true

(Mobile) Videos include accessible name

Procedure

For each instance of non-text content:

Using native mobile screen reader to review all videos in the app.
When videos are navigated to an accessible name is read out.
The accessible name includes the title of the video.

Expected results

#2 and #3 are true

Captions

Users have captions for the audio content.

Captions adjustable

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.

Tests

This section is non-normative.

Procedure

For each caption:

Check that the appearance of captions and associated visual indicators is adaptable including font size, font weight, font style, font color, background color, background transparency, and placement

Expected results

#1 is true

Captions available (prerecorded)

Captions are available for all prerecorded audio content.

Except when

The audio content is an alternative for text and clearly labelled as such.

Tests

This section is non-normative.

Procedure

For each pre-recorded media asset:

If the captions format is closed captions:
- Turn on the closed caption feature of the media player
- View the synchronized media content
- Check that captions (of all dialogue and important sounds) are visible and in the human language of the video
If the captions format is open captions:
- Check that captions (of all dialogue and important sounds) are visible and in the human language of the video

Expected results

#1 or #2 is true.

Captions available (live)

Captions are available for all live audio content.

Tests

This section is non-normative.

Procedure

For all live audio content:

Check that captions are provided

Expected results

#1 is true

Captions unobstructed

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

Tests

This section is non-normative.

Procedure

For each caption:

Check if caption doesn’t hide visual information needed to understand the video content

Expected results

#1 is true

Captions synchronized

Captions are synchronized with the audio content of synchronized media.

Tests

This section is non-normative.

Procedure

For each caption:

Check if it is in sync with video content

Expected results

#1 is true

Caption features available

Needs additional research

Enhanced features that allow users to interact with captions are available.

Needs additional research.

Tests

This section is non-normative.

Procedure

For each media asset with audio content that provides enhanced features to allow users to interact with captions:

Play the media with captions on.
Check that a mechanism is available so that users can interact with the captions using all relative input methods.

Expected results

#2 is true

Captions consistent

Captions are presented consistently throughout the media, and across related productions, unless exceptions are essential. This includes consistent styling and placement of the captions text and consistent methods for identifying speakers, languages, and sounds.

Tests

This section is non-normative.

Procedure

For each media asset with audio content:

Play the media with captions on.
Check that the captions are presented consistently throughout the audio content.

Expected results

#2 is true.

Captions centered (immersive)

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.

Tests

This section is non-normative.

Procedure

For each caption in 360-degree environments:

Check that captions remain directly in front of the user.

Expected results

#1 is true.

Captions controllable

A mechanism is available to turn captions on and off.

Except when

Captions are hard coded into the video content.

Tests

This section is non-normative.

Procedure

For each caption:

Check that content with captions provides a mechanism to turn on and off the captions. Expected results

#1 is true

Direction indicated (immersive)

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

Tests

This section is non-normative.

Procedure

For each instance of audio that is heard from outside the current view in a 360-degree digital environment:

Check that the captions indicate the direction of a sound or speech.

Expected results

#1 is true

Audio descriptions

Users have audio descriptions for video content.

Audio descriptions available (prerecorded)

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

WCAG 3 needs to specify how to handle video content with audio that does not include gaps to insert audio descriptions. Two possible solutions are providing an exception that allows the content author(s) to use descriptive transcripts instead or requiring content authors to provide an extended audio description.

Except when

the video content is an alternative for text and clearly labelled as such.

Tests

This section is non-normative.

Procedure

For prerecorded video:

Check that audio description is available for visual content needed to understand the media

Expected results

#1 is true

Audio descriptions synchronized

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

Except when

There are no audio descriptions.

Tests

This section is non-normative.

Procedure

For synchronized media with audio description:

Check that audio description is in sync with video content in synchronized media.
Check that audio description doesn’t overlap with dialogue and meaningful audio content.

Expected results

#1 and #2 are true

Audio descriptions available (live)

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

Tests

This section is non-normative.

Procedure

For each live media broadcast

Check that a secondary audio option exists that provides live audio description of the broadcast.

Expected results

#1 is true.

Extended audio descriptions available

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.

Tests

This section is non-normative.

Procedure

For each media asset with visual content:

Play the media with the extended audio description on.
Check that the extended audio description provides all of the information that is important and cannot be understood from the main soundtrack alone.

Expected results

Extended audio description is equivalent and equal to the visual content in the media.

Audio description volume adjustable

A mechanism is available that allows users to control the audio description volume independently from the audio volume of the video.

Tests

This section is non-normative.

Procedure

For each media asset with visual content:

Play the media with audio description on.
Check that the media player provides users with control of the audio description volume separately from the main audio track.

Expected results

The volume of the audio description can be controlled separately from the main audio track of the media using all relevant inputs.

Audio description language adjustable

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

Tests

This section is non-normative.

Procedure

For each media asset with audio content:

Check that a version of the media has audio description available in alternative languages.
Alternatively, check that alternative versions of the media exist that have audio description available in alternative languages.

Expected results

Alternative language versions of the audio description are provided with the media and the language of audio description can be changed by the user using all relevant input methods.
Or alternative versions of the video are provided with the audio description in alternative languages and they are findable using all relevant input methods.

Figure captions

Users can view figure captions even if not focused at figure.

Persistent captions

Needs additional research

Figure captions persist or a mechanism is available to make figure captions persist, even if the focus moves away.

Single sense

Users have content that does not rely on a single sense or perception.

Hue not relied on

Information is not conveyed by hue alone.

Information conveyed includes presenting data or meaning, indicating an action, prompting a response, distinguishing between items, conveying boundaries, etc. Artistic expression is not part of information conveyed.

Except when

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

Tests

This section is non-normative.

Procedure

For each instance where information is conveyed by hue:

For each instance identified in #1, identify the instances where the hue conveys information.
For each instance identified in #2, confirm that at least one * additional visual indicator is present that conveys the same information.

Expected results

#2 is true

Graphical object contrast sufficient

Parts of graphical object 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.

Tests

This section is non-normative.

Procedure

For each graphical object: For each graphical object that conveys information:

Confirm that these parts meet the minimum contrast ratio with adjacent colors.

Expected results

#1 is true.

Visual depth not relied on

Information is not conveyed through visual depth perception alone.

Tests

This section is non-normative.

Procedure

For each instance where information is conveyed by visual depth:

For each instance identified in #1, identify the instances where the visual depth conveys information.
For each instance identified in #2, confirm that at least one additional visual indicator is present that conveys the same information.

Expected results

#2 is true.

Sound not relied on

Information is not conveyed by sound alone.

Except when

Content is audio-based media.

Tests

This section is non-normative.

Procedure

For each instance where information is conveyed by sound:

For each instance identified in #1, identify the instances where the sound conveys information.
For each instance identified in #2, confirm the information is conveyed in a way that does not use sound, for instance with a visual, text, or haptic indicator.

Expected results

#2 is true

Spatial audio not relied on

Information is not conveyed by spatial audio alone.

Tests

This section is non-normative.

Procedure

For each instance where information is conveyed by spatial audio:

For each instance identified in #1, identify the instances where the sound conveys information.
For each instance identified in #2, confirm the information is conveyed in a way that does not use sound, for instance with a visual text, or haptic indicator.

Expected results

#2 is true for all instances

Text and wording

Text appearance

Users can read visually rendered text.

Blocks of text readable (minimum)

Needs additional research

The default/authored presentation of blocks of text meets the corresponding values for the content’s language, or, if the language is not listed in the table, of the language listed with the most similar orthography.

Orthography refers to how a language is represented in text. This requirement establishes minimal readability criteria for an initial set of orthographies.

The metrics in the following table are still to be determined; the current content is an example.

Characteristic	Arabic	Chinese	English	Hindi	Russian
Inline margin
Block margin			≥0.5em around paragraphs
Line length			30-100 characters
Line height			1.0 - paragraph separation height

Blocks of text readable (minimum) and Text style readable (minimum) are based on common usage, and their adjustable and enhanced counterparts are based on readability research. We need more readability research in these languages.

Tests

This section is non-normative.

Procedure

For each block of text:

Check that the attributes of the block of text are within the attributes in the table for the closest language.

Expected results

#1 is true.

Text style readable (minimum)

Needs additional research

The default/authored presentation of text style property meets the corresponding values for the content’s language, or, if the language is not listed in the table, of the language listed with the most similar orthography.

The metrics in the following table are still to be determined; the current content is an example.

Characteristic	Arabic	Chinese	English	Hindi	Russian
Font face
Font size			Vertical viewing angle of ≥0.2° (~10pt at typical desktop viewing distances)
Font width
Text decoration			Most text is not bold, italicized, and/or underlined
Letter spacing
Capitalization
End-of-line hyphenation			Don't hard-code in the raw text.

Tests

This section is non-normative.

Procedure

For each block of text:

Check that the attributes of the block of text are within the attributes in the table for the closest language.

Expected results

#1 is true.

Text contrast sufficient (minimum)

Needs additional research

The default visual presentation of text meets @@[X 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.

Transparency can cause testing issues, but should be tested as the rendered color.

The contrast algorithm used in WCAG 3 is yet to be determined. For this draft, the requirement assumes the algorithm will include a size/weight factor. If the algorithm does not include size/weight, it will need to be added to this requirement text.

A separate requirement may be needed if red/green color vision deficiency (CVD) is not accounted for within the contrast algorithm.

Tests

This section is non-normative.

Procedure

For each foreground and background combination of text:

Identify the foreground color.
Identify the background color.
Check the contrast of text meets the [TBD algorithm].

Expected results

#3 is true

Blocks of text adjustable

Needs additional research

The presentation of blocks of text can be adjusted, without loss of content or functionality, to meet the corresponding values for the content’s language, or where that language is not listed in the table, for the language listed with the most similar orthography.

The requirement is that the text is manipulable and the style attributes can be overridden.

Except when

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

The metrics in the following table are still to be determined; the current content is an example.

Characteristic	Chinese	English
Inline margin
Block Margin
Line length
Line height
Justification	Not applicable	Default inline start to Left aligned

Tests

This section is non-normative.

Procedure

For each block of text:

Apply the highest level of change of each attribute from the table, for that language/script.
Check that the text is changed by the override.

Expected results

#2 is true.

Text style adjustable

Needs additional research

The presentation of each of the following text style properties can be adjusted, without loss of content or functionality, to meet the corresponding values for the content’s language, or, if the language is not listed in the table, of the language listed with the most similar orthography.

The requirement is that the text is manipulable and the style attributes can be overridden.

Except when

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

The metrics in the following table are still to be determined; the current content is an example.

Characteristic	Arabic	Chinese	English	Hindi	Russian
Font face
Font width
Text decoration			Most text is not bold, italicized, and/or underlined Text is not bold and italicized at the same time Underlines are only used for links
Letter spacing
Capitalization
Automatic end-of-line hyphenation			Disabled

Tests

This section is non-normative.

Procedure

For each block of text:

Apply the highest level of change of each attribute from the table, for the closest language.
Check that the text is changed by the override.

Expected results

#2 is true.

Text size adjustable

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.

Tests

This section is non-normative.

Procedure

For each block of text:

Use each platform mechanism for increasing text size.
Check that at least one mechanism can achieve a 200% text-size increase.

Expected results

#2 is true.

Text color adjustable

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

The requirement is that the text is manipulable and the colors can be overridden. That could be achieved by the user-agent (including operating system, browser, and assistive technology), or provided by the content author.

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.

Tests

This section is non-normative.

Procedure

For each block of text:

Adjust the foreground and background color to a high-contrast light-on-dark theme.
Check that content and functionality is not lost.
Adjust the foreground and background color to a high-contrast dark-on-light theme.
Check that content and functionality is not lost.

Expected results

#2 and #4 are true.

Blocks of text readable (enhanced)

Needs additional research

The metrics in the following table are still to be determined; the current content is an example.

Characteristic	Arabic	Chinese	English	Hindi	Russian
Inline margin
Block margin
Line length
Line height
Justification			Left aligned

Tests

This section is non-normative.

Procedure

For each block of text:

HTML: Check CSS to confirm that relevant style attributes (such as line height, letter spacing, word spacing, text align) are set within the designated values for the text’s language.
Non-web apps: Check GUI toolkit settings (or defaults) to confirm that they apply values within the designated range.

Expected results

#1 or #2 is true.

Text style readable (enhanced)

Needs additional research

The default/authored presentation of text style properties meets the corresponding values for the content’s language, or, if the language is not listed in the table, of the language listed with the most similar orthography.

The metrics in the following table are still to be determined; the current content is an example.

Characteristic	Arabic	Chinese	English	Hindi	Russian
Font face
Font size			Vertical viewing angle of ≥0.24° (~12pt at typical desktop viewing distances)
Font width
Text decoration			Most text is not bold, italicized, and/or underlined Text is not bold and italicized at the same time Underlines are only used for links
Letter spacing
Capitalization
Hyphenation

Tests

This section is non-normative.

Procedure

For each block of text:

HTML: Check CSS to confirm that relevant style attributes (such as font size and letter spacing) are set within the designated values for the text’s language.
Non-web apps: Check GUI toolkit settings (or defaults) to confirm that they apply values within the designated range.

Expected results

#1 or #2 is true.

Text contrast sufficient (enhanced)

Needs additional research

The default visual presentation of text meets @@[X contrast measure, 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.

Tests

This section is non-normative.

Procedure

For each foreground and background combination of text:

Identify the foreground color.
Identify the background color.
Check the contrast of text meets the [TBD algorithm].

Expected results

#3 is true.

Text customizations retained

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

Applies when

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

Tests

This section is non-normative.

Procedure

Customize a page/view by adjusting aspects of the text appearance, such as size, style, and color.
Export, save, and print the content.
Check that the customizations remain intact in the exported/saved/printed version. If there are multiple export options, check that at least one preserves the customizations.

Expected results

#3 is true.

Text-to-speech

Users can access text content and its meaning with text-to-speech tools.

Text detectable

All visible text has a programmatically determinable equivalent.

Except when

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

Tests

This section is non-normative.

Procedure

Identify all visible text.
For text that is embedded in an image, check if text has a text alternative or can be accurately read using the accessibility support set.
For text content, check that the text is not hidden using code such as the aria-hidden attribute.

Expected results

#2 is true.
#3 is true.

Human language detectable

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

Except when

a language tag is not available in ISO 639 language codes, or
the technology used to create the view does not support indicating languages.

Tests

This section is non-normative.

Procedure

Establish which languages are used in the view.
Check that the content’s language is identified in the HTML code with a lang attribute.

Expected results

#2 is true.

Text appearance not relied on

Meaning conveyed by text style properties is also programmatically determinable.

Applies when

the styling, weight, or other text characteristics convey meaning beyond what the text itself says.

Except when

emphasis is the only additional meaning conveyed.

Tests

This section is non-normative.

Procedure

Identify any instances of text styling, weight, size, or other text characteristics conveying meaning that is not just emphasis.
Check that an additional indicator of that meaning is available.

Expected results

#2 is true.

Numerical metadata available

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

Numerical metadata is information that provides context about the numbers presented. This context helps users understand what the numbers represent and how they should be read. Without these cues, numbers can be ambiguous or misleading, making it harder for users to understand the intended meaning—especially across different regions, disciplines, or assistive technologies.

Tests

This section is non-normative.

Procedure

Identify any dates, temperatures, times, and Roman numerals that are presented visually.
Check that it uses an unambiguous format.
Check that it provides an alternative in an unambiguous format within the same page/view.

Expected results

#2 is true, or
#3 is true.

Clear language

Users can understand the content without having to process complex or unclear language.

This guideline will include exceptions for poetic, scriptural, artistic, and other content whose main goal is expressive rather than informative.

See also: Structure as these guidelines are closely related.

To ensure this guideline works well across different languages, members of AGWG, Cognitive and Learning Disabilities Accessibility Task Force (COGA), and internationalization (i18n) agreed on an initial set of languages to pressure-test the guidance.

The five “guardrail” languages are:

Arabic
English
Hindi
Mandarin
Russian

We started with the six official languages of the United Nations (UN). Then we removed French and Spanish because they are similar to English. We added Hindi because it is the most commonly spoken language that is not on the UN list.

The group of five languages includes a wide variety of language features, such as:

Right-to-left text layout
Vertical text layout
Tonal sounds that affect meaning

This list doesn’t include every language, but it helps keep the work manageable while making the guidance more useful for a wide audience.

We will work with W3C’s Global Inclusion community group, the Internationalization (i18n) task force, and others to review and refine the testing and techniques for these requirements. We also plan to create guidance for translating the guidelines into more languages in the future.

Abbreviations explained

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
- included in a longer phrase, such as “brand DNA,” whose meaning needs to be defined to meet the non-literal language requirement.

Tests

This section is non-normative.

Procedure

Check for any abbreviations in the content.
Check that an explanation is available for the first use of the abbreviation.
For an abbreviation that has no explanation available, check that it is included in a dictionary intended for the general public.

Expected result

#2 or #3 is true.

Non-literal language explained

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.

Translation software and other tools can aid content authors in identifying non-literal language.

Tests

This section is non-normative.

Procedure

For each phrase of non-literal language in text content:

Check that access is provided to an unambiguous alternative or to an explanation of the non-literal text.
Check that the non-literal text is presented in a way that is available to user agents, including assistive technologies (AT).
Check that the accessibility support set meets ‘Non-literal language explained’.

Expected results

#1 and #2 are true, or
#3 is true.

Summaries available

Needs additional research

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.

Research is needed to determine the number of words that trigger the summary requirement and whether this threshold varies for different languages.

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.

Tests

This section is non-normative.

Procedure

For long-form text content that has 300 or more words:

Check that a summary is present.
Check that the summary can be identified visually and programmatically.
Check that the summary explains uncommon words and uses concise sentences.

Expected results

#1 is true.
#2 is true.
#3 is true.

Common words used

Needs additional research

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.

This is not a core requirement because a list of common words would not cover terms that are known by specific audiences, such as accounting terms on an accounting site. However, in future guidance for policy makers, it is an example of a supplemental requirement that could be made mandatory for public service and education providers.

Lists of common words are called high-frequency corpora. They exist for many languages including Arabic, Hindi, Mandarin, and Russian as well as American English, British English, and Canadian English.

Research shows that using common words and defining uncommon words improves understanding. Making Content Usable for People with Cognitive and Learning Disabilities recommends using the 1,500 highest-frequency words or phrases because people with severe language impairments are most likely to know these terms. However, more research is needed to confirm if the same threshold applies to many languages for distinguishing common from uncommon words.

Tests

This section is non-normative.

Procedure

For each word:

Check that the word appears in the 1,500 most common words in a high-frequency corpus for the language used.
If the word is not in the list of the 1,500 most common words, check that it has a definition available within the page/view.
Check that a technology in the accessibility support set meets ‘Common words used.’

Expected results

#1, #2, or #3 is true.

Diacritics available

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.

A diacritic is a small mark that is added to a letter or character that changes how it is pronounced or what it means. Diacritics may appear above, below, within, or between letters or characters.

Hebrew and Arabic are examples of human languages that omit diacritics for proficient readers.

Tests

This section is non-normative.

Procedure

Check for content that has missing diacritics.
Check that an alternative version is provided that includes diacritics needed to identify the correct meaning of each word.
Check that the accessibility support set meets ‘Diacritics available’.

Expected results

#2 is true, or
#3 is true.

No nested clauses

Sentences do not include nested clauses.

Except when

text content:
- is poetic, scriptural, artistic, or expressive rather than informational, or
- provides legal information.

Tests

This section is non-normative.

Procedure

For each sentence:

Identify all nested clauses in the sentence (introduced by nesting conjunctions such as ‘because’, ‘although’, ‘if’, ‘that’, ‘which’, ‘who’, ‘when’, and ‘where’).
Check that each initial nested clause does not contain other nested clauses within it.
Check that a technology in the accessibility support set meets ‘No nested clauses’.

Expected results

#2 is true, or
#3 is true.

No unnecessary words

Sentences do not include unnecessary words.

Except when

text content is:
- poetic,
- scriptural,
- artistic, or
- expressive rather than informational.

Automated tools can help content authors identify unnecessary words in many languages, including Arabic, English, Hindi, Mandarin, and Russian.

Tests

This section is non-normative.

Procedure

For each sentence:

Identify any words that may be unnecessary.
Remove or replace the phrase with a simpler alternative.
Check that no meaning is lost.
Check that a technology in the accessibility support set meets ‘No unnecessary words.’

Expected results

#3 or #4 is true.

Numerical alternatives available

Explanations or alternatives are provided for complex numerical information such as statistics.

Complex numerical information can increase cognitive load, especially for users with a limited ability to understand and work with numbers. Providing written explanations or visualizations can aid understanding.

Tests

This section is non-normative.

Procedure

Check for any complex numerical information in the content.
Check that an alternative is available that is not presented as complex numerical information.

Expected results

#2 is true.

Clear language review

[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.

Visual aids review

[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

Interactive components

Keyboard focus appearance

Users can see which element has keyboard focus.

Default focus indicator used

The focusable item uses the user agent default focus indicator.

Tests

This section is non-normative.

Procedure

For user agents that allow the customization of focus indicators:

Use the keyboard to move focus onto the item.
Check that the focus indicator is the user agent’s default indicator.
For platform display changes, check that the focus indicator’s color is correct for the type of element.

Expected results

#2 and #3 are true.

Focus indicator contrast sufficient

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.

Tests

This section is non-normative.

Procedure

For each element able to attain focus:

Using a keyboard, tab to the component.
Check that the focus indicator contrast meets the minimum contrast ratio test.

Expected results

#2 is true

Focus indicator size sufficient

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.

Tests

This section is non-normative.

Procedure

For each custom focus indicator:

Check that the focus indicator is at least as large as the area of a 2 CSS pixel thick perimeter of the unfocused component or sub-component, and
Check that the focus indicator has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states.

Except when

the focus indicator is determined by the user agent and cannot be adjusted by the author, or the focus indicator and the indicator’s background color are not modified by the author.

Expected results

#1 and #2 are true.

Focus indicator style guide

[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.
A copy of the design style guide (if any) where focus style has been defined.

Pointer focus appearance

Users can see the location of the pointer focus.

Pointer activation indicated (minimum)

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.

This is primarily aimed at touch-interfaces and VR where you don’t have a pointer indicator, but do need to know when something has been selected.

Tests

This section is non-normative.

Procedure

Where the platform does not use a visible pointer indicator:

For each interactive element, check that there is an indicator of activation.

Expected results

#1 is true

Pointer activation indicated (enhanced)

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

Applies when

The platform does not use a visible pointer indicator.

This is primarily aimed at eye-tracking and touch-screens, where it is useful for the user to be able to have a visible indicator, but it wouldn’t be universal (i.e., it might get in the way for some users).

Tests

This section is non-normative.

Procedure

Check the settings of the OS or product for the ability to have an always-visible pointer indicator.

Expected results

#1 is true

Pointer contrast sufficient

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

There can be multiple types of pointer indicator (e.g. arrow, hand, caret). The size requirement applies to whichever type of indicator would be the default for that scenario.

Applies when

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

Tests

This section is non-normative.

Procedure

For each custom pointer:

Identify which visual information defines the boundaries of the interactive area.
Check if the visual information meets the minimum contrast ratio test.
For each possible state, repeat step 1 and 2.

Expected results

#3 is true for each state.

Default pointer used

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.

Methods & best practices:

No scripting or styling overrides the pointer indicator appearance.
A setting is provided so that the pointer indicator appearance is not overridden.

Tests

This section is non-normative.

Procedure

Check that the pointer uses the standard platform indicator.
If it does not, check for a setting that the user can enable to use the standard platform indicator.

Expected results

#1 or #2 is true

Pointer focus indicated

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.

Examples of pointers which do not always show the pointer indicator:

A touch-screen interface does not need to have an indicator as the pointer is not on an element before activating it.
An eye-tracking interface highlights the element under the gaze of the user, but otherwise does not have a pointer indicator.
A game where you use the pointer to move the entire view around a virtual environment.

Methods & best practices:

Method: Interactive elements are highlighted when the pointer is on the element. For example, a set of image-links are shown, and the one under the pointer is highlighted with an outline or size-change.

Tests

This section is non-normative.

Procedure

With appropriate user-settings enabled:

Move the pointer (mouse, eye tracker, hand gesture in VR space, …) and verify if there is some form of indication of where the user is pointing to.

Expected results

#1 is true

Pointer visible

The pointer indicator is always visible.

Except when

The pointer is on a video, it can be hidden if it is not moving.
The pointer controls the direction of view in a virtual or real world environment.

Methods & best practices

Method: No styling or scripting hides the pointer indicator.

Tests

This section is non-normative.

Procedure

If the pointer is ever not visible:

Check whether it meets one of the exceptions.

Expected results

#1 is is true

Enhanced pointer available

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.

Methods & best practices:

Provide a setting to adjust the pointer indicator.

Tests

This section is non-normative.

Procedure

Check for a setting that increases the visibility.
Check that it works in the conformance scope of web pages/views.

Expected results

#1 and #2 are true

Navigating content

Users can determine where they are and move through content (including interactive elements) in a systematic and meaningful way regardless of input or movement method.

Focus relevant

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

Tests

This section is non-normative.

Procedure

Identify components that receive focus.
For groups of repeated interactive elements (for example, a site-wide navigation bar on a website), check that a method of skipping them is available.
Check that hidden interactive elements do not receive focus
Check that static elements do not receive focus.

Expected results

#2, #3, and #4 are true.

Focus retained

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.

Tests

This section is non-normative.

Procedure

For each situation where the keyboard focus is removed:

verify that the keyboard focus moves to its previous location, or, if that no longer exists, to another meaningful location.

Expected results

#1 is true.

Focus order meaningful

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

The Common Keyboard Navigation Techniques are considered logical by default
Having the navigation follow a consistent pattern on the page would be an indication of logic (if it is not consistently random).
A strictly start-to-end order is not required.
Linear means in a single direction (forward/backward) - and is not required as long the non-linear (x-y) technique is in the Common Keyboard Navigation Techniques or is described on the page or where the user will encounter it prior.

Tests

This section is non-normative.

Procedure

Determine the logical order of the interactive elements.
Starting with the first focusable element in the page/view, tab through the interactive elements in the content.
Check that the focus order of the interactive elements in the content is the same as the logical order in #1.

Expected results

#3 is true

Expected behavior

Users can interact with interactive elements that behave as expected.

Consistent interactions

[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.

Consistent control location

Needs additional research

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 (such as e-commerce checkout).

Methods & best practices

Method: Establish a design system with documented rules for consistent placement of common interactive components (for example, navigation menus, search bars, and action buttons).
Method: Reuse the same components across pages/views instead of recreating them.
Best practice: If a visual position must change, document why and consider providing cues (for example, animations and labels) to reduce confusion.

Tests

This section is non-normative.

Procedure

For each interactive component in a set of pages/views:

Method: Components appear in the same relative visual position across pages/views, except when exceptions apply.
Best practice: Verify that any change in component position is intentional and documented.

Expected results

#1 is true.

Conventional pattern used

[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.

A component library specifies a set of standardized components used in a product or products. It can include code to use, but at a minimum would define how the component is used and define pointer, keyboard, and assistive technology interactions.

Using a component library can help larger teams and organizations provide a consistent experience.

Examples of component libraries include GDS, Carbon Design System, and Lion.

Examples of platform patterns are ARIA Platform Authoring Guide (web), Apple human interface guidelines, and Android Material Design.

Control information

Users have information about interactive elements that is identifiable and usable visually and using assistive technology.

Interactive element contrast sufficient

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

Except when

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

Tests

This section is non-normative.

Procedure

For each interactive element:

Identify which visual information defines the boundaries of the interactive area.
Check if the visual information meets the minimum contrast ratio test.
For each possible state, repeat step 1 and 2.

Expected results

#2 and #3 are true.

Interactive element importance indicated

Needs additional research

The importance of interactive components is indicated.

Interactive element names available

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

Visible labels can be text or non-text, for instance icons.

Methods & best practices

Method: Provide unique, descriptive text or image (icon) for each interactive element.
Best Practice: Ensure clarity by pairing an icon with a persistent visible text label or only use a persistent visible text label.
Best Practice: When an icon is the only visual label, provide a tooltip (hover label) with the text description.

Tests

This section is non-normative.

Procedure

For each interactive element:

Confirm it has a visual label that describes the element.
Confirm the visual label persists during use.

Expected results

#1 and #2 are true.

Changes to elements notified

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

Methods & best practices:

Method: Add code that clearly defines the name, role, value and state.
Method: visually indicate the names, roles and values of the interactive element.
Method: HTML - html tags or aria

Tests

This section is non-normative.

Procedure

For each interactive element:

Confirm that the role, value, and state (when applicable) are visually indicated in all states.
Inspect the code and accessibility tree (when available) to confirm that the name, role, value and state (when applicable) are indicated.

Expected results

#1 and #2 are true.

Interactive elements distinguishable

Interactive elements are visually distinguishable without interaction from static content and include visual cues on how to use them.

Methods & best practices

Method: Add visual indicators such as shading, border, drop down arrow, placement, etc. to interactive elements.
Best Practice: Document interactive indicators and designs in style guide

Input constraints used

Field constraints and conditions (required line length, date format, password format, etc.) are available.

Methods & best practices

Method (HTML): to programmatically indicate, use the pattern attribute or write the information in a label; to visually indicate, add the requirements to the page near the input.

Best practice: the constraints remain persistent

Tests

This section is non-normative.

Procedure

For each input:

Confirm it has a visual information that describes the constraint.
Inspect the code and accessibility tree (when applicable) and confirm that the constraint is programmatically listed in the code and associated with the input.

Expected results

#1 and #2 are true.

Label included in programmatic name

The programmatic name includes the visual label.

Methods & best practices

Method: Code the same name as you display.
Best Practice: Use unique names and keep the programmatic and visual names the same.

Tests

This section is non-normative.

Procedure

For each interactive element:

Identify the interactive elements’ programmatic name.
Identify the interactive element’s visual name.
Verify that #1 includes all of #2.

Expected results

#3 is true

Roles, values, states, properties available

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

Methods & best practices

Method (HTML): use HTML elements according to specification.
Method (ARIA): add roles, values, states, and properties according to specification.

Tests

This section is non-normative.

Procedure

For each interactive element:

Inspect the code and accessibility tree (when available) to confirm that the role, value, state, and properties (when applicable) are indicated.

Expected results

#1 is true.

Input / operation

Keyboard interface input

Users can navigate and operate content using only the keyboard.

Keyboard operable

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.

Tests

This section is non-normative.

Procedure

For each interactive element:

Check that it is an be operated using only the keyboard and keyboard actions in the Standard Keyboard Navigation & Operation Keys and Techniques or described on the page where it is required or on a page earlier in the process where it is required.

Expected results

#1 is true

Keyboard accessible

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

All content includes content made available via hovers, right clicks, etc.

Other input modalities include pointing devices, voice and speech recognition, gesture, camera, and any other means of input or control.

The “Keyboard operable” requirement allows you to navigate to all actionable elements, but if the next element is 5 screens down, you also need to be able to access all the content. Also, if the content is in expanding sections, you need to not only open them but also access all of the content, not just its actionable elements.

Tests

This section is non-normative.

Procedure

Using only the keyboard and keyboard actions in the Standard Keyboard Navigation & Operation Keys and Techniques or described on the page where it is required or on a page earlier in the process where it is required, try to view all content on the page/view

Expected results

#1 is true

Bidirectional navigation

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

Although keyboard navigation is required to be bidirectional, it is not required that it be symmetrical, even though this is usually best practice.

Methods & best practices:

Method: Use standard HTML to create interactive elements.
Avoid modifying the tab order to be in only one direction.

Tests

This section is non-normative.

Procedure For each interactive element:

Check that when tabbing forwards, you can navigate to the interactive element and then to the next interactive element.
Check that when tabbing backwards, you can navigate to the interactive element and then to the previous interactive element.

Expected results

#1 and #2 are true

Custom keys documented

Non-standard keyboard commands provided by content authors are documented and that documentation is programmatically and visually available from any page/view to which they apply.

Tests

This section is non-normative.

Procedure

For each non-standard (custom) keyboard command that works on a page/view:

Verify that documentation of keyboard commands exists.
Verify that the documentation is available from the page/view.

Expected results

#1 and #2 are true.

No keyboard conflicts

Keyboard commands provided by content authors do not conflict with standard platform keyboard commands or they can be remapped.

Tests

This section is non-normative.

Procedure

For each author generated keyboard command:

Check that it does not conflict against the standard platform keyboard commands.
Check that it can be remapped.

Expected results

#1 or #2 is true

Keyboard navigable if responsive

If the page/view uses responsive design, the page / view remains fully keyboard navigable.

Tests

This section is non-normative.

Procedure

For each breakpoint defined by the author and at minimum width:

Check that all keyboard input tests work.

Expected results

#1 is true

Focus placed

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.

Method: When removing interactive elements such as filters, dialogs, or popups that currently contain focus, actively place the focus back on the element that led to that element, the previous element within the focus order, or another meaningful location.

Best Practice: Conduct usability testing with screen reader users to evaluate the focus movement.

Tests

This section is non-normative.

Procedure

For each situation where elements that have or contain keyboard focus are removed:

Check that the keyboard focus moves to its previous location, or, if that no longer exists, to another meaningful location.

Expected results

#1 is true for each situation

No keyboard traps

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 on the page/view or earlier in the process.

Tests

This section is non-normative.

Procedure

For each interface element:

Check that you can exit from it in a forward or backward direction.

Expected results

#1 is true

Focus user-controlled

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.

Tests

This section is non-normative.

Procedure

For each time the keyboard focus changes:

Check that one of the following is true”
- The focus was moved under direct user control
- A new page / view such as a dialog is introduced and the focus is moved to it
- The user is informed of the potential move and given the chance to avoid the move
- The keyboard focus moves to the next item in keyboard navigation order

Expected results

#1 is true

Focus movement relevant

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.

Accordions, dropdown menus, and ARIA tab panels are examples of expandable content. According to this requirement, these would not expand simply because they include an element in the tab-order contained in them. They would either not expand or would not have any tab-order elements in them.

Tests

This section is non-normative.

Procedure

For any interactive element:

Check that keyboard focus does not disappear into content that is not visible.
Check that hidden element does not automatically expand (become visible) when the keyboard focus is on it (unless it is a visually hidden element specifically added to aid keyboard navigation) (e.g. skip to main content).

Expected results

#1 and #2 are true.

Physical or cognitive effort when using keyboard

Users can use keyboard without unnecessary physical or cognitive effort.

Navigation keys described

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.

Any platform-related functions are not the responsibility of the author as long as they are not overridden by the content. Examples:

Tab and Shift + Tab to move through elements
Sticky Keys functionality that allows single key activation of multi-key commands

Tests

This section is non-normative.

Procedure

For each keyboard command needed to operate functionality:

Check that it is in the list of common keyboard navigation technique.
Check that it is described on the page / view where it is required or on a page / view earlier in the process where it is used.

Expected results

#1 or #2 are true

No repetitive links

Repetitive adjacent links that have the same destination are avoided.

Supplemental if applicable to all content, else best practice.

A common pattern is having a component that includes a linked image and some linked text, where both links go to the same content. Someone using screen reading software can be disoriented from the unnecessary chatter, and a keyboard user has to navigate through more tab stops than should be necessary. Combining adjacent links that go to the same content improves the user experience.

Methods & best practices

Method: When repetitive links are used, remove them from the focus and reading order.
Method: Use a single link instead of multiple links to the same destination.
Best practice: Combine repetitive links into a single interactive element.

Tests

This section is non-normative.

Procedure

For adjacent links that go to the same destination: 2. Check that only one of the links is in the focus or reading order.

Expected Results

#1 is true.

Keyboard effort comparable

[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.

Other input modalities include pointing devices, voice and speech recognition, gesture, camera, and any other means of input or control.

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.
A copy of the user interface design principles document.

Pointer input

Pointer input is consistent and all functionality can be done with simple pointer input in a time and pressure insensitive way.

Pointer controllable

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 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.

Tests

This section is non-normative.

Procedure

For each element that can be activated with a simple pointer:

Check that the down-event of the pointer is not used to execute any part of the function.
Check that completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion.
Check that the up-event reverses any outcome of the preceding down-event.
Check that completing the function on the down-event is essential.

Expected results

#1, #2, #3, or #4 is true

Simple pointer input available

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.

Complex pointer inputs are not banned, but they cannot be the only way to accomplish an action.

Simple pointer input is different than single pointer input and is more restrictive than simply using a single pointer.

Tests

This section is non-normative.

Procedure

For each functionality that uses pointer input other than simple pointer input:

Check that it can also be operated by a simple pointer input or a sequence of simple pointer inputs that do not require timing.

Expected results

#1 is true

Consistent pointer cancellation

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.

Where it is essential to be different, it can be helpful to alert the user.

Tests

This section is non-normative.

Procedure

For each type of pointer interaction: #1. Check that it can be cancelled with a consistent interaction.

Expected results

#1 is true.

Pointer pressure not relied on

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

Except when

Specific pressure is essential to the functionality.

Methods & best practices:

Method: When building in functionality that relies on pointer pressure, add a slider or other control that can complete the same functionality.

Tests

This section is non-normative.

Procedure

For each instance of interactive content:

Check that pointer pressure is not the only way to achieve any functionality.

Expected results

#1 is true

Pointer speed not relied on

Functionality does not rely solely on specific pointer speed.

Except when

Specific pointer speed is essential to the functionality.

Tests

This section is non-normative.

Procedure

For each instance of functionality that uses a pointer:

Check that pointer speed is not the only way to achieve any functionality.

Expected results

#1 is true

Speech and voice input

Provide alternatives to speech input and facilitate speech control.

Speech not relied on

Content or functionality does not rely on speech alone.

Except when

Speech input is essential to the functionality.

Methods & best practices

Method: When speech input is supported, an additional way of providing input is also supported.

Tests

This section is non-normative.

Procedure

For each functionality or content that is accessed using speech input:

Check that there is another way to complete the functionality.

Expected results

#1 is true.

Real-time text available

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

Methods & best practices

Method: Provide a chat option for any voice communication

Tests

This section is non-normative.

Procedure

For each places where speech is used for communication (with human or AI):

Check that there is an alternative way to achieve the same function using real-time text.

Expected results

#1 is true

Generated speech testing

[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.

Input operation

Users have the option to use different input techniques and combinations and switch between them.

Hover or focus content dismissible

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.

This applies to content that appears in addition to the triggering of the interactive element itself. Since hidden interactive elements that are made visible on keyboard focus (such as links used to skip to another part of a page/view) do not present additional content, they are not covered by this requirement.

Tests

This section is non-normative.

Procedure

For additional content that appears on hover:

Check that the content can be closed without moving the pointer way from the trigger. Either by pressing Esc, by pressing another documented keyboard shortcut, or by activating the trigger.

For additional content that appears on focus:

Check that the content can be closed without moving the focus way from the trigger. Either by pressing Esc, by pressing another other documented keyboard shortcut, or by activating the trigger.

Expected results

For additional content that appears on hover: #1 is true.
For additional content that appears on focus: #1 is true.

Hover content persistent

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.

Tests

This section is non-normative.

Procedure

For additional content that appears on hover:

Check that he pointer can be moved over the additional content without the additional content disappearing.

Expected results

#1 is true.

Hover or focus content persistent

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.

Tests

This section is non-normative.

Procedure

For additional content or focus that appears on hover:

Check that the additional content stays visible and does not automatically close after a time.

Expected results

#1 is true.

Path-based gesture not relied on

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

Except when

A path-based gesture is essential to the functionality.

Tests

This section is non-normative.

Procedure

For each path-based gesture:

Check that the functionality is available without a path-based gesture.

Expected results

#1 is true

Input method flexible

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

This does not mean that all input technologies (pointer, keyboard, voice, gesture) need to be supported, but if an input modality is supported, it is supported everywhere in the content except where a particular input method is essential to the functionality.

Tests

This section is non-normative.

Procedure

For each input:

Set up multiple input types (pointer, keyboard, voice, gesture, etc)
Check that you can switch between inputs and complete functionality

Expected results

#2 is true

Body movements not relied on

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

Except where

Full or gross body movement is essential to the functionality.

This includes both detection of body movement and actions to the device, such as shaking, that require body movement.

Tests

This section is non-normative.

Procedure

For each instance of functionality that uses body movement:

Check that the body movement is not the only way to achieve any functionality.

Expected results

#1 is true

Eye tracking not relied on

Content and functionality does not rely solely on eye tracking.

Except when

Eye tracking is essential.

This is primarily aimed at ensuring there is an alternative for people who cannot use eye-tracking (but do have sight) due to eye conditions.

Some platforms may only allow eye tracking. Ideally the platforms allow additional mechanisms for control.

Tests

This section is non-normative.

Procedure

For platforms that use eye-tracking for pointer use:

Check that alternative, such as using a switch control, is available.

Expected results

#1 is true

Pointer accessible

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.

Tests

This section is non-normative.

Procedure

For every interactive element that allows pointer selection (including click events on non-interactive elements):

Check that the keyboard focus moves when the pointer selects the element.

Expected results

#1 is true

Authentication

Users have alternative authentication methods available to them.

Biometrics not relied on

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

Biometrics includes facial recognition software, fingerprinting, vocal patterns and other voice characteristics.

Methods & best practices

Method: When requiring biometric information for authentication, provide an additional way to authenticate that is not biometric. For example, if a finger print is required for authentication, then a password must also be supported.

Tests

This section is non-normative.

Procedure

For each method of user authentication:

Verify that there is at least one other method of non-biometric authentication.

Expected results

#1 is true.

Multiple biometrics available

Authentication does not rely solely on a single type of biometric information.

Methods & best practices

Method: When requiring biometric information for authentication, provide an additional way to authenticate (this may include using a different type of biometrics — for example, if a finger print is required for authentication, then voice authentication or a password must also be supported).

Tests

This section is non-normative.

Procedure For each method of user authentication:

Verify that there is at least one other method of authentication (biometric or non-biometric).

Expected results

#1 is true

Voice identification not relied on

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

Tests

This section is non-normative.

Procedure

Locate any places where voice is used for identification.
Check that there is an alternative way to achieve authentication.

Expected results

#2 is true

Error handling

Correct errors

Users know about and can correct errors.

Error notifications available

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

Tests

This section is non-normative.

Procedure

For each page/view:

Trigger errors.
For each error, verify that the nature of the problem is identified and described.

Expected results

#2 is true for each error.

Error suggestions provided

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.

Tests

This section is non-normative.

Procedure

For each error message:

Verify it is an error that needs correction by the user.
Verify that the error message includes suggestions for how to fix the error.

Expected results

#1 and #2 are true

Errors indicated in multiple ways

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

A symbol that is consistent throughout the product.
Color that differentiates the error message from surrounding content.
Text that clearly indicates the error.

Tests

This section is non-normative.

Procedure

For each validation error:

Verify that it meets at least two of the listed indicators (symbol, color or text).

Expected results

#1 is true

Error messages persistent

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

Methods & best practices

Method: Keep track of the state of the error and make visibility of the error message depending on this state.
Method: In a form, revalidate all fields when the form is submitted and remove all error messages that are no longer relevant.
Method: Add a “Dismiss” button to the error that makes the error message disappear.
Best Practice: [1-2 sentence description or a link to an example]

Tests

This section is non-normative.

Procedure

For each error messages:

Verify that the error message persists until the user fixes the error or dismisses the message.

Expected results

#1 is true

Errors associated

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

Tests

This section is non-normative.

Procedure

For each validation error:

Verify that validation error is indicated visually.
Verify that validation error is indicated programmatically.

Expected results

#2 and #3 are true.

Error messages collocated

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.

Tests

This section is non-normative.

Procedure

For each page/view:

Zoom in 400%
Trigger errors
Make sure the error is visible next to the trigger or that the focus moves to the error.

Expected results

#3 is true

Prevent errors

Users can review, confirm and fix information they submit in order to prevent errors.

Errors preventable

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

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

Except when

entered data is auto-saved and/or reversible.

Editors are looking at removing the grey area that may exist in this requirement due to interpretations of the word “submission“ (pressing “Submit” in the UI or receiving information server-side).

Tests

This section is non-normative.

Procedure

Identify all data entry points.
Verify that users can return at any point in the process to correct data they entered.
If it’s not possible to go back and correct the data during the process, verify that the information being submitted can be reviewed and corrected before submission, or that it’s validated and can be fixed before submission.

Expected results

#2 is true, or
#3 is true

Submission status notified

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

Applies when

data submission has succeeded or failed.

Tests

This section is non-normative.

Procedure

Submit data.
Verify that the user is notified about the submission immediately afterwards.

Expected results

#2 is true.

Data entry validated

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

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

Tests

This section is non-normative.

Procedure

Verify that no validation has not occurred before data entry.
Enter data.
Verify that validation is provided immediately after data entry or occurs before submission.

Expected results

#1 is true.
#2 is true.

Error prevention review

[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, and
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

Animation and movement

Avoid physical harm

Users do not experience physical harm from content.

No flashing

Content does not include flashing.

Except when

The flashing is essential.

Method(s)

Consider if flashing is essential and, if it is not, refrain from including it.

Tests

This section is non-normative.

Procedure

For each page/view:

Identify if content includes flashing.
For each instance of flashing, identify if the flashing is essential.

Expected results

#1 is false, or
#2 is true

No flashing (no exceptions)

Content does not include flashing.

Method(s)

Design content without using flashing.

Tests

This section is non-normative.

Procedure

For each page/view:

Identify if content includes flashing.

Expected results

#1 is false

No visual motion

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

Except when

The motion or pseudo-motion is essential.

Method(s)

Consider if motion or pseudo-motion is essential, and if it is not, refrain from including it.

Tests

This section is non-normative.

Procedure

For each page/view:

Identify if content includes visual motion or pseudo-motion.
For each instance, identify if the visual motion or pseudo-motion is essential.

Expected results

#1 is false, or
#2 is true

No visual motion (no exceptions)

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

Method(s)

Design content without using visual motion or pseudo-motion.

Tests

This section is non-normative.

Procedure

For each page/view:

Identify if content includes visual motion or pseudo-motion.

Expected results

#1 is false

Trigger warning available

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

Note: Triggers are flashing, motion lasting more than 5 seconds, and pseudo-motion.

Method(s)

Provide a warning for triggers and provide an option without the triggers.

Tests

This section is non-normative.

Procedure

For each trigger:

Check if a warning is provided before the user encounters the trigger.
Check that the same information is available without triggers.

Expected results

#1 and #2 are true

Haptic stimulation adjustable

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.

Method(s)

Add a setting to reduce haptic feedback or turn it off.

Tests

This section is non-normative.

Procedure

For haptic feedback caused by the digital content (vs. the operating system or user agent).

Identify if there is a setting that allows for reducing or turning off the haptic feedback.

Expected results

#1 is true

Audio shifting adjustable

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.

Method(s)

Add a setting to pause audio-shifting or turn it off.

Tests

This section is non-normative.

Procedure

For audio shifting caused by the digital content (vs. the operating system or user agent):

Check that there is a setting to pause or turn off the audio shifting.

Expected results

#1 is true

Visual stimulation

Needs additional research

Visual stimulation from combinations of density, color, movement, etc. can be reduced or turned off.

Safe content review

[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).

Troubling content will vary based on culture or individual situations, and reviews should take target audiences into consideration.

Layout

Recognizable layouts

Users have consistent and recognizable layouts available.

Conventional layout review

[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-convention layout is used, usability testing results that demonstrate the utility of the approach taken.

User orientation

Users can determine their location in content both visually and using assistive technologies.

Page/view title available

Pages/views have a title that describes the name, topic or purpose.

Except when

The presented content has no way to include a title.

Tests

This section is non-normative.

Procedure

Examine the source code of the HTML document and check that the first title element is not-empty.
Check that the title element describes the document.

Expected results

#1 and #2 are true.

Location within product review

[Title, role, or organization] asserts that:

We have reviewed conventions for presenting current location within a product or process.
The presentation of current location within a product or process uses appropriate visually and programmatically patterns.

It is often helpful for users to understand where within a product they are. There are many ways to achieve this, for example, a breadcrumb. Ideally this is consistently presented throughout the product but for some pages/views it may make less sense to include. For example, including a breadcrumb trail on the homepage or on pages that sit outside the hierarchy, for example a shopping cart.

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 product.
If a non-convention design pattern is used, usability testing results that demonstrate the utility of the design approach taken.

All steps listed

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.

Tests

This section is non-normative.

Visual multi-step listing

Procedure

Review the content within each stage of a multi-step process.
A list of steps in the process is included on each stage.

Expected results

#2 is true

HTML multi-step listing

Procedure

Examine the HTML source code for each step of the process.
An <ol> is included with a <li> for each step of the process at each step.
The <ol> is included in the accessibility tree.

Expected results

#2 and #3 are true

Current step indicated

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

Tests

This section is non-normative.

ARIA current

Procedure

Examine the source code of the HTML document.
Process navigation steps are included.
Current process step is identified using aria-current="step".

Expected results

Check #2 and #3 are true

Current step visually identifiable

Procedure

Visually examine the content.
Process navigation steps are viewable.
The current process step is visually distinguishable from other steps.

Expected results

Check #2 and #3 are true

Page/view change notified

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

Tests

This section is non-normative.

Opening new page

Procedure

Activate a link in the product that should open a new page/view.
Verify that the change is conveyed in the view.
Verify that the change is conveyed programmatically using the assistive technology in the accessibility support set.

Expected results

#2 and #3 are true

Return to start supported

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

Except when

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

Where the product is a sub-product then the starting point should be the sub-product starting point. For example, an organization’s careers website that is separate from the main website.

Tests

This section is non-normative.

HTML homepage link

Procedure

Select and view a website’s page other than the homepage.
Examine the source code of the HTML document.
Verify that there is a link that points to the website’s starting point.

Expected results

#3 is true

Return to start prominent

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

For HTML, a good programmatic positioning of such a mechanism would be early in the DOM.

Structure

Users can understand and navigate through the content using structure.

See also: Clear Language as these guidelines are closely related.

Relationships detectable

Relationships of meaning between elements are conveyed programmatically.

Tests

This section is non-normative.

HTML hierarchical relationship

Procedure

Determine the contextual hierarchy of the content either visually or through the meaning of the content.
Examine the source code of the HTML document to identify each hierarchical section.
Check that each section uses an appropriate semantic HTML element that reflects its position in the hierarchy.

Expected results

#3 is true

HTML input field/label relationship

Procedure

Identify all input fields within the unit of conformance through visual and code inspection.
Verify that each <input>, <select> and <textarea> in the source code has a programmatically associated <label> using for and id attributes.

Expected results

#2 is true

HTML list relationship

Procedure

Identify all lists within the unit of conformance through visual and code inspection.
Verify that each list consists of a <ul>, <ol> or <dl>.
Verify that each list item within the list is contained within an <li> element (for <ul> and <ol>) or <dt>/<dd> pair (for <dl>).
Verify that the immediate child element of the list is an <li> element (for <ul> and <ol>) or <dt>/<dd> pair (for <dl>).

Expected results

#2, #3 and #4 are true

HTML nested list relationship

Procedure

Identify all nested lists within the unit of conformance through visual and code inspection.
Verify that all child lists are contained within a <li> of the parent list.

Expected results

#2 is true

Blocks of content available (minimum)

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

Tests

This section is non-normative.

HTML sufficient space

Procedure

Identify meaningful blocks of content in the page/view that are not bounded by a visual border.
Examine the computed style to determine the total of margin, padding and border spacing.
The spacing between all adjacent meaningful blocks of content is sufficient.

Expected results

#3 is true

Programmatically identifiable meaningful blocks of content

Procedure

Identify meaningful blocks of content in the page/view.
Examine the source code to validate that an appropriate role is being used for the meaningful blocks of content.
Use assistive technology to validate that an appropriate role is being used for the meaningful blocks of content.

Expected results

#2 or #3 is true

Heading as a group

Procedure

Review content and identify meaningful blocks of content.
Examine the source code to validate that an appropriate role is being used for the meaningful blocks of content.
Use assistive technology to validate that an appropriate role is being used for the meaningful blocks of content.

Expected results

#2 or #3 is true

Sections labeled

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.

Add example(s) of labels and heading usage

Tests

This section is non-normative.

Meaningful label

Procedure

Review content and identify meaningful blocks with labels.
Each label correctly describes the block.

Expected results

#2 is true

Label exists

Procedure

Review content and identify meaningful blocks.
Each block has a label that describes the block.

Expected results

#2 is true

HTML heading semantics

Procedure

Visually identify each meaningful blocks.
Heading text is marked up using an <h?> element.

Expected results

#2 is true

Heading structure available

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

Except when

The technology does not support heading levels.

Tests

This section is non-normative.

Headings set at right level

Procedure

Review the hierarchy of headings.
Headings for sibling content blocks have the same heading level.
Headings for immediate child content blocks should be at most one level higher than parent content blocks.

Expected results

#2 and #3 are true

HTML Heading levels not skipped

Procedure

Review the hierarchy of headings.
Each heading level should be at most one numerical level higher than the preceding heading.

Expected results

#2 is true

Order detectable

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.

This includes lists and processes

Tests

This section is non-normative.

Process steps

Procedure

Review content and identify ordered processes.
Each step in the process includes an indicator of its position within the process.

Expected results

#2 is true

HTML ordered lists

Procedure

Review content and identify ordered lists.
Examine the HTML code and check that each ordered list is marked up with an <ol> element.

Expected results

#2 is true

Blocks of content available (enhanced)

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

Tests

This section is non-normative.

Visually identifiable meaningful blocks of content

Procedure

Identify meaningful blocks of content in the page/view.
Each meaningful block of content is grouped by one or more of the following characteristics:
- Color or lightness — the same color scheme is used (Note that this should also meet requirements for ‘Color alone’ and ‘Contrast’)
- Borders — blocks are contained within the same borders
- Spacing — blocks are grouped based on their proximity to others within the same area, while spacing is used to separate different sections of content
- Font — blocks are presented with similar font families
- Position — blocks are located in the same area of the page/view (for example, header, navigation, footer)
- Repeated visual feature — blocks contain a consistent visual feature (for example, bullets in a list, checkbox)

Expected results

#2 is true

Clear structure review

[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, and
- 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.
A copy of the style guide (if any) where clear structure review has been defined.

Key information usability testing

[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

No obstruction

Users can perceive and operate user interface components and navigation without obstruction.

Overlay content dismissible

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

Methods

The ‘Escape’ (Esc) key closes new content.
An accessible ‘close’ button is provided to close the new content.

Tests

This section is non-normative.

Modal dialogs on interaction

Procedure

Identify elements that open a modal dialog when interacted with.
Open the dialog.
Verify that the dialog includes a mechanism to allow the dialog to be dismissed.

Expected results

#3 is true

Infinite scrolling controllable

Where content includes infinite scrolling, a mechanism is provided prior to the scrolling content that allows users to switch off infinite scrolling. No content should be rendered unavailable as a result of switching on this option.

Tests

This section is non-normative.

Procedure

Identify instances of infinite scrolling.
Open the dialog.
Verify that the dialog includes a mechanism to allow the dialog to be dismissed

Expected results

#3 is true

Consistency across views

Consistency

Users have consistent and alternative methods for navigation.

Consistent structural order

The relative order of structural components remains consistent throughout each specific variation of product or process.

Applies when

In a set of pages/views

Relative order means that content can be added or removed, but repeated items are in the same order relative to each other.

Tests

This section is non-normative.

Consistent relative order for website

Procedure

For each variation of the product in scope:

Identify common structural components across multiple pages/views.
Verify that components are presented in the same order within each page/view.

Expected results

#2 is true

Consistent navigation order

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

Applies when

In a set of pages/views

This relates to consistency and terminology within blocks of navigation. The consistent ordering of blocks of navigation within a page/view is covered by ‘Consistent relative order’.

Tests

This section is non-normative.

Consistent main navigation relative order

Procedure

For each repeated blocks of navigation across multiple pages/views of the product or process:

Verify that the navigation items within each block of navigation have the same relative order across all pages/views of the product or process.

Expected results

#1 is true

Consistent navigation labels

The labelling of navigation items within blocks of navigation that are repeated on multiple pages/views of the product or process is consistent.

Except when

Labels for navigation items that are marked as ‘current’ within the product or process.

This relates to consistency and terminology within blocks of navigation. The consistent ordering of blocks of navigation within a page/view is covered by ‘Consistent relative order’.

Tests

This section is non-normative.

Consistent main navigation labels

Procedure

For each repeated block of navigation across multiple pages/views of the product or process:

Verify that the navigation items within each block of navigation have the same names across all pages/views of the product or process.

Expected results

#1 is true

Process and task completion

Avoid exclusionary cognitive tasks

Users can complete tasks without needing to memorize nor complete advanced cognitive tasks.

Automated entry allowed

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

Personal information includes names, passwords, et cetera.

Tests

This section is non-normative.

Procedure

Ensure there is a test identity set up in the browser.
Navigate to a form requiring the input of personal information.
Use browser tools to automatically populate personal information into the form.

Expected results

#3 is true

Cognitive test alternatives available

Processes, including authentication, can be completed without a cognitive function test.

Tests

This section is non-normative.

Procedure

Navigate to a form requiring the completion of a complex test, such as a puzzle, image identification, gesture reproduction, math question, or character recognition/entry.
Verify that there is an alternative provided that does not require completion of a cognitive function test.

Expected results

#2 is true

No memorization

Needs additional research

Processes can be completed without memorizing and recalling information from previous stages of the process.

Copying supported

Copying of content is not prevented.

Adequate time

Users have enough time to read and use content.

Timeout adjustable

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.

Tests

This section is non-normative.

Extend or disable at timeout

Procedure

Identify the presence of a time limit.
Verify if there is a way to disable it.
Wait for the timeout.
Verify that before the timeout, an option is given to extend the time limit.

Expected results

#3 is true.

No time limits

The completion of a process does not include time limits.

Except when

the time limit is essential, such as in an auction or timed exam.

Implying to a user that they will lose a benefit if they don’t act immediately is not an essential time limit.

Tests

This section is non-normative.

Procedure

Identify time limits in the page/view.
For each time limit, verify that it does not restart or reset immediately.

Expected results

#2 is true

No unnecessary time limits

[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.

Time limits conveyed

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

Applies when

products and processes have a time limit

Except when

hiding the existence of the time limit is essential

Tests

This section is non-normative.

Procedure

Identify the presence of a time limit.
Verify that a notification is provided to the user at the start of a process that the time limit exists, its length and that it can be adjusted.

Expected results

#3 is true.

Avoid deception

Users do not encounter deception when completing tasks.

Preselections visible

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

Tests

This section is non-normative.

Procedure

Identify all options that affect finance, privacy and safety.
For all identified in Step 1, verify that these are visible when completing a process.
For all identified in Step 1, verify that they are programmatically available before completing the process.

Expected results

#2 is true.
#3 is true.

No artificial time limits

The completion of a process does not include artificial time limits.

Except when

Time limit is essential such as in an auction, ticket sales, or a timed exam.

Tests

This section is non-normative.

Procedure

For each time limit:

Verify that it does not restart or reset immediately.

Expected results

#1 is true.

Deceptive practices usability testing

[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.
Maintain records of usability testing protocol, and results,
Disabilities represented within the group of participants.

Deceptive messaging expert review

[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.
Maintain records of deceptive practices found, and resolutions.

Retain information

Users do not have to reenter information or redo work.

Going back supported

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.

Tests

This section is non-normative.

Procedure

Identify any multi-step processes.
Verify that the user is prompted to review and confirm data.
Verify that the user is allowed to return to previous steps to review and change the data.
Verify that if a summary of all data input by the user is provided before the transaction is committed, and that a method is provided to correct errors, if necessary.

Expected results

#2 is true, or
#3 is true, or
#4 is true.

No redundant entry

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.

Tests

This section is non-normative.

Procedure

Identify any processes that require the user to enter information.
Check whether the information has already been requested ion a previous step of the process.
Verify that the information entered previously is prepopulated in the respective field(s) or is displayed on the page for copying.

Expected results

#3 is true.

Progress saved

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 (for example, an auction or concert ticket purchase), and no alternative to the time limit is possible.

Tests

This section is non-normative.

Procedure

Identify any processes that require the user to enter information.
Log in, if needed, and begin the timed activity.
Allow the session to time out.
Submit or save the data.
Log out if logged in.
Re-authenticate and log back in.
Verify that the process can continue from where you left off and be completed without loss of data, including the original data and any changes made after re-authentication.
Verify that the process used to save the information submitted in step 3 is not stored on the server. (Note: This requires knowledge of the technology and features used to implement the technique.)

Expected results

#7 is true.

Complete tasks

Users understand how to complete tasks.

Required action available

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. For example: the user needs to agree to the terms and conditions before they can submit the form.

Tests

This section is non-normative.

Procedure

Identify any parts of the process that cannot be completed without the user doing a required action.
Enter in all the information except for the required action(s).
Try to complete the process.
Verify that there is a notification that explains what the user needs to do before the process can be completed.

Expected results

#3 is true.

Information requirements available at start

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.

Tests

This section is non-normative.

Procedure

At the start of each process:

Identify any multi-step processes.
If it can be determined in advance, check that the number of steps it will take to complete the process is provided at the start of the process.
Verify that the details of any information and resources that are needed to perform the task are provided at the start of the process.
Verify that an overview of the process and next steps are provided at the start of the process.

Expected results

#2 is true.
#3 is true.
#4 is true.

Process instructions available

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

Applies when

The user needs to complete a multi-step process.

Tests

This section is non-normative.

Procedure

For each multi-step process:

Identify any multi-step processes.
Verify that the steps and instructions needed to complete a multi-step process are provided.
Verify that any breadcrumb navigation correctly communicates the current step in the process.

Expected results

#2 is true.

Unnecessary steps

Users can complete tasks without unnecessary steps.

Usability testing for unnecessary steps

[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):

Maintain 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.

Policy and protection

Risk

Users understand the benefits, risks, and consequences of options they select.

Risk comparable

Use of assistive technology, accessible alternative versions, accessibility-related modifications of digital content, and accessibility-related settings do not expose people with disabilities to additional risk.

Applies when

The product displays or requires entry of personal or sensitive information.

Additional risk includes risk to privacy, finances and personal safety — for example, unintentional exposure of a password or bank account number.

Tests

This section is non-normative.

Procedure

Identify information that is personal or sensitive.
Verify that personal or sensitive information is visually hidden by default.
Verify that the personal or sensitive information is programmatically hidden by default.
Verify that the use of AT, accessibility settings and accessibility-related modifications does not expose any personal or sensitive information.
Check whether any accessible alternative versions or modifications of the digital content exist.
Verify that the accessible alternative or modification of the digital content does not include additional risk beyond what’s in the inaccessible alternative.

Expected results

#2 is true.
#3 is true.
#4 is true.
#6 is true.

Consequences of choices explained

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.

Tests

This section is non-normative.

Procedure

Identify any choices being made by the user.
Identify any potential legal, financial, privacy and security consequences to the user as a result of the choice.
Verify that the consequences are provided when the user makes the choice.

Expected results

#3 is true.

Consequences explained before agreement

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

Applies when

Entering an agreement is required.

Tests

This section is non-normative.

Procedure

Identify any agreements being made by the user.
Identify any potential legal, financial, privacy and security consequences to the user as a result of the agreement.
Verify that the consequences are provided before the user enters into the agreement.

Expected results

#3 is true.

Diverse disabilities considered

[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

Algorithm inclusivity review

[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

Algorithms

Users are not disadvantaged or harmed by algorithms.

Inclusive data set

[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.

No harm from algorithms

[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 and feedback

Help available

Users have help available.

Consistent help available

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.

Tests

This section is non-normative.

Procedure

For each help item in a page / view:

Check that it is labeled consistently
Check that it remains in the same relative visual and programmatic location.

Expected results

#1 and #2 are true.

Contextual help available

Context-sensitive help is available.

Tests

This section is non-normative.

Procedure

For each form field that has input formatting requirements:

Check for other potentially confusing or difficult interactive elements.
For any element identified in #1 or #2, check for context-sensitive help that is helpful to the user.

Expected results

#2 is true.

Conversational support available

Conversational support allowing both text and speech formats is available.

Tests

This section is non-normative.

Procedure

Check that a conversational support mechanism is available.

Expected results

#1 is true

Disabled controls explained

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.

Tests

This section is non-normative.

Procedure

For each visible disabled control:

Check that instructions are available that explain how to enable them.

Expected results

#1 is true.

Data visualizations

Needs additional research

Editors are considering removal of this requirement.

Help is available to understand and use data visualizations.

New interfaces

Needs additional research

A mechanism to learn a new interface or revert to the older design is available

Applies when

Interfaces dramatically change due to redesign.

Except when

The new interface is essential.

Tests

This section is non-normative.

Procedure

When an interface has been redesigned, check that a tutorial is available or that the user is given an opportunity to revert to the previous design.

Expected results

#1 is true

Personalizable help

Needs additional research

Editors are considering removal of this requirement.

Help is adaptable and personalizable.

Sensory characteristics not relied on

Instructions and help do not rely on sensory characteristics such as shape, color, size, visual location, orientation, or sound.

Tests

This section is non-normative.

Procedure

For each reference to shape, size, or position of an object:

Check that the reference includes additional information that allows the item to be located and identified without any knowledge of its shape, size, or relative position.

Expected results

#1 is true.

Support available

Needs additional research

Support is available during data entry, task completion and search.

Except when

The content does not include one or more of the mentioned processes. For example, when the content does not include search, there is no requirement for support to be available for search.

Supported decision-making review

[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.

Help usability testing

[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

Feedback

Users can provide feedback to content author(s).

Feedback mechanism available

A mechanism is available to provide feedback to authors.

Tests

This section is non-normative.

Procedure

Check that a feedback mechanism exists.
Check that the feedback is sent to authors.

Expected results

#1 and #2 are true.

User control

Assistive techology control

Users can control content settings from their user agents including assistive technology.

Assistive technology supported

Content can be controlled using assistive and adaptive technology.

Tests

This section is non-normative.

Procedure

Using assistive technology:

interact with the controls in a page / view. Check that each control can be operated using the assistive technology and that operating the controls achieves the same results with and without assistive technology.
interact with non-interactive content in a page / view. Check to see that the same results are achieved with and without assistive technology.

Expected results

#1 and #2 are true.

User settings supported

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

Accessibility-related user settings include font size, icon size, color scheme, magnification, and motion.

Tests

This section is non-normative.

Procedure

For each setting:

Change an accessibility-related setting in a platform or user agent in the accessibility support set.
Check content to see that the setting has been applied.

Expected results

#2 is true

Virtual cursor supported

Assistive technologies can access content and interactions when using mechanisms that convey alternative points of regard or focus (i.e. virtual cursor).

Tests

This section is non-normative.

Procedure

For each setting:

Access content and interactions by using mechanisms that convey alternative points of regard or focus
Check that content is readable and interactions are operable.

Expected results

#2 is true

Notifications adjustable

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.

Tests

This section is non-normative.

Procedure

For each notifications:

check that settings allow the timing or location to be changed.

Expected results

#1 is true

Control text

Users can control text presentation.

Background adjustable

Patterns, designs, or images placed behind text are avoided or can be removed by the user.

Font size not relied on

When font size conveys visual meaning (such as headings), the text maintains its meaning and purpose when text is resized.

Adjustable viewport

Users can adjust the size and orientation of the viewport, adjust text size of content, or zoom content without loss of legibility or functionality.

Orientation supported (minimum)

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.

For extended reality, the platform default orientation aligns with the real world orientation.

Content does not have to re-layout or change aspect ratio in a different orientation, it just needs to display in the device orientation.

Tests

This section is non-normative.

Procedure

For platforms which have a default orientation:

Open the content.
Check that the orientation aligns with the platform default.

For platforms which do not have a default orientation:

Open the content
Check that the orientation can align with both portrait and landscape orientations.

Expected results

#2 is true

Orientation supported (enhanced)

Content supports both portrait and landscape orientations.

Except when

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

Tests

This section is non-normative.

Procedure

For platforms which do not have a default orientation:

Open the content
Check that the orientation can align with both portrait and landscape orientations.

Expected results

#2 is true

Text reflow supported

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. For example, preformatted text such as code, poems, maps, or comics.

Other languages may have other rules around line breaking: https://r12a.github.io/scripts/script-features/index.html

Tests

This section is non-normative.

HTML paragraph reflow without requiring scrolling in two dimensions

Procedure

Set the viewport at 320 CSS pixels in the direction of text.
Identify all the blocks of text within the scope.
Verify that each block of text does not require scrolling into two dimensions.
Verify that the text in each block of text is legible.

Expected results

#3 and #4 are true

Layout reflow supported

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, electronic program guides.
Canvases of presentational content. For example, slides.
Multiple palettes or panels that act on content. For example, Photoshop, IDE.

All block-level elements fit within a 320px inline-size without requiring scrolling in more than one direction.

Tests

This section is non-normative.

Procedure

Set the viewport at 320px in the direction of text.
Verify that each section of content fits within 320 CSS pixels.

Expected results

#2 is true

Media control

Users can control media and media alternatives.

Page/view audio adjustable

There are mechanisms 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.

Mechanisms include controls on each instance of content, or a single app-wide control that disables audio, for example: app-wide earcons.

Tests

This section is non-normative.

Procedure

Load a page / view.
Check for audio that starts automatically.
For audio content in a media player, check that the media player has controls that can pause, stop, or adjust the audio volume.
For audio content set at an application level, check that there is a central setting that enables or disables audio across the application.
Check that one of these are present: a. There is a mechanism within the first three elements in the page / view for the user to pause, stop, or adjust the audio volume; b. There are keyboard controls that can pause, stop, or adjust the audio volume.

Expected results

#3 or #4 or #5 is true

Media alternatives searchable

Alternatives for media can be searched and queried.

Tests

This section is non-normative.

Procedure

For each instance of media with captions and / or transcripts:

Check that a mechanism to search the captions or transcripts is available.
Check that a mechanism to search and look up terms in transcripts is available. This can be:
1. copying and pasting content from the transcript into a dictionary; or
2. allowing a platform or application dictionary to show a definition of the term.
  - Example: VoiceOver on MacOS includes a feature to look up terms for what is under a ‘mouse cursor point’

Expected results

#1 and #2 are true.

Media alternatives controllable

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

Tests

This section is non-normative.

Procedure

For each media asset with audio content:

Check that a mechanism is available so that users can turn on and off the closed captions.
Check that a mechanism is available so that users can change the audio track from a non-audio-described one to an audio-described.

Expected results

#1 and #2 are true.

Media chapters available

Needs additional research

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.

Tests

This section is non-normative.

Procedure

For media that lasts five minutes or more:

Play the media
Check that the media is divided up using chapters
Check that the chapter titles have descriptive names which are suitable for their content.

Expected results #2 and #3 are true

Content changes

Users know when content changes.

Change of content notified

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 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.

Tests

This section is non-normative.

Procedure

For each meaningful change of visual content:

Check that the change is conveyed programmatically using the assistive technology in the accessibility support set.

Expected results

#1 is true

Change of focus notified

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

Tests

This section is non-normative.

Procedure

For each instance of focus being changed by the content:

Verify that the change is conveyed visually and programmatically using the assistive technology in the accessibility support set.

Expected results

#1 is true

Change of user agent notified

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

Tests

This section is non-normative.

Procedure

For each instance where the content triggers a change of device or user agent change:

Check that the change is conveyed before the chance occurs.

Expected results #1 is true

Introduction

About this draft

Draft requirements

Section status levels

About WCAG 3

Guidelines

Images and media

Image alternatives

Images detectable

Decorative images hidden

Image alternatives available

Image types identified

Alternative text editable

Image alternatives style guide

Media alternatives

Transcripts available

Media alternatives equivalent

Media alternatives findable

Speakers identified

Speaker language identified

Sounds identified

Visual information identified

Non-verbal cues identified

Sign language available (prerecorded)

Sign language available (live)

Media alternatives style guide

Accessible video player selected

Media alternatives usability testing

Reviewed by content authors

Non-text alternatives

Non-text content not relied on

Captions

Captions adjustable

Captions available (prerecorded)

Captions available (live)

Captions unobstructed

Captions synchronized

Caption features available

Captions consistent

Captions centered (immersive)

Captions controllable

Direction indicated (immersive)

Audio descriptions

Audio descriptions available (prerecorded)

Audio descriptions synchronized

Audio descriptions available (live)

Extended audio descriptions available

Audio description volume adjustable

Audio description language adjustable

Figure captions

Persistent captions

Single sense

Hue not relied on

Graphical object contrast sufficient

Visual depth not relied on

Sound not relied on

Spatial audio not relied on

Text and wording

Text appearance

Blocks of text readable (minimum)

Text style readable (minimum)

Text contrast sufficient (minimum)

Blocks of text adjustable

Text style adjustable

Text size adjustable

Text color adjustable

Blocks of text readable (enhanced)

Text style readable (enhanced)

Text contrast sufficient (enhanced)

Text customizations retained

Text-to-speech

Text detectable

Human language detectable

Text appearance not relied on

Numerical metadata available

Clear language

Abbreviations explained

Non-literal language explained

Summaries available

Common words used