Web Content Accessibility Guidelines (WCAG) 2.2 2.1

W3C Editor's Draft Recommendation

More details about this document
This version:
https://w3c.github.io/wcag/guidelines/22/ https://www.w3.org/TR/2024/REC-WCAG21-20240311/
Latest published version:
https://www.w3.org/TR/WCAG22/ https://www.w3.org/TR/WCAG21/
Latest editor's draft:
https://w3c.github.io/wcag/guidelines/22/
Latest History:
https://www.w3.org/standards/history/WCAG21/
Commit history
Implementation report:
https://www.w3.org/WAI/WCAG21/implementation-report/
Previous Recommendation:
https://www.w3.org/TR/WCAG/ https://www.w3.org/TR/WCAG20/
Editors: Chuck Adams
(Oracle) ( Adobe )
( Invited Expert, InterAccess )
(Nomensa) Rachael Montgomery (Invited Expert) ( Nomensa )
(W3C) ( W3C )
Feedback:
GitHub w3c/wcag ( pull requests , new issue , open issues )
Andrew Kirkpatrick public-agwg-comments@w3.org (Adobe) with subject line [WCAG21] … message topic … ( archives )
Errata:
Errata exists .

See also translations .

Copyright © 2020-2024 World Wide Web Consortium . W3C ® ( MIT , ERCIM , Keio , Beihang ). W3C liability , trademark and document use rules apply.

Abstract

Web Content Accessibility Guidelines (WCAG) 2.2 2.1 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general.

WCAG 2.2 2.1 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction and links to WCAG technical and educational material.

WCAG 2.2 2.1 extends Web Content Accessibility Guidelines 2.1 2.0 [ WCAG21 WCAG20 ], which was published as a W3C Recommendation June 2018. December 2008. Content that conforms to WCAG 2.2 2.1 also conforms to WCAG 2.0 and WCAG 2.1. 2.0. The WG intends that for policies requiring conformance to WCAG 2.0 or WCAG 2.1, 2.0, WCAG 2.2 2.1 can provide an alternate means of conformance. The publication of WCAG 2.2 2.1 does not deprecate or supersede WCAG 2.0 or WCAG 2.1. 2.0. While WCAG 2.0 and WCAG 2.1 remain remains a W3C Recommendations, Recommendation, the W3C advises the use of WCAG 2.2 2.1 to maximize future applicability of accessibility efforts. The W3C also encourages use of the most current version of WCAG when developing or updating Web accessibility policies.

Status of This Document

This is a preview

Do not attempt to implement this version of the specification. Do not reference this version as authoritative in any way. Instead, see https://w3c.github.io/wcag/guidelines/22/ for the Editor's draft.

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.

This is an Editors' Draft a Recommendation of Web Content Accessibility Guidelines (WCAG) 2.2. WCAG 2.1 is a W3C by the Accessibility Guidelines Working Group . This incorporates errata and are described in the change log . At some point additional changes might be incorporated into an Edited or Amended Recommendation .

To comment, file an issue in the W3C WCAG GitHub repository . Although the proposed Success Criteria in this document reference issues tracking discussion, the Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to public-agwg-comments@w3.org ( comment archive ).

This document was published by the Accessibility Guidelines Working Group as an Editor's Draft. a Recommendation using the Recommendation track .

Comments regarding W3C recommends the wide deployment of this document are welcome. Please send them to public-agwg-comments@w3.org ( archives ). Publication specification as an Editor's Draft does not imply endorsement by a standard for the Web.

A W3C Membership. This Recommendation is a draft document and may be updated, replaced or obsoleted by other documents at any time. It specification that, after extensive consensus-building, is inappropriate endorsed by W3C and its Members, and has commitments from Working Group members to cite this document as other than work in progress. royalty-free licensing for implementations.

This document was produced by a group operating under the W3C Patent Policy . W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy .

This document is governed by the 1 March 2019 03 November 2023 W3C Process Document .

Introduction

This section is non-normative.

1.

Background on WCAG 2

Web Content Accessibility Guidelines (WCAG) 2.2 2.1 defines how to make Web content more accessible to people with disabilities. Accessibility involves a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. Although these guidelines cover a wide range of issues, they are not able to address the needs of people with all types, degrees, and combinations of disability. These guidelines also make Web content more usable by older individuals with changing abilities due to aging and often improve usability for users in general.

WCAG 2.2 2.1 is developed through the W3C process in cooperation with individuals and organizations around the world, with a goal of providing a shared standard for Web content accessibility that meets the needs of individuals, organizations, and governments internationally. WCAG 2.2 2.1 builds on WCAG 2.0 [ WCAG20 ] and WCAG 2.1 [ WCAG21 ], which in turn built on WCAG 1.0 [ WAI-WEBCONTENT ] and is designed to apply broadly to different Web technologies now and in the future, and to be testable with a combination of automated testing and human evaluation. For an introduction to WCAG, see the Web Content Accessibility Guidelines (WCAG) Overview .

Significant challenges were encountered in defining additional criteria to address cognitive, language, and learning disabilities, including a short timeline for development as well as challenges in reaching consensus on testability, implementability, and international considerations of proposals. Work will carry on in this area in future versions of WCAG. We encourage authors to refer to our supplemental guidance on improving inclusion for people with disabilities, including learning and cognitive disabilities, people with low-vision, and more .

Web accessibility depends not only on accessible content but also on accessible Web browsers and other user agents. Authoring tools also have an important role in Web accessibility. For an overview of how these components of Web development and interaction work together, see:

Where this document refers to WCAG 2 it is intended to mean any and all versions of WCAG that start with 2.

2.

WCAG 2 Layers of Guidance

The individuals and organizations that use WCAG vary widely and include Web designers and developers, policy makers, purchasing agents, teachers, and students. In order to meet the varying needs of this audience, several layers of guidance are provided including overall principles , general guidelines , testable success criteria and a rich collection of sufficient techniques , advisory techniques , and documented common failures with examples, resource links and code.

All of these layers of guidance (principles, guidelines, success criteria, and sufficient and advisory techniques) work together to provide guidance on how to make content more accessible. Authors are encouraged to view and apply all layers that they are able to, including the advisory techniques, in order to best address the needs of the widest possible range of users.

Note that even content that conforms at the highest level (AAA) will not be accessible to individuals with all types, degrees, or combinations of disability, particularly in the cognitive, language, cognitive language and learning areas. Authors are encouraged to consider the full range of techniques, including the advisory techniques, as well as to seek relevant advice about current best practice to ensure that Web content is accessible, as far as possible, to this community. Metadata may assist users in finding content most suitable for their needs.

3.

WCAG 2.2 2.1 Supporting Documents

The WCAG 2.2 2.1 document is designed to meet the needs of those who need a stable, referenceable technical standard. Other documents, called supporting documents, are based on the WCAG 2.2 2.1 document and address other important purposes, including the ability to be updated to describe how WCAG would be applied with new technologies. Supporting documents include:

  1. How to Meet WCAG 2.2 2.1 - A customizable quick reference to WCAG 2.2 2.1 that includes all of the guidelines, success criteria, and techniques for authors to use as they are developing and evaluating Web content. This includes content from WCAG 2.0, 2.0 and WCAG 2.1 2.2 and can be filtered in many ways to help authors focus on relevant content.

  2. Understanding WCAG 2.2 2.1 - A guide to understanding and implementing WCAG 2.2. 2.1. There is a short "Understanding" document for each guideline and success criterion in WCAG 2.2 2.1 as well as key topics.

  3. Techniques for WCAG 2.2 2.1 - A collection of techniques and common failures, each in a separate document that includes a description, examples, code and tests.

  4. The WCAG Documents - A diagram and description of how the technical documents are related and linked.

See Web Content Accessibility Guidelines (WCAG) Overview for a description of the WCAG 2.2 2.1 supporting material, including education resources related to WCAG 2. Additional resources covering topics such as the business case for Web accessibility, planning implementation to improve the accessibility of Web sites, and accessibility policies are listed in WAI Resources .

4.

Requirements for WCAG 2.2 2.1

WCAG 2.2 2.1 meets a set of requirements for WCAG 2.2 2.1 which, in turn, inherit requirements from previous WCAG 2 versions. 2.0. Requirements structure the overall framework of guidelines and ensure backwards compatibility. The Working Group also used a less formal set of acceptance criteria for success criteria, to help ensure success criteria are similar in style and quality to those in WCAG 2.0. These requirements constrained what could be included in WCAG 2.2. 2.1. This constraint was important to preserve its nature as a dot-release of WCAG 2.

5.

Comparison with WCAG 2.1 2.0

WCAG 2.2 2.1 was initiated with the goal to continue the work of WCAG 2.1: Improving improve accessibility guidance for three major groups: users with cognitive or learning disabilities, users with low vision, and users with disabilities on mobile devices. Many ways to meet these needs were proposed and evaluated, and a set of these were refined by the Working Group. Structural requirements inherited from WCAG 2.0, clarity and impact of proposals, and timeline led to the final set of success criteria included in this version. The Working Group considers that WCAG 2.2 2.1 incrementally advances web content accessibility guidance for all these areas, but underscores that not all user needs are met by these guidelines.

WCAG 2.2 2.1 builds on and is backwards compatible with WCAG 2.1, 2.0, meaning web pages that conform to WCAG 2.2 also conform to WCAG 2.1, which would 2.1 also conform to WCAG 2.0. Authors that are required by policy to conform with WCAG 2.0 or 2.1 will be able to update content to WCAG 2.2 2.1 without losing conformance with previous versions. WCAG 2.0. Authors following more than one version both sets of the guidelines should be aware of the following differences:

5.1

New Features in WCAG 2.2 2.1

WCAG 2.2 2.1 extends WCAG 2.1 2.0 by adding new success criteria, definitions to support them, and guidelines to organize the additions. additions, and a couple additions to the conformance section. This additive approach helps to make it clear that sites which conform to WCAG 2.2 2.1 also conform to WCAG 2.1. 2.0, thereby meeting conformance obligations that are specific to WCAG 2.0. The Accessibility Guidelines Working Group recommends that sites adopt WCAG 2.2 2.1 as their new conformance target, even if formal obligations mention previous versions, WCAG 2.0, to provide improved accessibility and to anticipate future policy changes.

The following Success Criteria are new in WCAG 2.2: 2.1:

The new success criteria may reference new terms that have also been added to the glossary and form part of the normative requirements of the success criteria.

In addition to the above new Success Criteria, Focus Visible Conformance section, a third note about page variants has been promoted from Level AA added to Level A. Full Pages , and an option for machine-readable metadata added to Optional Components of a Conformance Claim .

5.2

Numbering in WCAG 2.2 2.1

In order to avoid confusion for implementers for whom backwards compatibility to WCAG 2 versions 2.0 is important, new success criteria in WCAG 2.2 2.1 have been appended to the end of the set of success criteria within their guideline. This avoids the need to change the section number of success criteria from WCAG 2, 2.0, which would be caused by inserting new success criteria between existing success criteria in the guideline, but it means success criteria in each guideline are no longer grouped by conformance level. The order of success criteria within each guideline does not imply information about conformance level; only the conformance level indicator (A / AA / AAA) on the success criterion itself indicates this. The WCAG 2.2 2.1 Quick Reference will provide a way provides ways to view success criteria grouped by conformance level, along with many other filter and sort options.

5.3

Conformance to WCAG 2.2 2.1

WCAG 2.2 2.1 uses the same conformance model as WCAG 2.0. 2.0 with a couple additions, which is described in the Conformance section. It is intended that sites that conform to WCAG 2.2 2.1 also conform to WCAG 2.0 and WCAG 2.1, 2.0, which means they meet the requirements of any policies that reference WCAG 2.0 or WCAG 2.1, 2.0, while also better meeting the needs of users on the current Web.

6.

Later Versions of Accessibility Guidelines

In parallel with WCAG 2.2, 2.1, the Accessibility Guidelines Working Group is developing another major version of accessibility guidelines. The result of this work is expected to be a more substantial restructuring of web accessibility guidance than would be realistic for dot-releases of WCAG 2. The work follows a research-focused, user-centered design methodology to produce the most effective and flexible outcome, including the roles of content authoring, user agent support, and authoring tool support. This is a multi-year effort, so WCAG 2.2 2.1 is needed as an interim measure to provide updated web accessibility guidance to reflect changes on the web since the publication of WCAG 2.0. The Working Group might also develop additional interim versions, continuing with WCAG 2.2, on a similar short timeline to provide additional support while the major version is completed.

1. Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

Guideline 1.1 Text Alternatives

Understanding Text Alternatives |
How to Meet Text Alternatives

Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


20

/non-text-

content

.html

Guideline 1.2 Time-based Media

Understanding Time-based Media |
How to Meet Time-based Media

Provide alternatives for time-based media.

Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


20

/

audio

-only-and-

video

-only-prerecorded
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/captions-prerecorded.html

/uploads/YR43bC/guidelines/sc/20/captions-prerecorded.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


20

/

audio

-description-or-media-alternative-prerecorded
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/captions-live.html

/uploads/YR43bC/guidelines/sc/20/captions-live.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


20

/

audio

-description-prerecorded
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/sign-language-prerecorded.html

/uploads/YR43bC/guidelines/sc/20/sign-language-prerecorded.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


20

/extended-

audio

-description-prerecorded
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/media-alternative-prerecorded.html

/uploads/YR43bC/guidelines/sc/20/media-alternative-prerecorded.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


20

/

audio

-only-live
.html

Guideline 1.3 Adaptable

Understanding Adaptable |
How to Meet Adaptable

Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/info-and-relationships.html

/uploads/YR43bC/guidelines/sc/20/info-and-relationships.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/meaningful-sequence.html

/uploads/YR43bC/guidelines/sc/20/meaningful-sequence.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/sensory-characteristics.html

/uploads/YR43bC/guidelines/sc/20/sensory-characteristics.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/21/orientation.html

/uploads/YR43bC/guidelines/sc/21/orientation.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


21

/identify-

input

-purpose
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/21/identify-purpose.html

/uploads/YR43bC/guidelines/sc/21/identify-purpose.html

Guideline 1.4 Distinguishable

Understanding Distinguishable |
How to Meet Distinguishable

Make it easier for users to see and hear content including separating foreground from background.

Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


20

/use-of-

color

.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


20

/

audio

-control
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/contrast-minimum.html

/uploads/YR43bC/guidelines/sc/20/contrast-minimum.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


20

/

resize

-text
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/images-of-text.html

/uploads/YR43bC/guidelines/sc/20/images-of-text.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/contrast-enhanced.html

/uploads/YR43bC/guidelines/sc/20/contrast-enhanced.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


20

/low-or-no-

background

-

audio

.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/visual-presentation.html

/uploads/YR43bC/guidelines/sc/20/visual-presentation.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/images-of-text-no-exception.html

/uploads/YR43bC/guidelines/sc/20/images-of-text-no-exception.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/21/reflow.html

/uploads/YR43bC/guidelines/sc/21/reflow.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/21/non-text-contrast.html

/uploads/YR43bC/guidelines/sc/21/non-text-contrast.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/21/text-spacing.html

/uploads/YR43bC/guidelines/sc/21/text-spacing.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


21

/

content

-on-hover-or-focus
.html

2. Operable

User interface components and navigation must be operable.

Guideline 2.1 Keyboard Accessible

Understanding Keyboard Accessible |
How to Meet Keyboard Accessible

Make all functionality available from a keyboard.

Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/keyboard.html

/uploads/YR43bC/guidelines/sc/20/keyboard.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/no-keyboard-trap.html

/uploads/YR43bC/guidelines/sc/20/no-keyboard-trap.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/keyboard-no-exception.html

/uploads/YR43bC/guidelines/sc/20/keyboard-no-exception.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/21/character-key-shortcuts.html

/uploads/YR43bC/guidelines/sc/21/character-key-shortcuts.html

Guideline 2.2 Enough Time

Understanding Enough Time |
How to Meet Enough Time

Provide users enough time to read and use content.

Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/timing-adjustable.html

/uploads/YR43bC/guidelines/sc/20/timing-adjustable.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/pause-stop-hide.html

/uploads/YR43bC/guidelines/sc/20/pause-stop-hide.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/no-timing.html

/uploads/YR43bC/guidelines/sc/20/no-timing.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/interruptions.html

/uploads/YR43bC/guidelines/sc/20/interruptions.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/re-authenticating.html

/uploads/YR43bC/guidelines/sc/20/re-authenticating.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/21/timeouts.html

/uploads/YR43bC/guidelines/sc/21/timeouts.html

Guideline 2.3 Seizures and Physical Reactions

Understanding Seizures and Physical Reactions |
How to Meet Seizures and Physical Reactions

Do not design content in a way that is known to cause seizures or physical reactions.

Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/three-flashes-or-below-threshold.html

/uploads/YR43bC/guidelines/sc/20/three-flashes-or-below-threshold.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/three-flashes.html

/uploads/YR43bC/guidelines/sc/20/three-flashes.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


21

/

animation

-

from

-interactions
.html

Guideline 2.5 Input Modalities

Understanding Input Modalities |
How to Meet Input Modalities

[New]

Make it easier for users to operate functionality through various inputs beyond keyboard.

Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/21/pointer-gestures.html

/uploads/YR43bC/guidelines/sc/21/pointer-gestures.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/21/pointer-cancellation.html

/uploads/YR43bC/guidelines/sc/21/pointer-cancellation.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


21

/

label

-in-name
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/21/motion-actuation.html

/uploads/YR43bC/guidelines/sc/21/motion-actuation.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/21/target-size.html

/uploads/YR43bC/guidelines/sc/21/target-size.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


21

/concurrent-

input

-mechanisms
.html
Error Cannot GET /uploads/3l9AEc/guidelines/sc/22/dragging.html Error Cannot GET /uploads/3l9AEc/guidelines/sc/22/pointer-target-spacing.html

3. Understandable

Information and the operation of the user interface must be understandable.

Guideline 3.1 Readable

Understanding Readable |
How to Meet Readable

Make text content readable and understandable.

Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/language-of-page.html

/uploads/YR43bC/guidelines/sc/20/language-of-page.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/language-of-parts.html

/uploads/YR43bC/guidelines/sc/20/language-of-parts.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/unusual-words.html

/uploads/YR43bC/guidelines/sc/20/unusual-words.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/abbreviations.html

/uploads/YR43bC/guidelines/sc/20/abbreviations.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/reading-level.html

/uploads/YR43bC/guidelines/sc/20/reading-level.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/pronunciation.html

/uploads/YR43bC/guidelines/sc/20/pronunciation.html

Guideline 3.2 Predictable

Understanding Predictable |
How to Meet Predictable

Make Web pages appear and operate in predictable ways.

Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/on-focus.html

/uploads/YR43bC/guidelines/sc/20/on-focus.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/sc/

/uploads/YR43bC/guidelines/sc/


20

/on-

input

.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/consistent-navigation.html
Error
Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/consistent-identification.html
Error
Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/change-on-request.html

/uploads/YR43bC/guidelines/sc/20/consistent-navigation.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/22/findable-help.html

/uploads/YR43bC/guidelines/sc/20/consistent-identification.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/22/hidden-controls.html

/uploads/YR43bC/guidelines/sc/20/change-on-request.html

Guideline 3.3 Input Assistance

Understanding Input Assistance |
How to Meet Input Assistance

Help users avoid and correct mistakes.

Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/error-identification.html
Error
Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/labels-or-instructions.html
Error
Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/error-suggestion.html

/uploads/YR43bC/guidelines/sc/20/error-identification.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/error-prevention-legal-financial-data.html

/uploads/YR43bC/guidelines/sc/20/labels-or-instructions.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/help.html

/uploads/YR43bC/guidelines/sc/20/error-suggestion.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/error-prevention-all.html

/uploads/YR43bC/guidelines/sc/20/error-prevention-legal-financial-data.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/22/accessible-authentication.html

/uploads/YR43bC/guidelines/sc/20/help.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/22/redundant-entry.html

/uploads/YR43bC/guidelines/sc/20/error-prevention-all.html

4. Robust

Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.

Guideline 4.1 Compatible

Understanding Compatible |
How to Meet Compatible

Maximize compatibility with current and future user agents, including assistive technologies.

Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/parsing.html

/uploads/YR43bC/guidelines/sc/20/parsing.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/20/name-role-value.html

/uploads/YR43bC/guidelines/sc/20/name-role-value.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/sc/21/status-messages.html

/uploads/YR43bC/guidelines/sc/21/status-messages.html

5. Conformance

This section lists requirements for conformance to WCAG 2.2. 2.1. It also gives information about how to make conformance claims, which are optional. Finally, it describes what it means to be accessibility supported , since only accessibility-supported ways of using technologies can be relied upon for conformance. Understanding Conformance includes further explanation of the accessibility-supported concept.

5.1 Interpreting Normative Requirements

The main content of WCAG 2.2 2.1 is normative and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as "non-normative", diagrams, examples, and notes are informative (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim.

The key words MAY , MUST , MUST NOT , NOT RECOMMENDED , RECOMMENDED , SHOULD , and SHOULD NOT are to be interpreted as described in [ RFC2119 ].

5.2 Conformance Requirements

In order for a Web page to conform to WCAG 2.2, 2.1, all of the following conformance requirements must be satisfied:

5.2.1 Conformance Level

One of the following levels of conformance is met in full.

  • For Level A conformance (the minimum level of conformance), the Web page satisfies all the Level A Success Criteria, or a conforming alternate version is provided.
  • For Level AA conformance, the Web page satisfies all the Level A and Level AA Success Criteria, or a Level AA conforming alternate version is provided.
  • For Level AAA conformance, the Web page satisfies all the Level A, Level AA and Level AAA Success Criteria, or a Level AAA conforming alternate version is provided.
Note

Although conformance can only be achieved at the stated levels, authors are encouraged to report (in their claim) any progress toward meeting success criteria from all levels beyond the achieved level of conformance.

Note

It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content.

5.2.2 Full pages

Conformance (and conformance level) is for full Web page(s) only, and cannot be achieved if part of a Web page is excluded.

Note

For the purpose of determining conformance, alternatives to part of a page's content are considered part of the page when the alternatives can be obtained directly from the page, e.g., a long description or an alternative presentation of a video.

Note

Authors of Web pages that cannot conform due to content outside of the author's control may consider a Statement of Partial Conformance .

Note

A full page includes each variation of the page that is automatically presented by the page for various screen sizes (e.g. variations in a responsive Web page). Each of these variations needs to conform (or needs to have a conforming alternate version) in order for the entire page to conform.

5.2.3 Complete processes

When a Web page is one of a series of Web pages presenting a process (i.e., a sequence of steps that need to be completed in order to accomplish an activity), all Web pages in the process conform at the specified level or better. (Conformance is not possible at a particular level if any page in the process does not conform at that level or better.)

An online store has a series of pages that are used to select and purchase products. All pages in the series from start to finish (checkout) conform in order for any page that is part of the process to conform.

5.2.4 Only Accessibility-Supported Ways of Using Technologies

Only accessibility-supported ways of using technologies are relied upon to satisfy the success criteria. Any information or functionality that is provided in a way that is not accessibility supported is also available in a way that is accessibility supported. (See Understanding accessibility support .)

5.2.5 Non-Interference

If technologies are used in a way that is not accessibility supported , or if they are used in a non-conforming way, then they do not block the ability of users to access the rest of the page. In addition, the Web page as a whole continues to meet the conformance requirements under each of the following conditions:

  1. when any technology that is not relied upon is turned on in a user agent,
  2. when any technology that is not relied upon is turned off in a user agent, and
  3. when any technology that is not relied upon is not supported by a user agent

In addition, the following success criteria apply to all content on the page, including content that is not otherwise relied upon to meet conformance, because failure to meet them could interfere with any use of the page:

  • 1.4.2 - Audio Control ,
  • 2.1.2 - No Keyboard Trap ,
  • 2.3.1 - Three Flashes or Below Threshold , and
  • 2.2.2 - Pause, Stop, Hide .
Note

If a page cannot conform (for example, a conformance test page or an example page), it cannot be included in the scope of conformance or in a conformance claim.

For more information, including examples, see Understanding Conformance Requirements .

5.3 Conformance Claims (Optional)

Conformance is defined only for Web pages . However, a conformance claim may be made to cover one page, a series of pages, or multiple related Web pages.

5.3.1 Required Components of a Conformance Claim

Conformance claims are not required . Authors can conform to WCAG 2.2 2.1 without making a claim. However, if a conformance claim is made, then the conformance claim must include the following information:

  1. Date of the claim
  2. Guidelines title, version and URI "Web Content Accessibility Guidelines 2.2 2.1 at https://www.w3.org/TR/WCAG22/ https://www.w3.org/TR/WCAG21/ "
  3. Conformance level satisfied: (Level A, AA or AAA)

  4. A concise description of the Web pages , such as a list of URIs for which the claim is made, including whether subdomains are included in the claim.

    Note

    The Web pages may be described by list or by an expression that describes all of the URIs included in the claim.

    Note

    Web-based products that do not have a URI prior to installation on the customer's Web site may have a statement that the product would conform when installed.

  5. A list of the Web content technologies relied upon .
Note

If a conformance logo is used, it would constitute a claim and must be accompanied by the required components of a conformance claim listed above.

5.3.2 Optional Components of a Conformance Claim

In addition to the required components of a conformance claim above, consider providing additional information to assist users. Recommended additional information includes:

  • A list of success criteria beyond the level of conformance claimed that have been met. This information should be provided in a form that users can use, preferably machine-readable metadata.
  • A list of the specific technologies that are " used but not relied upon ."
  • A list of user agents, including assistive technologies that were used to test the content.
  • A list of specific accessibility characteristics of the content, provided in machine-readable metadata.
  • Information about any additional steps taken that go beyond the success criteria to enhance accessibility.
  • A machine-readable metadata version of the list of specific technologies that are relied upon .
  • A machine-readable metadata version of the conformance claim.
Note

Refer to Understanding Conformance Claims for more information and example conformance claims.

Note

Refer to Understanding Metadata for more information about the use of metadata in conformance claims.

5.4 Statement of Partial Conformance - Third Party Content

Sometimes, Web pages are created that will later have additional content added to them. For example, an email program, a blog, an article that allows users to add comments, or applications supporting user-contributed content. Another example would be a page, such as a portal or news site, composed of content aggregated from multiple contributors, or sites that automatically insert content from other sources over time, such as when advertisements are inserted dynamically.

In these cases, it is not possible to know at the time of original posting what the uncontrolled content of the pages will be. It is important to note that the uncontrolled content can affect the accessibility of the controlled content as well. Two options are available:

  1. A determination of conformance can be made based on best knowledge. If a page of this type is monitored and repaired (non-conforming content is removed or brought into conformance) within two business days, then a determination or claim of conformance can be made since, except for errors in externally contributed content which are corrected or removed when encountered, the page conforms. No conformance claim can be made if it is not possible to monitor or correct non-conforming content;

    OR

  2. A "statement of partial conformance" may be made that the page does not conform, but could conform if certain parts were removed. The form of that statement would be, "This page does not conform, but would conform to WCAG 2.2 2.1 at level X if the following parts from uncontrolled sources were removed." In addition, the following would also be true of uncontrolled content that is described in the statement of partial conformance:

    1. It is not content that is under the author's control.
    2. It is described in a way that users can identify (e.g., they cannot be described as "all parts that we do not control" unless they are clearly marked as such.)

5.5 Statement of Partial Conformance - Language

A "statement of partial conformance due to language" may be made when the page does not conform, but would conform if accessibility support existed for (all of) the language(s) used on the page. The form of that statement would be, "This page does not conform, but would conform to WCAG 2.2 2.1 at level X if accessibility support existed for the following language(s):"

6. Glossary

Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/abbreviation.html

/uploads/YR43bC/guidelines/terms/20/abbreviation.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/accessibility-supported.html

/uploads/YR43bC/guidelines/terms/20/accessibility-supported.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/alternative-for-

time

-based-media
.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/ambiguous-

to

-users-in-general
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/ascii-art.html

/uploads/YR43bC/guidelines/terms/20/ascii-art.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/assistive-technology.html

/uploads/YR43bC/guidelines/terms/20/assistive-technology.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/

audio

.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/

audio

-description
.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/

audio

-only
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/blinking.html

/uploads/YR43bC/guidelines/terms/20/blinking.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/blocks-of-text.html

/uploads/YR43bC/guidelines/terms/20/blocks-of-text.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/captcha.html

/uploads/YR43bC/guidelines/terms/20/captcha.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/captions.html

/uploads/YR43bC/guidelines/terms/20/captions.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/changes-of-context.html
Error
Cannot
GET
/uploads/3l9AEc/guidelines/terms/
22
/cognitive-
function
-
test
.
html

/uploads/YR43bC/guidelines/terms/20/changes-of-context.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/conformance.html

/uploads/YR43bC/guidelines/terms/20/conformance.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/conforming-alternate-version.html

/uploads/YR43bC/guidelines/terms/20/conforming-alternate-version.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/

content

.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/context-sensitive-help.html
Error
Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/contrast-ratio.html

/uploads/YR43bC/guidelines/terms/20/context-sensitive-help.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/correct-reading-sequence.html

/uploads/YR43bC/guidelines/terms/20/contrast-ratio.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/21/css-pixel.html

/uploads/YR43bC/guidelines/terms/20/correct-reading-sequence.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/21/down-event.html

/uploads/YR43bC/guidelines/terms/21/css-pixel.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/22/dragging-movement.html

/uploads/YR43bC/guidelines/terms/21/down-event.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/emergency.html

/uploads/YR43bC/guidelines/terms/20/emergency.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/essential.html

/uploads/YR43bC/guidelines/terms/20/essential.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/extended-

audio

-description
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/flash.html
Error
Cannot
GET
/uploads/3l9AEc/guidelines/terms/22/focus.html
Error
Cannot
GET
/uploads/3l9AEc/guidelines/terms/22/focus-indication-area.html

/uploads/YR43bC/guidelines/terms/20/flash.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/functionality.html

/uploads/YR43bC/guidelines/terms/20/functionality.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/general-flash-and-red-flash-thresholds.html

/uploads/YR43bC/guidelines/terms/20/general-flash-and-red-flash-thresholds.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/human-language.html

/uploads/YR43bC/guidelines/terms/20/human-language.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/idiom.html

/uploads/YR43bC/guidelines/terms/20/idiom.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/image-of-text.html

/uploads/YR43bC/guidelines/terms/20/image-of-text.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/informative.html

/uploads/YR43bC/guidelines/terms/20/informative.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/

input

-error
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/jargon.html

/uploads/YR43bC/guidelines/terms/20/jargon.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/keyboard-interface.html

/uploads/YR43bC/guidelines/terms/20/keyboard-interface.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/21/keyboard-shortcut.html

/uploads/YR43bC/guidelines/terms/21/keyboard-shortcut.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/

label

.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/large-scale.html

/uploads/YR43bC/guidelines/terms/20/large-scale.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/legal-commitments.html

/uploads/YR43bC/guidelines/terms/20/legal-commitments.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/link-purpose.html

/uploads/YR43bC/guidelines/terms/20/link-purpose.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/live.html

/uploads/YR43bC/guidelines/terms/20/live.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/lower-secondary-education-level.html

/uploads/YR43bC/guidelines/terms/20/lower-secondary-education-level.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/mechanism.html

/uploads/YR43bC/guidelines/terms/20/mechanism.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/media-alternative-for-text.html

/uploads/YR43bC/guidelines/terms/20/media-alternative-for-text.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


21

/motion-

animation

.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/name.html

/uploads/YR43bC/guidelines/terms/20/name.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/navigated-sequentially.html

/uploads/YR43bC/guidelines/terms/20/navigated-sequentially.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/non-text-

content

.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/normative.html

/uploads/YR43bC/guidelines/terms/20/normative.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/on-

a

-full-screen-window
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/paused.html

/uploads/YR43bC/guidelines/terms/20/paused.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


21

/pointer-

input

.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/prerecorded.html

/uploads/YR43bC/guidelines/terms/20/prerecorded.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/presentation.html

/uploads/YR43bC/guidelines/terms/20/presentation.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/primary-education-level.html

/uploads/YR43bC/guidelines/terms/20/primary-education-level.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/process.html

/uploads/YR43bC/guidelines/terms/20/process.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/programmatically-determined.html

/uploads/YR43bC/guidelines/terms/20/programmatically-determined.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/programmatically-determined-link-context.html

/uploads/YR43bC/guidelines/terms/20/programmatically-determined-link-context.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/programmatically-set.html

/uploads/YR43bC/guidelines/terms/20/programmatically-set.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/pure-decoration.html

/uploads/YR43bC/guidelines/terms/20/pure-decoration.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/real-

time

-event
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/21/region.html

/uploads/YR43bC/guidelines/terms/21/region.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/relationships.html

/uploads/YR43bC/guidelines/terms/20/relationships.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/relative-luminance.html

/uploads/YR43bC/guidelines/terms/20/relative-luminance.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/relied-upon.html

/uploads/YR43bC/guidelines/terms/20/relied-upon.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/role.html

/uploads/YR43bC/guidelines/terms/20/role.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/same-functionality.html

/uploads/YR43bC/guidelines/terms/20/same-functionality.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/same-relative-

order

.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/satisfies-

a

-success-criterion
.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/

section

.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/21/set-of-web-pages.html

/uploads/YR43bC/guidelines/terms/21/set-of-web-pages.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/sign-language.html

/uploads/YR43bC/guidelines/terms/20/sign-language.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/sign-language-interpretation.html

/uploads/YR43bC/guidelines/terms/20/sign-language-interpretation.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/21/single-pointer.html

/uploads/YR43bC/guidelines/terms/21/single-pointer.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/specific-sensory-experience.html

/uploads/YR43bC/guidelines/terms/20/specific-sensory-experience.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/21/state.html

/uploads/YR43bC/guidelines/terms/21/state.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/21/status-message.html

/uploads/YR43bC/guidelines/terms/21/status-message.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/structure.html

/uploads/YR43bC/guidelines/terms/20/structure.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/21/style-property.html

/uploads/YR43bC/guidelines/terms/21/style-property.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/supplemental-

content

.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/synchronized-media.html

/uploads/YR43bC/guidelines/terms/20/synchronized-media.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/21/target.html

/uploads/YR43bC/guidelines/terms/21/target.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/technology.html

/uploads/YR43bC/guidelines/terms/20/technology.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/text.html

/uploads/YR43bC/guidelines/terms/20/text.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/text-alternative.html

/uploads/YR43bC/guidelines/terms/20/text-alternative.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/21/up-event.html

/uploads/YR43bC/guidelines/terms/21/up-event.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/used-in-an-unusual-or-restricted-way.html

/uploads/YR43bC/guidelines/terms/20/used-in-an-unusual-or-restricted-way.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/user-agent.html

/uploads/YR43bC/guidelines/terms/20/user-agent.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/user-controllable.html

/uploads/YR43bC/guidelines/terms/20/user-controllable.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/user-interface-component.html

/uploads/YR43bC/guidelines/terms/20/user-interface-component.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/21/user-inactivity.html

/uploads/YR43bC/guidelines/terms/21/user-inactivity.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/

video

.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/terms/

/uploads/YR43bC/guidelines/terms/


20

/

video

-only
.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/viewport.html

/uploads/YR43bC/guidelines/terms/20/viewport.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/visually-customized.html

/uploads/YR43bC/guidelines/terms/20/visually-customized.html
Error 

Cannot
GET
/uploads/3l9AEc/guidelines/terms/20/web-page.html

/uploads/YR43bC/guidelines/terms/20/web-page.html
Error 

Cannot
GET
/uploads/
3
l9AEc/guidelines/

/uploads/YR43bC/guidelines/


input

-purposes
.html

A. Change Log

This section shows substantive changes made in for WCAG 2.2 2.1 since WCAG 2.1. its publication as a W3C Recommendation. These changes are also recorded as Errata fixes errata .

Changes since the W3C Recommendation of 05 June 2018 :

The full commit history to WCAG 2.1 is available.

B. Acknowledgments

This section is non-normative.

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

Error 

Cannot
GET
/uploads/3l9AEc/acknowledgements/ag-wg-active.html

/uploads/YR43bC/acknowledgements/ag-wg-active.html
Error 

Cannot
GET
/uploads/3l9AEc/acknowledgements/ag-contributors.html

/uploads/YR43bC/acknowledgements/ag-contributors.html
Error 

Cannot
GET
/uploads/3l9AEc/acknowledgements/funders.html

/uploads/YR43bC/acknowledgements/funders.html

C. References

C.1 Informative references

[appmanifest]
Web Application Manifest . Marcos Caceres; Kenneth Christiansen; Matt Giuca; Aaron Gustafson; Daniel Murphy; Anssi Kostiainen. W3C. 29 November 2023. W3C Working Draft. URL: https://www.w3.org/TR/appmanifest/
[css]
Reference not found.
[RFC2119]
Key words for use in RFCs to Indicate Requirement Levels . S. Bradner. IETF. March 1997. Best Current Practice. URL: https://www.rfc-editor.org/rfc/rfc2119
[WAI-WEBCONTENT]
Web Content Accessibility Guidelines 1.0 . Wendy Chisholm; Gregg Vanderheiden; Ian Jacobs. W3C. 5 May 1999. W3C Recommendation. URL: https://www.w3.org/TR/WAI-WEBCONTENT/
[WCAG20]
Web Content Accessibility Guidelines (WCAG) 2.0 . Ben Caldwell; Michael Cooper; Loretta Guarino Reid; Gregg Vanderheiden et al. W3C. 11 December 2008. W3C Recommendation. URL: https://www.w3.org/TR/WCAG20/ [WCAG21] Web Content Accessibility Guidelines (WCAG) 2.1 . Michael Cooper; Andrew Kirkpatrick; Joshue O'Connor; Alastair Campbell. W3C. 21 September 2023. W3C Recommendation. URL: https://www.w3.org/TR/WCAG21/