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.

This is an update to W3C Accessibility Guidelines (WCAG) 3.0. It includes all requirements that have reached the developing status.

To comment, file an issue in the wcag3 GitHub repository. Create separate GitHub issues for each comment, rather than commenting on multiple topics in a single issue. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, email public-agwg-comments@w3.org (comment archive).

In-progress updates to the guidelines can be viewed in the public Editor's Draft.

Introduction

Summary

About this draft

This draft includes an updated list of the potential guidelines, requirements, and assertions that have progressed to Developing status.

Requirements and assertions at the Exploratory status are not included in this Working Draft. If you would like to see the complete list, please review the Editor's Draft.

Please consider the following questions when reviewing this draft:

Additionally, the Working Group welcomes any research that supports requirements or assertions.

To provide feedback, please open a new issue in the WCAG 3 GitHub repository. Create a separate GitHub issue for each topic, rather than commenting on multiple topics in a single issue.

If it's not feasible for you to use GitHub, email your comments to public-agwg-comments@w3.org (comment archive). Please put your comments in the body of the message, not as an attachment.

Draft requirements

The list of requirements is longer than the list of success criteria in WCAG 2. This is because:

The final set of requirements in WCAG 3 will be different from what is in this draft. Requirements are likely to be added, combined, and removed. We also expect changes to the text of the requirements. Only some of the requirements will be used to meet the base level of conformance.

Section status levels

As part of the WCAG 3 drafting process, each normative section of this document is given a status. This status is used to indicate how far along in the development this section is, how ready it is for experimental adoption, and what kind of feedback the Accessibility Guidelines Working Group is looking for.

About WCAG 3

This specification presents a new model and guidelines to make web content and applications accessible to people with disabilities. W3C Accessibility Guidelines (WCAG) 3.0 supports a wide set of user needs, uses new approaches to testing, and allows frequent maintenance of guidelines and related content to keep pace with accelerating technology changes. WCAG 3 supports this evolution by focusing on the functional needs of users. These needs are then supported by guidelines that are written as outcome statements, requirements, assertions, and technology-specific methods to meet those needs.

WCAG 3 is a successor to Web Content Accessibility Guidelines 2.2 [[WCAG22]] and previous versions, but does not deprecate WCAG 2. It will also incorporate some content from and partially extend User Agent Accessibility Guidelines 2.0 [[UAAG20]] and Authoring Tool Accessibility Guidelines 2.0 [[ATAG20]]. These earlier versions provided a flexible model that kept them relevant for over 15 years. However, changing technology and changing needs of people with disabilities have led to the need for a new model to address content accessibility more comprehensively and flexibly.

There are many differences between WCAG 2 and WCAG 3. The WCAG 3 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; visual and auditory media; virtual and augmented reality; and alternative access presentation and control methods. 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 to determine whether the need has been met. Guidelines are also supported by technology-specific methods to meet each requirement.

Content that conforms to WCAG 2.2 Level A and Level AA is expected to meet most of the minimum conformance level of this new standard but, since WCAG 3 includes additional tests and different scoring mechanics, additional work will be needed to reach full conformance. Since the new standard will use a different conformance model, the Accessibility Guidelines Working Group expects that some organizations may wish to continue using WCAG 2, while others may wish to migrate to the new standard. For those that wish to migrate to WCAG 3, the Working Group will provide transition support materials, which may use mapping and other approaches to facilitate migration.

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

Image and media alternatives

Image alternatives

Users have equivalent alternatives for images.

Which foundational requirements apply?

For each image:

  1. Would removing the image impact how people understand the page?
  2. Is the image presented in a way that is available to user agents and assistive technology?
  3. Is an equivalent text alternative available for the image?
Detectable image

Non-decorative images are detectable

Applies when when content includes non-decorative images.

Tests

This section is non-normative.

Procedure

  1. For each image on a page, decide if the image is decorative or non-decorative
  2. 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

  • #2a or #2b is true.
Decorative image

Decorative images are programmatically hidden.

Tests

This section is non-normative.

(General) No accessible name

Procedure

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

Expected results

  • #2 is true.

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

Procedure

  1. Check for any images that add no information to the content.
  2. Check that title, aria-label, aria-labelledby etc. is either absent or empty.
  3. Check that an alt attribute is present and empty.

Expected results

  • #2 is true.
  • #3 is true.
Equivalent text alternative

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

  1. Remove, hide, or mask the image.
  2. Replace it with the text alternative.
  3. Check that the meaningful content in the image is described by the text alternative).
  4. 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 type

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:

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

Expected results

  • #2 is true.
Editable alternatives

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

  • #1a is true.
  • #1b is true,.
Image alternatives style guide

We assert that we follow an organizational style guide for image text alternatives.

Tests

This section is non-normative.

Information that needs to be included

  • Title, role or organization making the assertion
  • Date of assertion

Media alternatives

Users have equivalent alternatives for audio and video content.

Transcripts available

Transcripts are available for all audio and video content.

Except when

  • Except when the audio or video content is an alternative for text and clearly labelled as such.
  • Except when it is a background video with no spoken content.
Tests

This section is non-normative.

(General) Transcript is available

Procedure

  1. Identify all audio or video within the unit of conformance through visual inspection.
  2. Determine that a transcript is available for each instance of audio and video content.

Expected results

  • #2 is true.
Equivalent media alternatives

Equivalent media alternatives are available for audio and video content.

Except when except when it is a background video with no spoken content.

Tests

This section is non-normative.

Media alternative is equivalent

Procedure

  1. Check that the audio or video content has a media alternative.
  2. Check that the content of the media alternative is equivalent to the meaningful information in the media content.

Expected results

  • #2 is true.
Findable media alternatives

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

Except when 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

  1. Identify all audio or video content within the unit of conformance through visual inspection.
  2. A text description or link to a text description is provided for each audio or video.

Expected results

  • #2 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

  1. Check for any speakers in the audio or video content.
  2. Check that each speaker in the audio or video is consistently identified in the transcript.

Expected results

  • #2 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 incidental word usage.

Tests

This section is non-normative.

Language identified in transcripts

Procedure

  1. Identify all audio or video transcripts that include multiple languages.
  2. Part(s) using a language different from the original language is programmatically determined in the media alternatives.

Expected results

  • #2 is true.
Meaningful sounds

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 except when it is a decorative video.

Applies when applies when there is sound.

Tests

This section is non-normative.

Meaningful sounds in captions

Procedure

  1. Identify all audio or video with captions within the unit of conformance.
  2. Identify which ones include meaningful non-verbal audio.
  3. Captions include a description of the meaningful non-verbal audio.

Expected results

  • #3 is true.
Meaningful visual information

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

  1. Check the content in the audio or video for any meaningful visual information.
  2. Check that the transcript includes a description of any visual information needed to understand the content of the audio or video.
  3. Check that the audio description includes a description of any visual information needed to understand the content of the audio or video.

Expected Results

  • #2 and #3 are true.
Non-verbal cues

Needs additional research

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

Tests

This section is non-normative.

Procedure

  1. Identify all audio content that include nonverbal cues.
  2. Check if media alternatives explain audio nonverbal cues, such as tone of voice, facial expressions, body gestures, or music with emotional meaning.

Expected results

  • #2 is true.
Sign language prerecorded

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

Except when except when it is a decorative background sound.

Tests

This section is non-normative.

Sign language for audio only

Procedure

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

Expected results

  • #2 is true.
Sign language live

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

Tests

This section is non-normative.

Information that needs to be included publically

  • 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

Content author(s) assert that they follow a style guide that includes guidance on media alternatives.

Tests

This section is non-normative.

Information that needs to be included publically

  • 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).
  • Summary of the needs of users involved.
  • Identified issues and details of solutions applied.
Video player supports media alternative

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 applies when a video is used that does not play in standard browsers.

Tests

This section is non-normative.

Information that needs to be included publically

  • 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)

  • Video player documentation exists detailing functional support for media alternatives.
Testing media alternatives with users

tests were conducted with users who need media alternatives, and the issues were fixed based on the findings.

  • Scope
  • Types of disabilities each user had
  • Number of users (for each type of disability)
  • Date of testing
  • Examples of fixed issues based on the results
Tests

This section is non-normative.

Information that needs to be included publically

  • 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).
  • Summary of the needs of users involved.
  • Identified issues and details of solutions applied.
Reviewed by content authors

Content author(s) have reviewed the media alternatives.

  • Role of the creator
  • Number of creators (for each Role)
  • Date (Period) of review
  • Examples of fixed issues based on the feedback

Non-text alternatives

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

Non text content

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

  1. Examine the source code of the HTML document to identify all non-decorative img elements.
  2. Each img element has an alt attribute.
  3. The alt attribute provides a text alternative which conveys meaning or content that is displayed visually.
  4. 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

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

Expected Results

  • #2 and #3 are true

Captions

Users have captions for the audio content.

Adaptable captions

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:

  1. Check if 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 prerecorded

Captions are available for all prerecorded audio content.

Except when 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:

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

Captions are available for all live audio content.

Tests

This section is non-normative.

Procedure For all live audio content:

  1. Check if captions are provided

Expected Results

  • #1 is true
Captions avoid obstruction

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:

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

Expected Results

  • #1 is true
Captions are synchronized

Captions are synchronized with the audio content of synchronized media.

Tests

This section is non-normative.

Procedure For each caption:

  1. Check if it is in sync with video content

Expected Results

  • #1 is true
Enhanced caption features

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:

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

Expected Results

  • #2 is true
Consistent captions

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:

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

Expected Results

  • #2 is true.
Captions location 360

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

Applies when 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:

  1. Check if captions remain directly in front of the user.

Expected Results

  • #1 is true.
Controllable captions

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:

  1. Check if content with captions provides a mechanism to turn on and off the captions. Expected Results
  • #1 is true
Visual indicators 360

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 caption in 360-degree digital environments, when audio is heard from outside the current view:

  1. Indicate the direction of a sound or speech.

Expected Results

  • #1 is true

Audio descriptions

Users have audio descriptions for video content.

Audio descriptions prerecorded

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

Except when

  • 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:

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

Expected Results

  • #1 is true
Audio description timing

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

Except when except when there are no audio descriptions.

Tests

This section is non-normative.

Procedure For synchronized media with audio description:

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

Expected Results

  • #1 and #2 are true
Audio descriptions live

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

Tests

This section is non-normative.

Procedure

  1. Find a live media broadcast
  2. Check that a secondary audio option exists that provides live audio description of the broadcast.

Expected results

  • #2 is true.
Extended audio description

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

  • 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:

  1. Play the media with the extended audio description on.
  2. 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

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:

  1. Play the media with audio description on.
  2. 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

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:

  1. Check that a version of the media has audio description available in alternative languages.
  2. 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.

Use of hue

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

  • Identify everywhere 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
Use of visual depth

Information is not conveyed through visual depth alone.

Tests

This section is non-normative.

Procedure

  1. Identify everywhere information is conveyed by visual depth.
  2. For each instance identified in #1, identify the instances where the visual depth conveys information.
  3. 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.
Use of sound

Information is not conveyed by sound alone.

Except when

  • Content is audio-based media.

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.

Tests

This section is non-normative.

Procedure

  1. Identify everywhere information is conveyed by sound.
  2. For each instance identified in #1, identify the instances where the sound conveys information.
  3. 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

  • #3 is true for all instances
Use of spatial audio

Information is not conveyed by spatial audio 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.

Tests

This section is non-normative.

Procedure

  1. Identify everywhere information is conveyed by spatial sound.
  2. For each instance identified in #1, identify the instances where the sound conveys information.
  3. 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

  • #3 is true for all instances

Text and wording

Text appearance

Users can read visually rendered text.

Which foundational requirements apply?

For each word of text:

  1. Is the text purely decorative or, is it not readable by anybody?
    • Yes, Pass
    • No, Continue
  2. Does the default/authored presentation meet minimum requirements?
    1. Yes, the default/authored presentation meets Readable Blocks of Text (foundational) and Readable Text Style (foundational), Continue
    2. No, Fail
  3. Can the text appearance be adjusted by the user without loss of content or functionality?
    1. Yes, text must be user-manipulable text and:
      1. The accessibility support set meets:
        1. Adjustable blocks of text
        2. Adjustable text style
      2. Pass
    2. Yes, via product-provided themes:
      1. Adjustable blocks of text
      2. Adjustable text style
      3. Pass
    3. No, and the product does not provide its own themes:
      1. Fail.
Readable blocks of text (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.

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

Readable blocks of text (minimum) and Readable text style (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:

  1. 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.
Readable text style (minimum)

Needs additional research

The default/authored presentation 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.

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.

Readable blocks of text (minimum) and Readable text style (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:

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

For this foundational level requirement, the default minimum contrast level should be roughly equivalent to the WCAG2 4.5:1 level for small/body text.

Tests

This section is non-normative.

Procedure

For each foreground and background combination of text:

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

Expected results

  • #3 is true
Adjustable blocks of text

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 content is hard-coded (e.g., the raw text 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
Inline margin
Block Margin
Line length
Line height
Justification Not applicable Default inline start to Left aligned

Readable blocks of text (minimum) and Readable text style (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 piece of text:

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

Expected results

  • #2 is true.
Adjustable text style

Needs additional research

The presentation of each of the following font features 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 content is hard-coded (e.g., the raw text 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

Readable blocks of text (minimum) and Readable text style (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:

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

Expected results

  • #2 is true.
Adjustable text size

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 piece of text:

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

Expected results

  • #2 is true.
Adjustable text colors

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 piece of text:

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

Expected results

  • #2 and #4 are true.
Readable blocks of text (enhanced)

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.

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

Readable blocks of text (minimum) and Readable text style (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:

  1. 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.
  2. 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.
Readable text style (enhanced)

Needs additional research

The default/authored presentation 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.

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

Readable blocks of text (minimum) and Readable text style (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:

  1. 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.
  2. 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 (enhanced)

Needs additional research

The default visual presentation of text meets @@[X contrast measure, at a higher level than the foundational requirement for Text contrast (minimum)].

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.

For this supplemental level requirement, the default minimum contrast level should be roughly equivalent to the WCAG2 7:1 level for small/body text.

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:

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

Expected results

  • #3 is true.
Exported/saved/prints supports text-appearance customizations

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

Applies when

  • the page/view can be exported or printed option.

Examples of interoperable formats include:

  • PDF
  • HTML
  • SVG
  • OpenDocument

Examples of non-interoperable formats include:

  • Scriptable Network Graphics
  • DOCX, unless you know your audience has the required software (for example, you’re writing internal documents for your company which provides employees with the necessary software)
  • Java object code
Tests

This section is non-normative.

Procedure

  1. Customize a page/view by adjusting aspects of the text appearance, such as size, style, and color.
  2. Export, save, and print the content.
  3. 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

  1. Identify all visible text.
  2. 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.
  3. 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

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

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

Expected results

  • #2 is true.
Use of text appearance

Meaning conveyed by text appearance 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

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

Expected results

  • #2 is true.
Unambiguous numerical formatting

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

Tests

This section is non-normative.

Procedure

  1. Identify any dates, temperatures, times, and Roman numerals that are presented visually.
  2. Check that it uses an unambiguous format.
  3. 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 AG, 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

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

  1. Check for any abbreviations in the content.
  2. Check that an explanation is available for the first use of the abbreviation.

Expected result

  • #2 is true.
No nested clauses

Sentences do not include nested clauses.

Except when

  • content provides legal or technical information.
Tests

This section is non-normative.

Procedure

For each sentence:

  1. Identify all nested clauses in the sentence (introduced by nesting conjunctions such as ‘because’, ‘although’, ‘if’, ‘that’, ‘which’, ‘who’, ‘when’, and ‘where’).

  2. Check that each initial nested clause does not contain other nested clauses within it.

  3. Check that a technology in the accessibility support set meets ‘No nested clauses’.

Expected results

  • #2 is true, or
  • #3 is true.
Non-literal language

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

Except when text is poetic, scriptural, artistic, or expressive rather than informational.

Translation software and other tools can aid human reviewers in identifying non-literal language.

Tests

This section is non-normative.

Procedure

For each phrase of non-literal language:

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

Expected results

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

Needs additional research

A summary is available for long-form written 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, confirm each of the following is true:

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

Expected results

  • #1 is true.
  • #2 is true.
  • #3 is true.
Common words

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

This requirement is not foundational 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:

  1. Check whether the word appears in the 1,500 most common words in a high-frequency corpus for the language used.
  2. 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.
  3. Check that a technology in the accessibility support set meets ‘Common words.’

Expected results

  • #1, #2, or #3 is true.
No missing letters or diacritics

Letters or diacritics required to identify the correct meaning of each word are available.

Applies when

  • a human language has a version that removes letters or diacritics for proficient readers.

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

Tests

This section is non-normative.

Procedure

  1. Check for content that has missing letters or diacritics.
  2. Check that an alternative version is provided that includes letters or diacritics needed to identify the correct meaning of each word.
  3. Check that the accessibility support set meets ‘No missing letters or diacritics’.

Expected results

  • #2 is true, or
  • #3 is true.
No unnecessary words

Sentences do not include unnecessary words or phrases.

Except when

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

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

Tests

This section is non-normative.

Procedure

  1. Check that the written content does not include unnecessary words or phrases.

Expected results

  • #1 is true.
Numerical alternatives

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

Complex numerical information can increase cognitive load, especially for users with dyscalculia or low numeracy. Providing written explanations or visualizations can aid understanding.

Tests

This section is non-normative.

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

Expected result:

  • #2 is true.
Clear language review process

Our organization has a process and policy to review written content for clear language before publication. The process includes confirming:

  • All of the foundational 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 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 to include 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

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

Information to include 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

Which foundational requirements apply?

For each focusable item:

  1. Is the user agent default focus indicator used?
  2. Is the focus indicator defined by the author?
Custom focus indicator

The user agent’s default focus indicator is replaced by a custom focus indicator that has sufficient size, change of contrast, adjacent contrast, and adjacency.

User agent default focus indicator

The focusable item uses the user agent default focus indicator.

Supplementary indicators

@@

Focus indicator style guide

Content author(s) follow a style guide that includes guidance on focus indicators.

Pointer focus appearance

Users can see the location of the pointer focus.

Pointer visible

There is a visible indicator of pointer focus.

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 in viewport

The focus does not move to a position outside the current viewport, unless a mechanism is available to return to the previous focus point.

Focus retention

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.

Keyboard focus order

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

Relevant focus

The focus order does not include repetitive, hidden, or static elements.

Expected behavior

Users can navigate using interactive components that behave as expected.

Consistent interaction

Interactive components with the same functionality behave consistently.

Consistent labels

Interactive components with the same functionality have consistent labels.

Consistent visual design

Interactive components that have similar function and behavior have a consistent visual design.

Control location

Needs additional research

Interactive components are visually and programmatically located in conventional locations.

Conventions

Needs additional research

Interactive components follow established conventions.

Familiar component

Conventional interactive components are used.

Reliable positioning

Interactive components retain their position unless a user changes the viewport or moves the component.

Control information

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

Control contrast

Needs additional research

Visual information required to identify user interface components and states meet a minimum contrast ratio test, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author.

Control importance

Needs additional research

The importance of interactive components is indicated.

Control labels

Interactive components have visible labels that identify the purpose of the component.

Control updates

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

Distinguishable controls

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

Field constraints

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

Input labels

Inputs have visible labels that identify the purpose of the input.

Label in name

The programmatic name includes the visual label.

Name, role, value, state

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

Input / operation

Keyboard interface input

Users can navigate and operate content using only the keyboard.

All elements keyboard actionable

All elements that can be controlled or activated by pointer, audio (voice or other), gesture, camera input, or other means can be controlled or activated from the keyboard interface.

All content 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 input, and any other means of input or control.

The All Elements Keyboard-Actionable 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.

Bidirectional navigation

It is always possible to move forward and backward at each point using keyboard navigation.

We are considering making this require that the navigation be symmetrical (ie., if you navigate forward and then backward you always end up back in the same place) but are interested in comments on this.

Conflicting keyboard commands

Author-generated keyboard commands do not conflict with standard platform keyboard commands or they can be remapped.

Keyboard navigable if responsive

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

No keyboard trap

It is always possible to navigate away from an element after navigating to, entering, or activating the element by using a common keyboard navigation technique, or by using a technique described on the page/view or on a page/view earlier in the process where it is used.

User control of keyboard focus

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.

Methods & best practices

  • Method: Move the keyboard focus only when the user advances it with a common keyboard command or interacts with an interactive element. Avoid automatically moving the keyboard focus without user interaction.
Tests

This section is non-normative.

Procedure

  1. Using the keyboard, complete all functionality within the conformance scope.
  2. Pause (do not interact) at various times. Note: #1 and #2 is often done during other manual testing.
  3. Verify that the focus moves as a result of user interaction.
  4. If the focus moves automatically, verify that you were notified prior to the movement or it results from a security or emergency situation.

Expected Results

  • #3 is true.
  • #4 is true for all instances that focus moves automatically.
Relevant tab order keyboard focus

Except for skip links and other elements that are hidden but specifically added to aid keyboard navigation, tabbing does not move the keyboard focus into 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.

Physical or cognitive effort when using keyboard

Users can use keyboard without unnecessary physical or cognitive effort.

Logical keyboard focus order

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

Standard or described navigation keys

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
Preserve keyboard focus

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.

When the previous focus location no longer exists, best practice is to put focus on the focusable location just before the one that was removed. An example of this would be a list of subject-matter tags in a document, with each tag having a delete button. A user clicks on the delete button in a tag in the middle of the tag list. When the tag is deleted, focus is placed onto the tag that was before the now-deleted tag.

This is also quite useful when moving between pages but this would usually have to be done by the browser, unless the user is in some process where that information is stored in a cookie or on the server between pages in the process so that it still has the old location when the person returns to the page.

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.

Comparable keyboard effort

Content author(s) follow 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.

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

Pointer input

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

Pointer cancellation

For functionality that can be activated using a simple pointer input, at least one of the following is true:

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
Essential
Completing the function on the down event is essential
Simple pointer input

Any functionality that uses pointer input other than simple pointer input can also be operated by a simple pointer input, or a sequence of simple pointer inputs, that do not require timing.

Examples of pointer input that are not simple pointer input are double clicking, swipe gestures, multipoint gestures like pinching or split tap or two-finger rotor, variable pressure or timing, and dragging movements.

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.

Consistent pointer cancellation

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

Except when

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

Pointer pressure alternative

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

Except when

  • Specific pressure is essential to the functionality.
Pointer speed alternative

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

Except when

  • Specific pointer speed is essential to the functionality.

Speech and voice input

Provide alternatives to speech input and facilitate speech control.

Speech alternative

Speech input is not the only way of achieving any functionality except where a speech input is essential to the functionality.

Real-time bidirectional voice communication

Wherever there is real-time bidirectional voice communication, a real-time text option is available.

Input operation

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

Change keyboard focus with pointer device

If content interferes with pointer or keyboard focus behavior of the user agent, then selecting anything on the view with a pointer moves the keyboard focus to that interactive element, even if the user drags off the element (so as to not activate it).

Content on hover or keyboard focus

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, all of the following are true:

Dismissible
A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content does not obscure or replace other content
Hoverable
If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing
Persistent
The additional content remains visible until the hover or keyboard focus trigger is removed, the user dismisses it, or its information is no longer valid

Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML title attribute.

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.

Path based gesture alternative

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

Except when

  • A path-based gesture is essential to the functionality.
Input method flexibility

Where functionality, including input or navigation, is achievable using different input methods, users have the option to switch between those input methods 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.

Use without body movement

Full or gross body movement is not the only way of achieving any functionality.

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.

Use without eye tracking

Content and functionality does not rely solely on eye tracking alone.

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.

Focus from pointer

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.

Need to investigate the behavior in other contexts, e.g. touch-screen with bluetooth keyboard.

Methods & best practices

  • Mouse events are not added to non-interactive elements to prevent clicking for focus.
Tests

This section is non-normative.

Procedure

  1. Check for click events on non-interactive elements.

Expected Results

  • #1 is true

Authentication

Users have alternative authentication methods available to them.

Biometric identification

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

Voice identification

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

Biometric identification (minimum)

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

Biometrics includes vocal patterns and other voice characteristics.

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:

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

Expected Results

  • #1 is true

Error handling

Correct errors

Users know about and can correct errors.

Error notification

Errors that can be automatically detected are identified and the problem is clearly described to the user.

Examples of errors include invalid form input, server errors or application errors.

Tests

This section is non-normative.

Procedure 1.Identify parts of the conformance scope where errors can occur. 2. Trigger errors. 3. For each error, verify that the nature of the problem is identified and described

Expected results

  • #3 is true for each error.
Error suggestion

Error messages include suggestions for corrections.

Except when it would jeopardize the security or purpose of the content.

Tests

This section is non-normative.

Procedure

  1. Review all error messages.
  2. Verify that the error messages include suggestions for how to fix the error.

Expected Results

  • #2 is true
Error visibility

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

  • An internally consistent symbol.
  • Color that differentiates the error message from surrounding content.
  • Text that clearly indicates the error.
Tests

This section is non-normative.

Procedure

  1. Identify all validation errors.
  2. Verify that they meet at least two of the listed requirements.

Expected results

  • #2 is true
Error persists

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

  1. Identify the error messages.
  2. Verify that the error messages persist until the user fixes the error or dismisses the message.

Expected Results

  • #2 is true
Input errors

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

Examples of failing validation:

  • When input is required and the field is left empty.
  • When the user input does not meet the requested format.
Tests

This section is non-normative.

Procedure

  1. Identify validation errors.
  2. Verify that validation errors are indicated visually.
  3. Verify that validation errors are indicated programmatically.

Expected Results

  • #2 and #3 are true.
Error location

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.

Tests

This section is non-normative.

Procedure

  1. Zoom in 400%
  2. Trigger errors
  3. 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.

Error prevention

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.

Submission confirmation

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

Applies when data submission has succeeded or failed

Validation timing

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

  • when the user leaves the field, or
  • when the form is submitted.
Design to reduce mistakes

[Title, role or organization] assert 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:

  • Title, role or organization making the assertion
  • Date of assertion
  • 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.

Avoid flashing

Content does not include non-essential flashing.

Method(s)

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

This section is non-normative.

Procedure

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

Expected Results

  • #1 is false, or
  • #2 is true
No flashing

Content does not include flashing.

Method(s)

  • Design content without using flashing.
Tests

This section is non-normative.

Procedure

  1. Identify if content includes flashing.

Expected Results

  • #1 is false
Avoid visual motion

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

Method(s)

  • Consider if motion or pseudomotion is essential, and if it is not, refrain from including it.
Tests

This section is non-normative.

Procedure

  1. Identify if content includes visual motion or pseudomotion.
  2. For each instance, identify if the visual motion or pseudomotion is essential.

Expected Results

  • #1 is false, or
  • #2 is true
No visual motion

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

Method(s)

  • Design content without using visual motion or pseudomotion.
Tests

This section is non-normative.

Procedure

  1. Identify if content includes visual motion or pseudomotion.

Expected Results

  • #1 is false
Trigger warning

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

  1. Identify triggers.
  2. For triggers, check if a warning is provided before the user encounters the trigger.
  3. For triggers, check that the same information is available without triggers.

Expected Results

  • #2 and #3 are true
Manage haptic stimulation

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

  1. Identify any haptic feedback that is caused by the digital content (vs. the operating system or user agent).
  2. Identify if there is a setting that allows for reducing or turning off the haptic feedback.

Expected Results

  • #1 is false, or #1 and #2 are true
Manage audio shifting

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

  1. Check for any audio shifting that is caused by the digital content (vs. the operating system or user agent).
  2. Check if there is a setting that allows for pause or turning off the audio shifting.

Expected Results

  • #2 is true
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.

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 layouts

[Title, role, or organization] asserts that:

  • 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

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

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

Expected Results

  • Check #1 and #2 are true.
Location within product

[Title, role, or organization] asserts that:

  • 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.
Multi-step navigation

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

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

Expected Results

  • #2 is true

HTML multi-step listing

Procedure

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

Expected Results

  • #2 and #3 are true
Location in multi-step process

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

Tests

This section is non-normative.

ARIA current

Procedure

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

Expected Results

  • Check #2 and #3 are true

Current step visually identifiable

Procedure

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

Expected Results

  • Check #2 and #3 are true
Context in multi-step process

Contextual information is provided visually and programmatically to help the user orient within the multi-step process.

Tests

This section is non-normative.

ARIA current

Procedure

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

Expected Results

  • #2 and #3 are true

Current step visually identifiable Procedure

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

Expected Results

  • #2 and #3 are true
Change of page/view

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

  1. Activate a link in the product that should open a new page/view.
  2. Verify that the change is conveyed in the view.
  3. 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 product starting point

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

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

Expected Results

  • #3 is true
Starting point position

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.

This was originally labeled as “type: good-practice” but has been updated to “supplemental”, possibly due to a missing parameter.

Structure

Users can understand and navigate through the content using structure.

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

Programmatic relationships

Relationships of meaning between elements are conveyed programmatically.

Tests

This section is non-normative.

HTML hierarchical relationship

Procedure

  1. Determine the contextual hierarchy of the content either visually or through the meaning of the content.
  2. Examine the source code of the HTML document to identify each hierarchical section.
  3. 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

  1. Identify all input fields within the unit of conformance through visual and code inspection.
  2. 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

  1. Identify all lists within the unit of conformance through visual and code inspection.
  2. Verify that each list consists of a <ul>, <ol> or <dl>.
  3. Verify that each list item within the list is contained within an <li> element (for <ul> and <ol>) or <dt>/<dd> pair (for <dl>).
  4. 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

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

Expected Results

  • #2 is true
Clear blocks of content

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

Tests

This section is non-normative.

HTML sufficient space

Procedure

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

Expected Results

  • #3 is true

Programmatically identifiable meaningful blocks of content

Procedure

  1. Identify meaningful blocks of content in the page/view.
  2. Examine the source code to validate that an appropriate role is being used for the meaningful blocks of content.
  3. 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

  1. Review content and identify meaningful blocks of content.
  2. Examine the source code to validate that an appropriate role is being used for the meaningful blocks of content.
  3. 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
Section labels

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

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

Expected Results

  • #2 is true

Label exists

Procedure

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

Expected Results

  • #2 is true

HTML heading semantics

Procedure

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

Expected Results

  • #2 is true
Heading structure

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

  1. Review the hierarchy of headings.
  2. Headings for sibling content blocks have the same heading level.
  3. 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

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

Expected Results

  • #2 is true
Ordered content

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

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

Expected Results

  • #2 is true

HTML ordered lists

Procedure

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

Expected Results

  • #2 is true
Clear blocks of content (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

  1. Identify meaningful blocks of content in the page/view.
  2. 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 process

[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 foundational 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.
Find key information

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

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.

Dismissible overlaying content

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

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

Expected Results

  • #3 is true
Controllable infinite scrolling

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.

Infinite scrolling on/off control

Procedure

  1. Identify instances of infinite scrolling.
  2. Open the dialog.
  3. 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 relative 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

  1. For each variation of the product in scope, identify common structural components across multiple pages/views.
  2. For each variation of the product in scope, verify that components are presented in the same order within each page/view.

Expected Results

  • #2 is true
Consistent navigation relative 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

  1. Identify repeated blocks of navigation across multiple pages/views of the product or process.
  2. 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

  • #2 is true
Consistent navigation terminology

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

  1. Identify repeated blocks of navigation across multiple pages/views of the product or process.
  2. 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

  • #2 is true

Process and task completion

Avoid exclusionary cognitive tasks

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

Allow automated entry

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

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

Expected results

  • #3 is true
Alternatives to cognitive tests

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

Tests

This section is non-normative.

Procedure

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

Adequate time

Users have enough time to read and use content.

Adjust timeout

A mechanism exists to extend the time limit at timeout, or to disable the timeout at any point.

Applies when time limits exist.

Except when the time limit is essential.

Tests

This section is non-normative.

Extend or disable at timeout

Procedure

  1. Identify the presence of a time limit.
  2. Wait for the timeout.
  3. Verify that the timeout includes a notification with options to extend or disable the timeout.

Expected results

  • #3 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, and
  • 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.

Avoid deception

Users do not encounter deception when completing tasks.

No hidden preselections

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

  1. Identify all options that affect finance, privacy and safety.
  2. For all identified in Step 1, verify that these are visible when completing a process.
  3. 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 pressure

The completion of a process does not include artificial 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 an artificial time limit.

Tests

This section is non-normative.

Procedure

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

Expected results

  • #2 is true
Clear messaging usability testing

[Title, role, or organization] We assert 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; and we removed any deceptive practices found.

Information that needs to be included publicly:

  • Title, role or organization making the assertion
  • Date of assertion
  • Number of participants
  • The deceptive practices evaluated

Recommended internal documentation (Informative):

  • Maintain records of usability testing protocol, and results
  • Disabilities represented within the group of participants
Clear messaging expert review

[Title, role, or organization] We assert that we conducted an expert review to evaluate content for misleading wording, artificial pressure, misdirection, and other deceptive practices; and we removed any deceptive practices found.

Information that needs to be included publicly:

  • Title, role or organization making the assertion
  • Date of assertion
  • The deceptive practices evaluated

Recommended internal documentation (Informative):

  • Maintain records of deceptive practices found, and resolutions

Retain information

Users do not have to reenter information or redo work.

Go back in process

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

  1. Identify any multi-step processes.
  2. Verify that the user is prompted to review and confirm data.
  3. Verify that the user is allowed to return to previous steps to review and change the data.
  4. 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.
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

  1. Identify any processes that require the user to enter information.
  2. Check whether the information has already been requested ion a previous step of the process.
  3. 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.
Save progress

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), and no alternative to the time limit is possible.
Tests

This section is non-normative.

Procedure

  1. Identify any processes that require the user to enter information.
  2. Log in, if needed, and begin the timed activity.
  3. Allow the session to time out.
  4. Submit or save the data.
  5. Log out if logged in.
  6. Re-authenticate and log back in.
  7. 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.
  8. 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.

Action required

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: checking a box to agree to terms and conditions before creating an account or completing a transaction.

Tests

This section is non-normative.

Procedure

  1. Identify any parts of the process that cannot be completed without the user doing a required action.
  2. Enter in all the information except for the required action(s).
  3. Try to complete the process.
  4. 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.
Inform at start of process

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 when the user needs to complete a multi-step process.

Tests

This section is non-normative.

Procedure

At the start of each process:

  1. Identify any multi-step processes.
  2. 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.
  3. Verify that the details of any information and resources that are needed to perform the task are provided at the start of the process.
  4. 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.
Multi-step instructions

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

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

Tests

This section is non-normative.

Procedure

For each multi-step process:

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

Expected results

  • #2 is true.

Policy and protection

Content source

Users can determine when content is provided by a Third Party

Citation

Needs additional research

The author or source of the primary content is visually and programmatically indicated.

Indicate third-party content

Needs additional research

Third-party content (AI, Advertising, etc.) is visually and programmatically indicated.

Risk

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

Comparable risk

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

  1. Identify information that is personal or sensitive.
  2. Verify that personal or sensitive information is visually hidden by default.
  3. Verify that the personal or sensitive information is programmatically hidden by default.
  4. Verify that the use of AT, accessibility settings and accessibility-related modifications does not expose any personal or sensitive information.
  5. Check whether any accessible alternative versions or modifications of the digital content exist.
  6. 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.
Consequential choices

Legal, financial, privacy, or security choices clearly state the benefits, risks, and potential consequences before confirming the choice.

Tests

This section is non-normative.

Procedure

  1. Identify any choices being made by the user.
  2. Identify any potential legal, financial, privacy and security consequences to the user as a result of the choice.
  3. Verify that the consequences are provided before or when the user is making the choice.

Expected results

  • #3 is true.
Consequences provided

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

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

Expected results

  • #3 is true.
Safety and security

[Title, role, or organization] asserts the following:

  • 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 band intent.
  • Ongoing research is being conducted on risks to safety, wellbeing, and mental health for users with diverse disabilities and, when risks are found, all reasonable practical steps are 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
Inclusive algorithm

[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

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

No harm from algorithms

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

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:

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

Expected results

  • #1 and #2 are true.
Contextual help

Context-sensitive help is available.

Tests

This section is non-normative.

Procedure

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

Expected results

  • #3 is true.
Conversational support

Conversational support allowing both text and speech formats is available.

Tests

This section is non-normative.

Procedure

  1. Check that a conversational support mechanism is available.

Expected Results

  • #1 is true
Disabled interactive elements

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

  1. Identify visible disabled controls.
  2. For all visible disabled controls, check that instructions are available that explain how to enable them.

Expected results

  • #2 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

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

Instructions and help do not rely on sensory characteristics alone.

Tests

This section is non-normative.

Procedure

  1. Find all references in the web page that mention the shape, size, or position of an object. For each such item:
  2. 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

A review was conducted 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, and
  • 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.
Usability testing of help

Help and training was added based on usability testing with people with cognitive and mental health disabilities to identify gaps. Solutions include help with completing functionality such as data entry, task completion and search and understanding complex ideas and visualizations.

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

A mechanism is available to provide feedback to authors.

User control

Control text

Users can control text presentation.

Adjust color

Text and background colors can be customized.

Adjust background

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

Font size meaning

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

Text customization

Users can change the text style (like font and size) and the layout (such as spacing and single column) to fit their needs.

Adjustable viewport

Users can transform size and orientation of content presentation to make it viewable and usable.

Orientation

Content orientation allows the user to read the language presented without changing head or body position.

Text reflow

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

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

Expected Results

  • #3 and #4 are true

Transform content

Users can transform content to make it understandable.

Alternative presentation

Needs additional research

Complex information or instructions for complex processes are available in multiple presentation formats.

Content markup

Role and priority of content is programmatically determinable.

Summary

Access to a plain-language summary, abstract, or executive summaries is available.

Transform content

Needs additional research

Content can be transformed to make its purpose clearer.

Media control

Users can control media and media alternative.

Adjust captions

The position and formatting of captions can be changed.

Audio control

Audio can be turned off, while still playing the video, and without affecting the system sound.

Interactive audio alternative

Needs additional research

Alternatives for audio include the ability to search and look up terms.

Media alternative control

Captions and audio descriptions can be turned on and off.

Media chapters

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.
Searchable media alternative

Alternatives for media can be searched and queried.

Control interruptions

Users can control interruptions.

Control notifications

The timing and positioning of notifications and other interruptions can be changed, suppressed or saved, except interruptions involving an emergency.

Control possible harm

Users can control potential sources of harm.

Disturbing content

Needs additional research

Warnings are available about content that may be emotionally disturbing, and the disturbing content can be hidden.

Haptic stimulation

Haptic feedback can be reduced or turned off.

Triggers

Needs additional research

Warnings are available about triggering content, and the warnings and triggering content can be hidden.

Verbosity

Needs additional research

Overwhelming wordiness can be reduced or turned off.

Visual stimulation

Needs additional research

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

User agent support

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

Assistive technology control

Content can be controlled using assistive and adaptive technology.

Printing

Needs additional research

Printing respects user’s content presentation preferences.

User settings

Content does not interfere with a user’s 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:

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

Expected Results

  • #2 is true
Virtual cursor

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

Conformance

Summary

You might want to make a claim that your content or product meets the WCAG 3 guidelines. If it does meet the guidelines, we call this "conformance".

If you want to make a formal conformance claim, you must use the process described in this document. Conformance claims are not required and your content can conform to WCAG 3, even if you don't want to make a claim.

There are two types of content in this document:

We are experimenting with different conformance approaches for WCAG 3. Once we have developed enough guidelines, we will test how well each works.

WCAG 3 will use a different conformance model than WCAG 2 in order to meet its requirements. Developing and vetting the conformance model is a large portion of the work AG needs to complete over the next few years.

AG is exploring a model based on Foundational Requirements, Supplemental Requirements, and Assertions.

The most basic level of conformance will require meeting all of the Foundational Requirements. This set will be somewhat comparable to WCAG 2.2 Level AA.

Higher levels of conformance will be defined and met using Supplemental Requirements and Assertions. AG will be exploring whether meeting the higher levels would work best based on points, percentages, or predefined sets of requirements (modules).

Other conformance concepts AG continues to explore the following include conformance levels, issue severity, adjectival ratings and pre-assessment checks.

See Explainer for W3C Accessibility Guidelines (WCAG) 3.0 for more information.

Only accessibility-supported ways of using technologies

The concept of "accessibility-supported" is to account for the variety of user agents and scenarios. How does an author know that a particular technique for meeting a guideline will work in practice with user agents that are used by real people?

The intent is for the responsibility of testing with user agents to vary depending on the level of conformance.

At the foundational level of conformance, assumptions can be made by authors that methods and techniques provided by WCAG 3 work. At higher levels of conformance the author may need to test that a technique works, or check that available user agents meet the requirement, or a combination of both.

This approach means the Working Group will ensure that methods and techniques included do have reasonably wide and international support from user agents, and there are sufficient techniques to meet each requirement.

The intent is that WCAG 3 will use a content management system to support tagging of methods/techniques with support information. There should also be a process where interested parties can provide information.

An "accessibility support set" is used at higher levels of conformance to define which user agents and assistive technologies you test with. It would be included in a conformance claim, and enables authors to use techniques that are not provided with WCAG 3.

An exception for long-present bugs in assistive technology is still under discussion.

Defining conformance scope

When evaluating the accessibility of content, WCAG 3 requires the guidelines apply to a specific scope. While the scope can be an all content within a digital product, it is usually one or more subsets of the whole. Reasons for this include:

WCAG 3 therefore defines two ways to scope content: views and processes. Evaluation is done on one or more complete views or processes, and conformance is determined on the basis of one or more complete views or processes.

Conformance is defined only for processes and views. However, a conformance claim may be made to cover one process and view, a series of processes and views, or multiple related processes and views. All unique steps in a process MUST be represented in the set of views. Views outside of the process MAY also be included in the scope.

We recognize that representative sampling is an important strategy that large and complex sites use to assess accessibility. While it is not addressed within this document at this time, our intent is to later address it within this document or in a separate document before the guidelines reach the Candidate Recommendation stage. We welcome your suggestions and feedback about the best way to incorporate representative sampling in WCAG 3.

Glossary

Many of the terms defined here have common meanings. When terms appear with a link to the definition, the meaning is as formally defined here. When terms appear without a link to the definition, their meaning is not explicitly related to the formal definition here. These definitions are in progress and may evolve as the document evolves.

This glossary includes terms used by content that has reached a maturity level of Developing or higher. The definitions themselves include a maturity level and may mature at a different pace than the content that refers to them. The AGWG will work with other taskforces and groups to harmonize terminology across documents as much as is possible.

abbreviation

shortened form of a word, phrase, or name where the abbreviation has not become part of the language

This includes initialisms, acronyms, and numeronyms.

  1. initialisms are shortened forms of a name or phrase made from the initial letters of words or syllables contained in that name or phrase. These are not defined in all languages.
  2. acronyms are abbreviated forms made from the initial letters or parts of other words (in a name or phrase) which may be pronounced as a word.
  3. numeronyms are shortened forms of a word that use the first and last letters, with a number in between showing the number of letters left out.

Some companies have adopted what used to be an initialism as their company name. In these cases, the new name of the company is the letters (for example, Ecma) and the word is no longer considered an abbreviation.

accessibility support set

group of user agents and assistive technologies you test with

The AGWG is considering defining a default set of user agents and assistive technologies that they use when validating guidelines.

Accessibility support sets may vary based on language, region, or situation.

If you are not using the default accessibility set, the conformance report should indicate what set is being used.

accessibility supported

supported by in at least 2 major free browsers on every operating system and/or available in assistive technologies used by 80% cumulatively of the AT users on each operating system for each type of AT used

actively available

available for the user to read and use any actionable items included

artificial time limits

To be defined.

assertion

formal claim of fact, attributed to a person or organization, regarding procedures practiced in the development and maintenance of the content or product to improve accessibility

assistive technology

hardware and/or software that acts as a user agent, or along with a mainstream user agent, to provide functionality to meet the requirements of users with disabilities that go beyond those offered by mainstream user agents

Functionality provided by assistive technology includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation mechanisms, and content transformations (e.g., to make tables more accessible).

Assistive technologies often communicate data and messages with mainstream user agents by using and monitoring APIs.

The distinction between mainstream user agents and assistive technologies is not absolute. Many mainstream user agents provide some features to assist individuals with disabilities. The basic difference is that mainstream user agents target broad and diverse audiences that usually include people with and without disabilities. Assistive technologies target narrowly defined populations of users with specific disabilities. The assistance provided by an assistive technology is more specific and appropriate to the needs of its target users. The mainstream user agent may provide important functionality to assistive technologies like retrieving web content from program objects or parsing markup into identifiable bundles.

audio

the technology of sound reproduction

Audio can be created synthetically (including speech synthesis), recorded from real world sounds, or both.

audio description

narration added to the soundtrack to describe important visual details that cannot be understood from the main soundtrack alone

For audiovisual media, audio description provides information about actions, characters, scene changes, on-screen text, and other visual content.

Audio description is also sometimes called “video description”, “described video”, “visual description”, or “descriptive narration”.

In standard audio description, narration is added during existing pauses in dialogue. See also extended audio description.

If all important visual information is already provided in the main audio track, no additional audio description track is necessary.

automated evaluation

evaluation conducted using software tools, typically evaluating code-level features and applying heuristics for other tests

Automated testing is contrasted with other types of testing that involve human judgement or experience. Semi-automated evaluation allows machines to guide humans to areas that need inspection. The emerging field of testing conducted via machine learning is not included in this definition.

blinking

switching back and forth between two visual states in a way that is meant to draw attention

See also flash. It is possible for something to be large enough and blink brightly enough at the right frequency to be also classified as a flash.

blocks of text

more than one sentence of text

camera input

control using a camera as a motion sensor to detect gestures of any type, for example “in the air” gestures

This does not include, for example, a static QR code image on a web page.

captions

synchronized visual and/or text alternative for both the speech and non-speech audio portion of a work of audiovisual content

Closed captions are equivalents that can be turned on and off with some players and can often be read using assistive technology..

Open captions are any captions that cannot be turned off in the player. For example, if the captions are visual equivalent images of text embedded in video.

Audio descriptions can be, but do not need to be, captioned since they are descriptions of information that is already presented visually.

In some countries, captions are called subtitles. The term ‘subtitles’ is often also used to refer to captions that present a translated version of the audio content.

cognitive function test

A task that requires the user to remember, manipulate, or transcribe information. Examples include, but are not limited to:

  • memorization, such as remembering a username, password, set of characters, images, or patterns. The common identifiers name, e-mail, and phone number are not considered cognitive function tests as they are personal to the user and consistent across websites;
  • transcription, such as typing in characters;
  • use of correct spelling;
  • performance of calculations;
  • solving of puzzles.
common keyboard navigation technique

keyboard navigation technique that is the same across most or all applications and platforms and can therefore be relied upon by users who need to navigate by keyboard alone

A sufficient listing of common keyboard navigation techniques for use by authors can be found in the WCAG common keyboard navigation techniques list

complex numerical information

numbers, statistics, or quantitative data that require extra cognitive effort to understand, interpret, or compare. This includes mental calculation, proportional reasoning, or comparison against an unstated whole.

complex pointer input

any pointer input other than a single pointer input

component

grouping of elements for a distinct function

conformance

satisfying all the requirements of the guidelines. Conformance is an important part of following the guidelines even when not making a formal Conformance Claim

See the Conformance section for more information.

content

information and sensory experience to be communicated to the user by an interface, including code or markup that defines the content’s structure, presentation, and interactions

content author

To be defined.

context-sensitive help

help text that provides information related to the function currently being performed

contrast ratio test

To be defined.

conversational support

To be defined.

decorative

serving only an aesthetic purpose, providing no information, and having no functionality

Text is only purely decorative if the words can be rearranged or substituted without changing their purpose.

deprecate

declare something outdated and in the process of being phased out, usually in favor of a specified replacement

Deprecated documents are no longer recommended for use and may cease to exist in the future.

descriptive transcript

a text version of the speech and non-speech audio information and visual information needed to understand the content.

diacritic

placeholder

down event

platform event that occurs when the trigger stimulus of a pointer is depressed

The down event may have different names on different platforms, such as “touchstart” or “mousedown”.

essential exception

exception because there is no way to carry out the function without doing it this way or fundamentally changing the functionality

evaluation

process of examining content for conformance to these guidelines

Different approaches to evaluation include automated evaluation, semi-automated evaluation, human evaluation, and usability testing.

extended audio description

audio description that is added to audiovisual media by pausing the video to allow for additional time to add audio description

This technique is only used when the sense of the video would be lost without the additional audio description and the pauses between dialogue or narration are too short.

figure captions

title, brief explanation, or comment that accompanies a work of visual media and is always visible on the page

flash

a pair of opposing changes in relative luminance that can cause seizures in some people if it is large enough and in the right frequency range

See general flash and red flash thresholds for information about types of flash that are not allowed.

See also blinking.

functional need

statement that describes a specific gap in one’s ability, or a specific mismatch between ability and the designed environment or context

general flash and red flash thresholds

a flash or rapidly-changing image sequence is below the threshold (i.e., content passes) if any of the following are true:

  • there are no more than three general flashes and / or no more than three red flashes within any one-second period; or
  • the combined area of flashes occurring concurrently occupies no more than a total of .006 steradians within any 10 degree visual field on the screen (25% of any 10 degree visual field on the screen) at typical viewing distance

where:

  • A general flash is defined as a pair of opposing changes in relative luminance of 10% or more of the maximum relative luminance (1.0) where the relative luminance of the darker image is below 0.80; and where “a pair of opposing changes” is an increase followed by a decrease, or a decrease followed by an increase, and
  • A red flash is defined as any pair of opposing transitions involving a saturated red

Exception: Flashing that is a fine, balanced, pattern such as white noise or an alternating checkerboard pattern with “squares” smaller than 0.1 degree (of visual field at typical viewing distance) on a side does not violate the thresholds.

For general software or web content, using a 341 x 256 pixel rectangle anywhere on the displayed screen area when the content is viewed at 1024 x 768 pixels will provide a good estimate of a 10 degree visual field for standard screen sizes and viewing distances (e.g., 15-17 inch screen at 22-26 inches). This resolution of 75 - 85 ppi is known to be lower, and thus more conservative than the nominal CSS pixel resolution of 96 ppi in CSS specifications. Higher resolutions displays showing the same rendering of the content yield smaller and safer images so it is lower resolutions that are used to define the thresholds.

A transition is the change in relative luminance (or relative luminance/color for red flashing) between adjacent peaks and valleys in a plot of relative luminance (or relative luminance/color for red flashing) measurement against time. A flash consists of two opposing transitions.

The new working definition in the field for “pair of opposing transitions involving a saturated red” (from WCAG 2.2) is a pair of opposing transitions where, one transition is either to or from a state with a value R/(R + G + B) that is greater than or equal to 0.8, and the difference between states is more than 0.2 (unitless) in the CIE 1976 UCS chromaticity diagram. [[ISO_9241-391]]

Tools are available that will carry out analysis from video screen capture. However, no tool is necessary to evaluate for this condition if flashing is less than or equal to 3 flashes in any one second. Content automatically passes (see #1 and #2 above).

gesture

motion made by the body or a body part used to communicate to technology

guideline

high-level, plain-language outcome statements used to organize requirements

Guidelines provide a high-level, plain-language outcome statements for managers, policy makers, individuals who are new to accessibility, and other individuals who need to understand the concepts but not dive into the technical details. They provide an easy-to-understand way of organizing and presenting the requirements so that non-experts can learn about and understand the concepts.

Each guideline includes a unique, descriptive name along with a high-level plain-language summary. Guidelines address functional needs on specific topics, such as contrast, forms, readability, and more.

Guidelines group related requirements and are technology-independent.

high-frequency corpus

large collections of text (corpora) used in linguistics to identify and analyze words and phrases that appear most often in a language

human evaluation

evaluation conducted by a human, typically to apply human judgement to tests that cannot be fully automatically evaluated

Human evaluation is contrasted with automated evaluation which is done entirely by machine, though it includes semi-automated evaluation which allows machines to guide humans to areas that need inspection. Human evaluation involves inspection of content features, in contrast with usability testing which directly tests the experience of users with content.

image

To be defined.

image role

To be defined.

image type

To be defined.

informative

content provided for information purposes and not required for conformance. Also referred to as non-normative

interactive element

element that responds to user input and has a distinct programmatically determinable name

In contrast to non-interactive elements. For example, headings or paragraphs.

items

smallest testable unit for testing scope

Items could be an interactive component such as a drop down menu, a link, or a media player.

They could also be units of content such as a phrase, a paragraph, a label or error message, an icon, or an image.

keyboard focus

point in the content where any keyboard actions would take effect

keyboard interface

API (Application Programming Interface) where software gets “keystrokes” from

“Keystrokes” that are passed to the software from the “keyboard interface” may come from a wide variety of sources including but not limited to a scanning program, sip-and-puff morse code software, speech recognition software, AI of all sorts, as well as other keyboard substitutes or special keyboards.

long form written content

placeholder

mechanism

process or technique for achieving a result

The mechanism may be explicitly provided in the content, or may be relied upon to be provided by either the platform or by user agents, including assistive technologies.

The mechanism needs to meet all requirements for the conformance level claimed.

media alternatives

alternative formats, usually text, for audio, video, and audio-video content including captions, audio descriptions, and descriptive transcripts

method

detailed information, either technology-specific or technology-agnostic, on ways to meet the requirement as well as tests and scoring information

nested clause

dependent clause that is embedded inside another dependent clause

Dependent clauses are sometimes called subordinate clauses.

non-interactive element

element that does not respond to user input and does not include sub-parts

If a paragraph included a link, the text either side of the link would be considered a static element, but not the paragraph as a whole.

Letters within text do not constitute a “smaller part”.

non-literal language

words or phrases used in a way that are beyond their standard or dictionary meaning to express deeper, more complex ideas

This is also called figurative language.

To understand the content, users have to interpret the implied meaning behind the words, rather than just their literal or direct meaning.

Examples include:

  • allusions
  • hyperbole
  • idioms
  • irony
  • jokes
  • litotes
  • metaphors
  • metonymies
  • onomatopoeia
  • oxymorons
  • personification
  • puns
  • sarcasm
  • similes
normative

content whose instructions are required for conformance

open captions

captions that are visual equivalent images of text that are embedded in video

Open captions are also known as burned-in, baked-on, or hard-coded captions. Open captions cannot be turned off and cannot be read using assistive technology.

page

non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together

Where a URI is available and represents a unique set of content, that would be the preferred conformance unit.

Path-based gesture

gesture that depends on the path of the pointer input and not just its endpoints

Path based gesture includes both time dependent and non-time dependent path-based gestures.

platform

software, or collection of layers of software, that lie below the subject software and provide services to the subject software and that allows the subject software to be isolated from the hardware, drivers, and other software below

Platform software both makes it easier for subject software to run on different hardware, and provides the subject software with many services (e.g. functions, utilities, libraries) that make the subject software easier to write, keep updated, and work more uniformly with other subject software.

A particular software component might play the role of a platform in some situations and a client in others. For example a browser is a platform for the content of the page but it also relies on the operating system below it.

The platform is the context in which the product exists.

point of regard

position in rendered content that the user is presumed to be viewing. The dimensions of the point of regard can vary

The point of regard is almost always within the viewport, but it can exceed the spatial or temporal dimensions of the viewport. See rendered content for more information about viewport dimensions.

The point of regard can also refer to a particular moment in time for content that changes over time. For example, an audio-only presentation.

User agents can determine the point of regard in a number of ways, including based on viewport position in content, keyboard focus, and selection.

pointer

To be defined.

private and sensitive information

private and sensitive information

process

series of views or pages associated with user actions, where actions required to complete an activity are performed, often in a certain order, regardless of the technologies used or whether it spans different sites or domains

product

testing scope that is a combination of all items, views, and task flows that make up the web site, set of web pages, web app, etc.

The context for the product would be the platform.

programmatically determinable

meaning of the content and all its important attributes can be determined by software functionality that is accessibility supported

pseudo motion

static content on the page that gives the user the perception or feeling of motion

relative luminance

the relative brightness of any point in a colorspace, normalized to 0 for darkest black and 1 for lightest white

For the sRGB colorspace, the relative luminance of a color is defined as L = 0.2126 * R + 0.7152 * G + 0.0722 * B where R, G and B are defined as:

  • if RsRGB <= 0.04045 then R = RsRGB/12.92 else R = ((RsRGB+0.055)/1.055) ^ 2.4
  • if GsRGB <= 0.04045 then G = GsRGB/12.92 else G = ((GsRGB+0.055)/1.055) ^ 2.4
  • if BsRGB <= 0.04045 then B = BsRGB/12.92 else B = ((BsRGB+0.055)/1.055) ^ 2.4

and RsRGB, GsRGB, and BsRGB are defined as:

  • RsRGB = R8bit/255
  • GsRGB = G8bit/255
  • BsRGB = B8bit/255

The ”^” character is the exponentiation operator. (Formula taken from [[SRGB]].)

Before May 2021 the value of 0.04045 in the definition was different (0.03928). It was taken from an older version of the specification and has been updated. It has no practical effect on the calculations in the context of these guidelines.

Almost all systems used today to view web content assume sRGB encoding. Unless it is known that another color space will be used to process and display the content, authors should evaluate using sRGB colorspace.

If dithering occurs after delivery, then the source color value is used. For colors that are dithered at the source, the average values of the colors that are dithered should be used (average R, average G, and average B).

Tools are available that automatically do the calculations when testing contrast and flash.

WCAG 2.2 includes a separate page giving the relative luminance definition using MathML to display the formulas. This will need to be addressed for inclusion in WCAG 3.

requirement

result of practices that reduce or eliminate barriers that people with disabilities experience

section

self-contained portion of content that deals with one or more related topics or thoughts

A section may consist of one or more paragraphs and include graphics, tables, lists and sub-sections.

Semi-automated evaluation

evaluation conducted using machines to guide humans to areas that need inspection

Semi-automated evaluation involves components of automated evaluation and human evaluation.

simple pointer input

input event that involves only a single ‘click’ event or a ‘button down’ and ‘button up’ pair of events with no movement between

Examples of things that are not simple pointer actions include double clicks, dragging motions, gestures, and any use of multipoint input or gestures, and the simultaneous use of a mouse and keyboard.

single pointer

input modality that only targets a single point on the page/screen at a time – such as a mouse, single finger on a touch screen, or stylus

Single pointer interactions include clicks, double clicks, taps, dragging motions, and single-finger swipe gestures. In contrast, multipoint interactions involve the use of two or more pointers at the same time, such as two-finger interactions on a touchscreen, or the simultaneous use of a mouse and stylus.

single pointer input

input modality that only targets a single point on the view at a time – such as a mouse, single finger on a touch screen, or stylus

Single pointer interactions include clicks, double clicks, taps, dragging motions, and single-finger swipe gestures. In contrast, multipoint interactions involve the use of two or more pointers at the same time, such as two-finger interactions on a touchscreen, or the simultaneous use of a mouse and stylus.

Single pointer input is in contrast to multipoint input such as two, three or more fingers or pointers touching the surface, or gesturing in the air, at the same time.

Activation is usually by click or tap but can also be by programmatic simulation of a click or tap or other similar simple activation.

standard platform keyboard commands

keyboard commands that are the same across most or platforms and are relied upon by users who need to navigate by keyboard alone

A sufficient listing of common keyboard navigation techniques for use by authors can be found in the WCAG standard keyboard navigation techniques list.

support

To be defined.

task flow

testing scope that includes a series views that support a specified user activity

A task flow may include a subset of items in a view or a group of views. Only the part of the views that support the user activity are included in a test of the task flow.

test

mechanism to evaluate implementation of a method

text

sequence of characters that can be programmatically determined, where the sequence is expressing something in human language

text alternative

text that is programmatically associated with non-text content or referred to from text that is programmatically associated with non-text content

up event

platform event that occurs when the trigger stimulus of a pointer is released

The up event may have different names on different platforms, such as “touchend” or “mouseup”.

usability testing

evaluation of the experience of users using a product or process by observation and feedback

user agent

software that retrieves and presents external content for users

user need

end goal a user has when starting a process through digital means

User-manipulable text

text which the user can adjust

This could include, but is not limited to, changing:

  • Line, word or letter spacing
  • Color
  • Line length — being able to control width of block of text
  • Typographic alignment — justified, flushed right/left, centered
  • Wrapping
  • Columns — number of columns in one-dimensional content
  • Margins
  • Underlining, italics, bold
  • Font face, size, width
  • Capitalization — all caps, small caps, alternating case
  • End of line hyphenation
  • Links
video

the technology of moving or sequenced pictures or images

Video can be made up of animated or photographic images, or both.

view

content that is actively available in a viewport including that which can be scrolled or panned to, and any additional content that is included by expansion while leaving the rest of the content in the viewport actively available

A modal dialog box would constitute a new view because the other content in the viewport is no longer actively available.

viewport

object in which the platform presents content

The author has no control of the viewport and almost always has no idea what is presented in a viewport (e.g. what is on screen) because it is provided by the platform. On browsers the hardware platform is isolated from the content.

Content can be presented through one or more viewports. Viewports include windows, frames, loudspeakers, and virtual magnifying glasses. A viewport may contain another viewport. For example, nested frames. Interface components created by the user agent such as prompts, menus, and alerts are not viewports.

visual aids

diagrams, pictures, or a simplified step process to assist users in understanding complex ideas, such as processes, workflows, relationships, or chronological information.

Privacy Considerations

The content of this document has not matured enough to identify privacy considerations. Reviewers of this draft should consider whether requirements of the conformance model could impact privacy.

Security Considerations

The content of this document has not matured enough to identify security considerations. Reviewers of this draft should consider whether requirements of the conformance model could impact security.

Change log

This section shows substantive changes made in WCAG 3 since the First Public Working Draft was published in 21 January 2021.

The full commit history to WCAG 3 and commit history to Silver is available.

Acknowledgements

Additional information about participation in the Accessibility Guidelines Working Group (AG WG) can be found on the Working Group home page.

Contributors to the development of this document

Previous contributors to the development of this document

Abi James, Abi Roper, Alastair Campbell, Alice Boxhall, Alina Vayntrub, Alistair Garrison, Amani Ali, Andrew Kirkpatrick, Andrew Somers, Andy Heath, Angela Hooker, Aparna Pasi, Ashley Firth, Avneesh Singh, Avon Kuo, Azlan Cuttilan, Ben Tillyer, Betsy Furler, Brooks Newton, Bruce Bailey, Bryan Trogdon, Caryn Pagel, Charles Hall, Charles Nevile, Chris Loiselle, Chris McMeeking, Christian Perera, Christy Owens, Chuck Adams, Cybele Sack, Daniel Bjorge, Daniel Henderson-Ede, Darryl Lehmann, David Fazio, David MacDonald, David Sloan, David Swallow, Dean Hamack, Detlev Fischer, DJ Chase, E.A. Draffan, Eleanor Loiacono, Filippo Zorzi, Francis Storr, Frankie Wolf, Frederick Boland, Garenne Bigby, Gez Lemon, Giacomo Petri, Glenda Sims, Graham Ritchie, Greg Lowney, Gregg Vanderheiden, Gundula Niemann, Hidde de Vries, Imelda Llanos, Jaeil Song, JaEun Jemma Ku, Jake Abma, Jan Jaap de Groot, Jan McSorley, Janina Sajka, Jaunita George, Jeanne Spellman, Jedi Lin, Jeff Kline, Jennifer Chadwick, Jennifer Delisi, Jennifer Strickland, Jennison Asuncion, Jill Power, Jim Allan, Joe Cronin, John Foliot, John Kirkwood, John McNabb, John Northup, John Rochford, John Toles, Jon Avila, Joshue O’Connor, Judy Brewer, Julie Rawe, Justine Pascalides, Karen Schriver, Katharina Herzog, Kathleen Wahlbin, Katie Haritos-Shea, Katy Brickley, Kelsey Collister, Kim Dirks, Kimberly McGee, Kimberly Patch, Laura Carlson, Laura Miller, Len Beasley, Léonie Watson, Lisa Seeman-Kestenbaum, Lori Oakley, Lori Samuels, Lucy Greco, Luis Garcia, Lyn Muldrow, Makoto Ueki, Marc Johlic, Marie Bergeron, Mark Tanner, Mary Ann Jawili, Mary Jo Mueller, Matt Garrish, Matthew King, Melanie Philipp, Melina Maria Möhnle, Michael Cooper, Michael Crabb, Michael Elledge, Michael Weiss, Michellanne Li, Michelle Lana, Mike Beganyi, Mike Crabb, Mike Gower, Nicaise Dogbo, Nicholas Trefonides, Nina Krauß, Omar Bonilla, Patrick H. Lauke, Paul Adam, Peter Korn, Peter McNally, Pietro Cirrincione, Poornima Badhan Subramanian, Rachael Bradley Montgomery, Rain Breaw Michaels, Ralph de Rooij, Rashmi Katakwar, Rebecca Monteleone, Rick Boardman, Roberto Scano, Ruoxi Ran, Ruth Spina, Ryan Hemphill, Sarah Horton, Sarah Pulis, Scott Hollier, Scott O’Hara, Shadi Abou-Zahra, Shannon Urban, Shari Butler, Shawn Henry, Shawn Lauriat, Shawn Thompson, Sheri Byrne-Haber, Shrirang Sahasrabudhe, Shwetank Dixit, Stacey Lumley, Stein Erik Skotkjerra, Stephen Repsher, Steve Faulkner, Steve Lee, Sukriti Chadha, Susi Pallero, Suzanne Taylor, sweta wakodkar, Takayuki Watanabe, Tananda Darling, Theo Hale, Thomas Logan, Thomas Westin, Tiffany Burtin, Tim Boland, Todd Libby, Todd Marquis Boutin, Victoria Clark, Wayne Dick, Wendy Chisholm, Wendy Reid, Wilco Fiers.

Research Partners

These researchers selected a Silver research question, did the research, and graciously allowed us to use the results.

Enabling funders

This publication has been funded in part with U.S. Federal funds from the Health and Human Services, National Institute on Disability, Independent Living, and Rehabilitation Research (NIDILRR), initially under contract number ED-OSE-10-C-0067, then under contract number HHSP23301500054C, and now under HHS75P00120P00168. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Health and Human Services or the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.