From 58110ff65bfbda13af4aa2e8adbec15ce7f06a65 Mon Sep 17 00:00:00 2001 From: w3cgruntbot <87540780+w3cgruntbot@users.noreply.github.com> Date: Thu, 19 Dec 2024 19:39:23 +0000 Subject: [PATCH] :robot: Deploy to GitHub Pages: 9383b93391f44964394166c30df2cb42bde554e0 from branch refs/heads/WCAG-2.1 --- guidelines/guidelines.css | 14 +- guidelines/index.html | 4708 +++++++++++++++++++--------- guidelines/relative-luminance.html | 362 +++ 3 files changed, 3549 insertions(+), 1535 deletions(-) create mode 100644 guidelines/relative-luminance.html diff --git a/guidelines/guidelines.css b/guidelines/guidelines.css index f8ede25671..ef3be40bf0 100644 --- a/guidelines/guidelines.css +++ b/guidelines/guidelines.css @@ -34,11 +34,6 @@ dd.new, dd.proposed, dd.changed { display: block; width: 25%; hyphens: none; - padding: 1em; - display: flex; - flex-direction: column; - gap: .5em; - margin-left: 2em; } .sc dt { display: list-item; @@ -55,7 +50,8 @@ dd.new, dd.proposed, dd.changed { div.note-title, div.ednote-title { color: #008400 } -a.internalDFN[title]:hover, .internalDFN[title]:active, a.internalDFN[title]:focus { - cursor: help; -} -span.screenreader {position: absolute; left: -10000px} \ No newline at end of file +/* make links in W3C masthead bold, since we can't make them underline */ +span.screenreader {position: absolute; left: -10000px} +.head p:not(.copyright) > a, .head > a:first-child { + font-weight: bold; +} \ No newline at end of file diff --git a/guidelines/index.html b/guidelines/index.html index 06007cc6e5..9d3e500bf5 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -1,305 +1,113 @@ - + + - Web Content Accessibility Guidelines (WCAG) 2.1 + +Web Content Accessibility Guidelines (WCAG) 2.1 - - - -
- -

Web Content Accessibility Guidelines (WCAG) 2.1

- -

W3C Editor's Draft

-
-
This version:
https://w3c.github.io/wcag/21/guidelines/
Latest published version:
https://www.w3.org/TR/WCAG21/
-
Latest editor's draft:
https://w3c.github.io/wcag/21/guidelines/
- + "publishISODate": "2024-12-19T00:00:00.000Z", + "generatedSubtitle": "W3C Editor's Draft 19 December 2024" +} + +
+

+

Web Content Accessibility Guidelines (WCAG) 2.1

+

W3C Editor's Draft

+
+ More details about this document +
+
This version:
+ https://w3c.github.io/wcag/guidelines/ +
+
Latest published version:
+ https://www.w3.org/TR/WCAG21/ +
+
Latest editor's draft:
https://w3c.github.io/wcag/guidelines/
+
History:
+ https://www.w3.org/standards/history/WCAG21/ +
+ Commit history +
+ +
Implementation report:
+ https://www.w3.org/WAI/WCAG21/implementation-report/ +
+ + +
Latest Recommendation:
https://www.w3.org/TR/WCAG20/
+
Editor:
+ (Nomensa) +
+
+ Former editors: +
+ Andrew Kirkpatrick (Adobe) - Until +
+ (Invited Expert, InterAccess) - Until +
+ Michael Cooper (W3C) - Until +
+ +
Feedback:
+ GitHub w3c/wcag + (pull requests, + new issue, + open issues) +
public-agwg-comments@w3.org with subject line [WCAG21] … message topic … (archives)
+
Errata:
Errata exists.
+ +
+
+

+ Copyright + © + 2020-2024 + World Wide Web Consortium. + W3C® + liability, + trademark and + document use rules apply. +

+
+
+

Abstract

+

Web Content Accessibility Guidelines (WCAG) 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.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.1 extends Web Content Accessibility Guidelines 2.0 [WCAG20], which was published as a W3C Recommendation December 2008. Content that conforms to WCAG 2.1 also conforms to WCAG 2.0. The WG intends that for policies requiring conformance to WCAG 2.0, WCAG 2.1 can provide an alternate means of conformance. The publication of WCAG 2.1 does not deprecate or supersede WCAG 2.0. While WCAG 2.0 remains a W3C Recommendation, the W3C advises the use of WCAG 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 section describes the status of this + document at the time of its publication. 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 a Recommendation of WCAG 2.1 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. +

Publication as an Editor's Draft does not + imply endorsement by W3C and its Members.

+ This is a draft document and may be updated, replaced or obsoleted by other + documents at any time. It is inappropriate to cite this document as other + than work in progress. -

Latest Recommendation:
https://www.w3.org/TR/2018/REC-WCAG21-20180605/
-
Editors:
-
(Adobe)
(Invited Expert, InterAccess)
(Nomensa)
(W3C)
-
WCAG 2.0 Editors (until December 2008):
Ben Caldwell (Trace R&D Center, University of Wisconsin-Madison)
Loretta Guarino Reid (Google, Inc.)
Gregg Vanderheiden (Trace R&D Center, University of Wisconsin-Madison)
Wendy Chisholm (W3C)
John Slatin (Accessibility Institute, University of Texas at Austin)
Jason White (University of Melbourne)
+

+ This document was produced by a group + operating under the + W3C Patent + Policy. + -

- - - -

- Copyright © - 2017-2018 - - W3C® - (MIT, - ERCIM, - Keio, Beihang). + 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. - W3C liability, - trademark and - document use - rules apply. -

-
-
-

Abstract

-

Web Content Accessibility Guidelines (WCAG) 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.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.1 extends Web Content Accessibility Guidelines 2.0 [WCAG20], which was published as a W3C Recommendation December 2008. Content that conforms to WCAG 2.1 also conforms to WCAG 2.0. The WG intends that for policies requiring conformance to WCAG 2.0, WCAG 2.1 can provide an alternate means of conformance. The publication of WCAG 2.1 does not deprecate or supersede WCAG 2.0. While WCAG 2.0 remains a W3C Recommendation, the W3C advises the use of WCAG 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 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 of Web Content Accessibility Guidelines (WCAG) 2.1. WCAG 2.1 is a W3C Recommendation. This draft incorporates errata and are described in the change log. At some point these changes might be incorporated into a 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. - -

- - Comments regarding this document are welcome. - Please send them to - public-agwg-comments@w3.org - (archives). - -

- Publication as an Editor's Draft does not imply endorsement by the W3C - Membership. This is a draft document and may be updated, replaced or obsoleted by other - documents at any time. It is inappropriate to cite this document as other than work in - progress. -

- - 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 February 2018 W3C Process Document. -

-
-

Introduction

This section is non-normative.

-
-

0.1 Background on WCAG 2§

+

+ This document is governed by the + 03 November 2023 W3C Process Document. +

+

Introduction

This section is non-normative.

+ +

Background on WCAG 2

+

Web Content Accessibility Guidelines (WCAG) 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.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.1 builds on WCAG 2.0 [WCAG20], 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.

+

WCAG 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.1 builds on WCAG 2.0 [WCAG20], 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.

+

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.

-
-

0.2 WCAG 2 Layers of Guidance§

+

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.

  • @@ -563,8 +337,8 @@

    0.2 WCAG 2 La

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

-
-

0.3 WCAG 2.1 Supporting Documents§

+

WCAG 2.1 Supporting Documents

+

The WCAG 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.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. @@ -580,19 +354,19 @@

    0.3 WCAG

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

+

See Web Content Accessibility Guidelines (WCAG) Overview for a description of the WCAG 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.

-
-

0.4 Requirements for WCAG 2.1§

-

WCAG 2.1 meets a set of requirements for WCAG 2.1 which, in turn, inherit requirements from WCAG 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.1. This constraint was important to preserve its nature as a dot-release of WCAG 2.

+

Requirements for WCAG 2.1

+ +

WCAG 2.1 meets a set of requirements for WCAG 2.1 which, in turn, inherit requirements from WCAG 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.1. This constraint was important to preserve its nature as a dot-release of WCAG 2.

-
-

0.5 Comparison with WCAG 2.0§

+

Comparison with WCAG 2.0

+

WCAG 2.1 was initiated with the goal to 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.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.1 builds on and is backwards compatible with WCAG 2.0, meaning web pages that conform to WCAG 2.1 also conform to WCAG 2.0. Authors that are required by policy to conform with WCAG 2.0 will be able to update content to WCAG 2.1 without losing conformance with WCAG 2.0. Authors following both sets of guidelines should be aware of the following differences:

-
-

0.5.1 New Features in WCAG 2.1§

+

New Features in WCAG 2.1

+

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

The following Success Criteria are new in WCAG 2.1:

-

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

+

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 the Conformance section, a third note about page variants has been added to Full Pages, and an option for machine-readable metadata added to Optional Components of a Conformance Claim.

-
-

0.5.2 Numbering in WCAG 2.1§

+

Numbering in WCAG 2.1

+

In order to avoid confusion for implementers for whom backwards compatibility to WCAG 2.0 is important, new success criteria in WCAG 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.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.1 Quick Reference provides ways to view success criteria grouped by conformance level, along with many other filter and sort options.

-
-

0.5.3 Conformance to WCAG 2.1§

+

Conformance to WCAG 2.1

+

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

-
-

0.6 Later Versions of Accessibility Guidelines§

+

Later Versions of Accessibility Guidelines

+

In parallel with WCAG 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.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 §

+

1. Perceivable

+

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

-
-

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

+

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.

-
+

Success Criterion 1.1.1 Non-text Content

+ -

Success Criterion 1.1.1 Non-text Content§

-
Understanding Non-text Content |
How to Meet Non-text Content

(Level A)

+
Understanding Non-text Content |
How to Meet Non-text Content

(Level A)

-

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. +

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.

@@ -654,7 +428,7 @@

Success Criterion 1.1.1 -

If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 for additional requirements for controls and content that accepts user input.) +

If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 for additional requirements for controls and content that accepts user input.)

@@ -673,7 +447,7 @@

Success Criterion 1.1.1 -

If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text +

If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.

@@ -683,13 +457,13 @@

Success Criterion 1.1.1 -

If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text +

If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.

-
CAPTCHA
+
CAPTCHA
@@ -706,8 +480,8 @@

Success Criterion 1.1.1 -

If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented - in a way that it can be ignored by assistive technology. +

If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented + in a way that it can be ignored by assistive technology.

@@ -715,20 +489,21 @@

Success Criterion 1.1.1

+
-
-

Guideline 1.2 Time-based Media§

-

Provide alternatives for time-based media.

+

Guideline 1.2 Time-based Media

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

Provide alternatives for time-based media.

-
+

Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded)

-

Success Criterion 1.2.1 Audio-only and Video-only (Prerecorded)§

-
Understanding Audio-only and Video-only (Prerecorded) |
How to Meet Audio-only and Video-only (Prerecorded)

(Level A)

-

For prerecorded - audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: +

Understanding Audio-only and Video-only (Prerecorded) |
How to Meet Audio-only and Video-only (Prerecorded)

(Level A)

+ +

For prerecorded + audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:

@@ -737,7 +512,7 @@

Succes
-

An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content. +

An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.

@@ -756,235 +531,241 @@

Succes

-
+ +

Success Criterion 1.2.2 Captions (Prerecorded)

-

Success Criterion 1.2.2 Captions (Prerecorded)§

-
Understanding Captions (Prerecorded) |
How to Meet Captions (Prerecorded)

(Level A)

-

Captions are provided for all prerecorded - audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. +

Understanding Captions (Prerecorded) |
How to Meet Captions (Prerecorded)

(Level A)

+ +

Captions are provided for all prerecorded + audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

-
+ +

Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded)

-

Success Criterion 1.2.3 Audio Description or Media Alternative (Prerecorded)§

-
Understanding Audio Description or Media Alternative (Prerecorded) |
How to Meet Audio Description or Media Alternative (Prerecorded)

(Level A)

-

An alternative for time-based media or audio description of the prerecorded - video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. +

Understanding Audio Description or Media Alternative (Prerecorded) |
How to Meet Audio Description or Media Alternative (Prerecorded)

(Level A)

+ +

An alternative for time-based media or audio description of the prerecorded + video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

-
+ +

Success Criterion 1.2.4 Captions (Live)

-

Success Criterion 1.2.4 Captions (Live)§

-
Understanding Captions (Live) |
How to Meet Captions (Live)

(Level AA)

-

Captions are provided for all live - audio content in synchronized media. +

Understanding Captions (Live) |
How to Meet Captions (Live)

(Level AA)

+ +

Captions are provided for all live + audio content in synchronized media.

-
+ +

Success Criterion 1.2.5 Audio Description (Prerecorded)

-

Success Criterion 1.2.5 Audio Description (Prerecorded)§

-
Understanding Audio Description (Prerecorded) |
How to Meet Audio Description (Prerecorded)

(Level AA)

-

Audio description is provided for all prerecorded - video content in synchronized media. +

Understanding Audio Description (Prerecorded) |
How to Meet Audio Description (Prerecorded)

(Level AA)

+ +

Audio description is provided for all prerecorded + video content in synchronized media.

-
+ +

Success Criterion 1.2.6 Sign Language (Prerecorded)

-

Success Criterion 1.2.6 Sign Language (Prerecorded)§

-
Understanding Sign Language (Prerecorded) |
How to Meet Sign Language (Prerecorded)

(Level AAA)

-

Sign language interpretation is provided for all prerecorded - audio content in synchronized media. +

Understanding Sign Language (Prerecorded) |
How to Meet Sign Language (Prerecorded)

(Level AAA)

+ +

Sign language interpretation is provided for all prerecorded + audio content in synchronized media.

-
+ +

Success Criterion 1.2.7 Extended Audio Description (Prerecorded)

-

Success Criterion 1.2.7 Extended Audio Description (Prerecorded)§

-
Understanding Extended Audio Description (Prerecorded) |
How to Meet Extended Audio Description (Prerecorded)

(Level AAA)

-

Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded - video content in synchronized media. +

Understanding Extended Audio Description (Prerecorded) |
How to Meet Extended Audio Description (Prerecorded)

(Level AAA)

+ +

Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded + video content in synchronized media.

-
+ +

Success Criterion 1.2.8 Media Alternative (Prerecorded)

-

Success Criterion 1.2.8 Media Alternative (Prerecorded)§

-
Understanding Media Alternative (Prerecorded) |
How to Meet Media Alternative (Prerecorded)

(Level AAA)

-

An alternative for time-based media is provided for all prerecorded - synchronized media and for all prerecorded video-only media. +

Understanding Media Alternative (Prerecorded) |
How to Meet Media Alternative (Prerecorded)

(Level AAA)

+ +

An alternative for time-based media is provided for all prerecorded + synchronized media and for all prerecorded video-only media.

-
+ +

Success Criterion 1.2.9 Audio-only (Live)

-

Success Criterion 1.2.9 Audio-only (Live)§

-
Understanding Audio-only (Live) |
How to Meet Audio-only (Live)

(Level AAA)

-

An alternative for time-based media that presents equivalent information for live - audio-only content is provided. +

Understanding Audio-only (Live) |
How to Meet Audio-only (Live)

(Level AAA)

+ +

An alternative for time-based media that presents equivalent information for live + audio-only content is provided.

+
-
-

Guideline 1.3 Adaptable§

-

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

+

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.

-
+

Success Criterion 1.3.1 Info and Relationships

+ -

Success Criterion 1.3.1 Info and Relationships§

-
Understanding Info and Relationships |
How to Meet Info and Relationships

(Level A)

+
Understanding Info and Relationships |
How to Meet Info and Relationships

(Level A)

-

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. +

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

-
+ +

Success Criterion 1.3.2 Meaningful Sequence

+ -

Success Criterion 1.3.2 Meaningful Sequence§

-
Understanding Meaningful Sequence |
How to Meet Meaningful Sequence

(Level A)

+
Understanding Meaningful Sequence |
How to Meet Meaningful Sequence

(Level A)

-

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. +

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

-
+ +

Success Criterion 1.3.3 Sensory Characteristics

+ -

Success Criterion 1.3.3 Sensory Characteristics§

-
Understanding Sensory Characteristics |
How to Meet Sensory Characteristics

(Level A)

+
Understanding Sensory Characteristics |
How to Meet Sensory Characteristics

(Level A)

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.

-
Note

For requirements related to color, refer to Guideline 1.4.

+
Note

For requirements related to color, refer to Guideline 1.4.

-
- -

Success Criterion 1.3.4 Orientation§

- -
Understanding Orientation |
How to Meet Orientation

(Level AA)

+

Success Criterion 1.3.4 Orientation

-

Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.

+
Understanding Orientation |
How to Meet Orientation

(Level AA)

+ +

Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.

-
Note

Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality content where binary display orientation is not applicable.

+
Note

Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality content where content is not necessarily restricted to landscape or portrait display orientation.

-
- -

Success Criterion 1.3.5 Identify Input Purpose§

+

Success Criterion 1.3.5 Identify Input Purpose

-
Understanding Identify Input Purpose |
How to Meet Identify Input Purpose

(Level AA)

+
Understanding Identify Input Purpose |
How to Meet Identify Input Purpose

(Level AA)

-

The purpose of each input field collecting information about the user can be programmatically determined when:

+

The purpose of each input field collecting information about the user can be programmatically determined when:

-
+

Success Criterion 1.3.6 Identify Purpose

-

Success Criterion 1.3.6 Identify Purpose§

+ -
Understanding Identify Purpose |
How to Meet Identify Purpose

(Level AAA)

+
Understanding Identify Purpose |
How to Meet Identify Purpose

(Level AAA)

- - -

In content implemented using markup languages, the purpose of User Interface Components, icons, and regions can be programmatically determined.

+

In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined.

-
-

Guideline 1.4 Distinguishable§

-

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

+

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.

-
+

Success Criterion 1.4.1 Use of Color

+ -

Success Criterion 1.4.1 Use of Color§

-
Understanding Use of Color |
How to Meet Use of Color

(Level A)

+
Understanding Use of Color |
How to Meet Use of Color

(Level A)

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

-
Note

This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.

+
Note

This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.

-
+

Success Criterion 1.4.2 Audio Control

-

Success Criterion 1.4.2 Audio Control§

-
Understanding Audio Control |
How to Meet Audio Control

(Level A)

-

If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio +

Understanding Audio Control |
How to Meet Audio Control

(Level A)

+ +

If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.

-
Note

Since any content that does not meet this success criterion can interfere with a user's +

Note

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

-
+ +

Success Criterion 1.4.3 Contrast (Minimum)

-

Success Criterion 1.4.3 Contrast (Minimum)§

-
Understanding Contrast (Minimum) |
How to Meet Contrast (Minimum)

(Level AA)

-

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: +

Understanding Contrast (Minimum) |
How to Meet Contrast (Minimum)

(Level AA)

+ +

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:

@@ -993,7 +774,7 @@

Success Criterion 1.4.3 -

Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; +

Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;

@@ -1002,7 +783,7 @@

Success Criterion 1.4.3 -

Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant +

Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.

@@ -1020,24 +801,26 @@

Success Criterion 1.4.3 -
+ +

Success Criterion 1.4.4 Resize Text

-

Success Criterion 1.4.4 Resize text§

-
Understanding Resize text |
How to Meet Resize text

(Level AA)

-

Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. +

Understanding Resize Text |
How to Meet Resize Text

(Level AA)

+ +

Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

-
+ +

Success Criterion 1.4.5 Images of Text

-

Success Criterion 1.4.5 Images of Text§

-
Understanding Images of Text |
How to Meet Images of Text

(Level AA)

-

If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: +

Understanding Images of Text |
How to Meet Images of Text

(Level AA)

+ +

If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following:

@@ -1046,7 +829,7 @@

Success Criterion 1.4.5 -

The image of text can be visually customized to the user's requirements; +

The image of text can be visually customized to the user's requirements;

@@ -1055,24 +838,25 @@

Success Criterion 1.4.5 -

A particular presentation of text is essential to the information being conveyed. +

A particular presentation of text is essential to the information being conveyed.

-
Note

Logotypes (text that is part of a logo or brand name) are considered essential.

+
Note

Logotypes (text that is part of a logo or brand name) are considered essential.

-
+ +

Success Criterion 1.4.6 Contrast (Enhanced)

-

Success Criterion 1.4.6 Contrast (Enhanced)§

-
Understanding Contrast (Enhanced) |
How to Meet Contrast (Enhanced)

(Level AAA)

-

The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following: +

Understanding Contrast (Enhanced) |
How to Meet Contrast (Enhanced)

(Level AAA)

+ +

The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following:

@@ -1081,7 +865,7 @@

Success Criterion 1.4.6 -

Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1; +

Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1;

@@ -1090,7 +874,7 @@

Success Criterion 1.4.6 -

Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant +

Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.

@@ -1108,15 +892,16 @@

Success Criterion 1.4.6 -
+ +

Success Criterion 1.4.7 Low or No Background Audio

-

Success Criterion 1.4.7 Low or No Background Audio§

-
Understanding Low or No Background Audio |
How to Meet Low or No Background Audio

(Level AAA)

-

For prerecorded - audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio - CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression +

Understanding Low or No Background Audio |
How to Meet Low or No Background Audio

(Level AAA)

+ +

For prerecorded + audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio + CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true:

@@ -1146,7 +931,7 @@

Success Criterion with the exception of occasional sounds that last for only one or two seconds.

-
Note

Per the definition of "decibel," background sound that meets this requirement will +

Note

Per the definition of "decibel," background sound that meets this requirement will be approximately four times quieter than the foreground speech content.

@@ -1156,96 +941,90 @@

Success Criterion

-
+ +

Success Criterion 1.4.8 Visual Presentation

+ -

Success Criterion 1.4.8 Visual Presentation§

-
Understanding Visual Presentation |
How to Meet Visual Presentation

(Level AAA)

+
Understanding Visual Presentation |
How to Meet Visual Presentation

(Level AAA)

-

For the visual presentation of blocks of text, a mechanism is available to achieve the following: +

For the visual presentation of blocks of text, a mechanism is available to achieve the following:

  • Foreground and background colors can be selected by the user.
  • Width is no more than 80 characters or glyphs (40 if CJK).
  • Text is not justified (aligned to both the left and the right margins).
  • Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.
    • -
  • Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window.
    • +
  • Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window.
- +
-
+

Success Criterion 1.4.9 Images of Text (No Exception)

+ -

Success Criterion 1.4.9 Images of Text (No Exception)§

-
Understanding Images of Text (No Exception) |
How to Meet Images of Text (No Exception)

(Level AAA)

+
Understanding Images of Text (No Exception) |
How to Meet Images of Text (No Exception)

(Level AAA)

-

Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. +

Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.

-
Note

Logotypes (text that is part of a logo or brand name) are considered essential.

+
Note

Logotypes (text that is part of a logo or brand name) are considered essential.

-
- -

Success Criterion 1.4.10 Reflow§

- -
Understanding Reflow |
How to Meet Reflow

(Level AA)

+ +

Success Criterion 1.4.10 Reflow

+
Understanding Reflow |
How to Meet Reflow

(Level AA)

+

Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:

    -
  • Vertical scrolling content at a width equivalent to 320 CSS pixels;
    • -
  • Horizontal scrolling content at a height equivalent to 256 CSS pixels.
    • +
  • Vertical scrolling content at a width equivalent to 320 CSS pixels;
    • +
  • Horizontal scrolling content at a height equivalent to 256 CSS pixels.

Except for parts of the content which require two-dimensional layout for usage or meaning.

-
Note

320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which are designed to scroll horizontally (e.g. with vertical text), the 256 CSS pixels is equivalent to a starting viewport height of 1024px at 400% zoom.

+
Note

320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which is designed to scroll horizontally (e.g., with vertical text), 256 CSS pixels is equivalent to a starting viewport height of 1024 CSS pixels at 400% zoom.

-
Note

Examples of content which require two-dimensional layout are images, maps, diagrams, - video, games, presentations, data tables, and interfaces where it is necessary to keep toolbars in view while - manipulating content.

+
Note

Examples of content which requires two-dimensional layout are images required for understanding (such as maps and diagrams), video, games, presentations, data tables (not individual cells), and interfaces where it is necessary to keep toolbars in view while manipulating content. It is acceptable to provide two-dimensional scrolling for such parts of the content.

-
- -

Success Criterion 1.4.11 Non-text Contrast§

- -
Understanding Non-text Contrast |
How to Meet Non-text Contrast

(Level AA)

+

Success Criterion 1.4.11 Non-text Contrast

-

The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):

+
Understanding Non-text Contrast |
How to Meet Non-text Contrast

(Level AA)

+ +

The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):

User Interface Components
-
Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
+
Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
Graphical Objects
-
Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
+
Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
-
+

Success Criterion 1.4.12 Text Spacing

-

Success Criterion 1.4.12 Text Spacing§

+ -
Understanding Text Spacing |
How to Meet Text Spacing

(Level AA)

+
Understanding Text Spacing |
How to Meet Text Spacing

(Level AA)

- - -

In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:

+

In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:

  • Line height (line spacing) to at least 1.5 times the font size;
    • @@ -1255,24 +1034,22 @@

    Success Criterion 1.4.12

    Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.

    - +

-
- -

Success Criterion 1.4.13 Content on Hover or Focus§

- -
Understanding Content on Hover or Focus |
How to Meet Content on Hover or Focus

(Level AA)

- +

Success Criterion 1.4.13 Content on Hover or Focus

+ +
Understanding Content on Hover or Focus |
How to Meet Content on Hover or Focus

(Level AA)

+

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, 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 communicates an input error or does not obscure or replace other content;
+
A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or 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;
@@ -1284,93 +1061,95 @@

Success Criterion

Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.

-
Note

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

-
Note

Custom tooltips, sub-menus, and other nonmodal popups that display on hover and focus are examples of additional content covered by this criterion.

+
Note

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

+
Note

Custom tooltips, sub-menus, and other nonmodal popups that display on hover and focus are examples of additional content covered by this criterion.

+
-
-

2. Operable §

+

2. Operable

+

User interface components and navigation must be operable.

-
-

Guideline 2.1 Keyboard Accessible§

-

Make all functionality available from a keyboard.

+

Guideline 2.1 Keyboard Accessible

+ +
Understanding Keyboard Accessible |
How to Meet Keyboard Accessible

Make all functionality available from a keyboard.

-
+

Success Criterion 2.1.1 Keyboard

-

Success Criterion 2.1.1 Keyboard§

-
Understanding Keyboard |
How to Meet Keyboard

(Level A)

-

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying +

Understanding Keyboard |
How to Meet Keyboard

(Level A)

+ +

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

-
Note

This exception relates to the underlying function, not the input technique. For example, +

Note

This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.

-
Note

This does not forbid and should not discourage providing mouse input or other input +

Note

This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

-
+ +

Success Criterion 2.1.2 No Keyboard Trap

-

Success Criterion 2.1.2 No Keyboard Trap§

-
Understanding No Keyboard Trap |
How to Meet No Keyboard Trap

(Level A)

-

If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, +

Understanding No Keyboard Trap |
How to Meet No Keyboard Trap

(Level A)

+ +

If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

-
Note

Since any content that does not meet this success criterion can interfere with a user's +

Note

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

-
+ +

Success Criterion 2.1.3 Keyboard (No Exception)

-

Success Criterion 2.1.3 Keyboard (No Exception)§

-
Understanding Keyboard (No Exception) |
How to Meet Keyboard (No Exception)

(Level AAA)

-

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. +

Understanding Keyboard (No Exception) |
How to Meet Keyboard (No Exception)

(Level AAA)

+ +

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

+ -
+

Success Criterion 2.1.4 Character Key Shortcuts

-

Success Criterion 2.1.4 Character Key Shortcuts§

+ -
Understanding Character Key Shortcuts |
How to Meet Character Key Shortcuts

(Level A)

+
Understanding Character Key Shortcuts |
How to Meet Character Key Shortcuts

(Level A)

- - -

If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:

+

If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:

Turn off
-
A mechanism is available to turn the shortcut off;
+
A mechanism is available to turn the shortcut off;
Remap
-
A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc);
+
A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt);
Active only on focus
-
The keyboard shortcut for a user interface component is only active when that component has focus.
+
The keyboard shortcut for a user interface component is only active when that component has focus.
@@ -1378,15 +1157,15 @@

Success Criterion 2.

-
-

Guideline 2.2 Enough Time§

-

Provide users enough time to read and use content.

+

Guideline 2.2 Enough Time

+ +
Understanding Enough Time |
How to Meet Enough Time

Provide users enough time to read and use content.

-
+

Success Criterion 2.2.1 Timing Adjustable

-

Success Criterion 2.2.1 Timing Adjustable§

-
Understanding Timing Adjustable |
How to Meet Timing Adjustable

(Level A)

+ +
Understanding Timing Adjustable |
How to Meet Timing Adjustable

(Level A)

For each time limit that is set by the content, at least one of the following is true:

@@ -1435,7 +1214,7 @@

Success Criterion 2.2.1 -

The time limit is essential and extending it would invalidate the activity; or +

The time limit is essential and extending it would invalidate the activity; or

@@ -1450,20 +1229,21 @@

Success Criterion 2.2.1 -
Note

This success criterion helps ensure that users can complete tasks without unexpected +

Note

This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

-
+ +

Success Criterion 2.2.2 Pause, Stop, Hide

-

Success Criterion 2.2.2 Pause, Stop, Hide§

-
Understanding Pause, Stop, Hide |
How to Meet Pause, Stop, Hide

(Level A)

-

For moving, blinking, scrolling, or auto-updating information, all of the following are true: +

Understanding Pause, Stop, Hide |
How to Meet Pause, Stop, Hide

(Level A)

+ +

For moving, blinking, scrolling, or auto-updating information, all of the following are true:

@@ -1474,8 +1254,8 @@

Success Criterion 2.2.2 For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, - there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity - where it is essential; and + there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity + where it is essential; and

@@ -1494,56 +1274,59 @@

Success Criterion 2.2.2 -
Note

For requirements related to flickering or flashing content, refer to Guideline 2.3. +

Note

For requirements related to flickering or flashing content, refer to Guideline 2.3.

-
Note

Since any content that does not meet this success criterion can interfere with a user's +

Note

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

-
Note

Content that is updated periodically by software or that is streamed to the user agent +

Note

Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.

-
Note

An animation that occurs as part of a preload phase or similar situation can be considered +

Note

An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.

-
+ +

Success Criterion 2.2.3 No Timing

-

Success Criterion 2.2.3 No Timing§

-
Understanding No Timing |
How to Meet No Timing

(Level AAA)

-

Timing is not an essential part of the event or activity presented by the content, except for non-interactive - synchronized media and real-time events. +

Understanding No Timing |
How to Meet No Timing

(Level AAA)

+ +

Timing is not an essential part of the event or activity presented by the content, except for non-interactive + synchronized media and real-time events.

-
+ +

Success Criterion 2.2.4 Interruptions

-

Success Criterion 2.2.4 Interruptions§

-
Understanding Interruptions |
How to Meet Interruptions

(Level AAA)

+ +
Understanding Interruptions |
How to Meet Interruptions

(Level AAA)

Interruptions can be postponed or suppressed by the user, except interruptions involving - an emergency. + an emergency.

-
+ +

Success Criterion 2.2.5 Re-authenticating

-

Success Criterion 2.2.5 Re-authenticating§

-
Understanding Re-authenticating |
How to Meet Re-authenticating

(Level AAA)

+ +
Understanding Re-authenticating |
How to Meet Re-authenticating

(Level AAA)

When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. @@ -1551,147 +1334,152 @@

Success Criterion 2.2.5 -
- -

Success Criterion 2.2.6 Timeouts§

- -
Understanding Timeouts |
How to Meet Timeouts

(Level AAA)

+ +

Success Criterion 2.2.6 Timeouts

-

Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.

+
Understanding Timeouts |
How to Meet Timeouts

(Level AAA)

+ +

Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.

-
Note

Privacy regulations may require explicit user consent before user identification has been authenticated and before user data is preserved. In cases where the user is a minor, explicit consent may not be solicited in most jurisdictions, countries or regions. Consultation with privacy professionals and legal counsel is advised when considering data preservation as an approach to satisfy this success criterion.

+
Note

Privacy regulations may require explicit user consent before user identification has been authenticated and before user data is preserved. In cases where the user is a minor, explicit consent may not be solicited in most jurisdictions, countries or regions. Consultation with privacy professionals and legal counsel is advised when considering data preservation as an approach to satisfy this success criterion.

-
-

Guideline 2.3 Seizures and Physical Reactions§

-

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

+

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.

-
+

Success Criterion 2.3.1 Three Flashes or Below Threshold

-

Success Criterion 2.3.1 Three Flashes or Below Threshold§

-
Understanding Three Flashes or Below Threshold |
How to Meet Three Flashes or Below Threshold

(Level A)

-

Web pages do not contain anything that flashes more than three times in any one second period, - or the flash is below the general flash and red flash thresholds. +

Understanding Three Flashes or Below Threshold |
How to Meet Three Flashes or Below Threshold

(Level A)

+ +

Web pages do not contain anything that flashes more than three times in any one second period, + or the flash is below the general flash and red flash thresholds.

-
Note

Since any content that does not meet this success criterion can interfere with a user's +

Note

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

-
+ +

Success Criterion 2.3.2 Three Flashes

+ -

Success Criterion 2.3.2 Three Flashes§

-
Understanding Three Flashes |
How to Meet Three Flashes

(Level AAA)

+
Understanding Three Flashes |
How to Meet Three Flashes

(Level AAA)

-

Web pages do not contain anything that flashes more than three times in any one second period. +

Web pages do not contain anything that flashes more than three times in any one second period.

+ -
+

Success Criterion 2.3.3 Animation from Interactions

-

Success Criterion 2.3.3 Animation from Interactions§

+ -
Understanding Animation from Interactions |
How to Meet Animation from Interactions

(Level AAA)

+
Understanding Animation from Interactions |
How to Meet Animation from Interactions

(Level AAA)

- - -

Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.

+

Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.

-