diff --git a/.gitignore b/.gitignore index c23c97841c..26d41dc54a 100644 --- a/.gitignore +++ b/.gitignore @@ -220,3 +220,21 @@ pip-log.txt ############# build.properties + +############# +## Output +############# + +/output/ +/output.html +/techniques/toc.html +/techniques/techniques.xml +/techniques/technique-associations.xml +/techniques/index-flat.html +/techniques/about-flat.html +/understanding/toc.html +/understanding/index-flat.html +/understanding/about-flat.html +/guidelines/wcag.xml +/guidelines/versions.xml +/guidelines/index-flat.html diff --git a/acknowledgements/funders.html b/acknowledgements/funders.html index 77b78f87d7..cc6ccd68eb 100644 --- a/acknowledgements/funders.html +++ b/acknowledgements/funders.html @@ -1,4 +1,4 @@ -
-

Enabling funders

+
+

Enabling funders

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

-
\ No newline at end of file +
diff --git a/act.xml b/act.xml new file mode 100644 index 0000000000..b994f53627 --- /dev/null +++ b/act.xml @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/biblio.js b/biblio.js index c87140e278..4a35866972 100644 --- a/biblio.js +++ b/biblio.js @@ -30,18 +30,13 @@ respecConfig.localBiblio = { "title": "Ergonomics of human-system interaction -- Part 112: Principles for the presentation of information", "publisher": "International Standards Organization" }, - - "sRGB": { - "authors": [ - "M. Stokes", - "M. Anderson", - "S. Chandrasekar", - "R. Motta" - ], - "date": "November 5, 1996", - "href": "https://www.w3.org/Graphics/Color/sRGB.html", - "title": "A Standard Default Color Space for the Internet - sRGB, Version 1.10" - }, + + "ISO_9241-391": { + "isoNumber": "9241-391", + "href": "https://www.iso.org/standard/56350.html", + "title": "Ergonomics of human-system interaction—Part 391: Requirements, analysis and compliance test methods for the reduction of photosensitive seizures", + "publisher": "International Standards Organization" + }, "UNESCO": { "date": "1997", diff --git a/build.xml b/build.xml index 6a77f60971..baa6dec34c 100644 --- a/build.xml +++ b/build.xml @@ -10,7 +10,7 @@ - + @@ -42,11 +42,15 @@ + + + + @@ -61,7 +65,7 @@ - + @@ -101,7 +105,7 @@ - + @@ -168,7 +172,7 @@ - + @@ -188,10 +192,12 @@ + + + - @@ -204,7 +210,7 @@ - + @@ -212,7 +218,7 @@ - + @@ -223,11 +229,38 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + - + @@ -245,10 +278,10 @@ + - - + @@ -263,15 +296,39 @@ - + + + + + + + + + + + + + + + + + + + + + + + + + - + - + @@ -282,7 +339,10 @@ + + + @@ -328,18 +388,27 @@ - + + + + + + + + + + - + - + - + @@ -352,6 +421,22 @@ + + + + + + + + + + + + + + + + diff --git a/css/a11y-light.css b/css/a11y-light.css new file mode 100644 index 0000000000..f1bf8f3f8f --- /dev/null +++ b/css/a11y-light.css @@ -0,0 +1,99 @@ +/* a11y-light theme */ +/* Based on the Tomorrow Night Eighties theme: https://github.com/isagalaev/highlight.js/blob/master/src/styles/tomorrow-night-eighties.css */ +/* @author: ericwbailey */ + +/* Comment */ +.hljs-comment, +.hljs-quote { + color: #696969; +} + +/* Red */ +.hljs-variable, +.hljs-template-variable, +.hljs-tag, +.hljs-name, +.hljs-selector-id, +.hljs-selector-class, +.hljs-regexp, +.hljs-deletion { + color: #d91e18; +} + +/* Orange */ +.hljs-number, +.hljs-built_in, +.hljs-builtin-name, +.hljs-literal, +.hljs-type, +.hljs-params, +.hljs-meta, +.hljs-link { + color: #aa5d00; +} + +/* Yellow */ +.hljs-attribute { + color: #aa5d00; +} + +/* Green */ +.hljs-string, +.hljs-symbol, +.hljs-bullet, +.hljs-addition { + color: #008000; +} + +/* Blue */ +.hljs-title, +.hljs-section { + color: #007faa; +} + +/* Purple */ +.hljs-keyword, +.hljs-selector-tag { + color: #7928a1; +} + +.hljs { + display: block; + overflow-x: auto; + background: #fefefe; + color: #545454; + padding: 0.5em; +} + +.hljs-emphasis { + font-style: italic; +} + +.hljs-strong { + font-weight: bold; +} + +@media screen and (-ms-high-contrast: active) { + .hljs-addition, + .hljs-attribute, + .hljs-built_in, + .hljs-builtin-name, + .hljs-bullet, + .hljs-comment, + .hljs-link, + .hljs-literal, + .hljs-meta, + .hljs-number, + .hljs-params, + .hljs-string, + .hljs-symbol, + .hljs-type, + .hljs-quote { + color: highlight; + } + + .hljs-keyword, + .hljs-selector-tag { + font-weight: bold; + } +} diff --git a/css/base.css b/css/base.css index b028c7b059..9076df76a2 100644 --- a/css/base.css +++ b/css/base.css @@ -1,17 +1,376 @@ -.wcag21, .wcag22 { - background-color: #E9FBE9; - border-left: solid .5em #52E052; +main { + display: block; } -span.wcag21, span.wcag22 { - margin-left: .25em; - padding-left: .25em; + +.nav-container { + background-image: linear-gradient(#d0e1f1 0, #d0e1f1 50px, #fff 50px); } -div.wcag21, div.wcag22 { - margin: 1em auto; - padding: .5em; - page-break-inside: avoid; + +.nav__item a { + display: inline-block; } -.new-version { - font-size: smaller; + +.nav__item a svg { + vertical-align: middle; + height: 1em; +} + +.nav__item a + button { + margin-left: -0.75em; + margin-right: 1em; + ; +} + +.minimal-header { + -ms-grid-column: 2; + -ms-grid-column-span: 8; + -ms-grid-row: 1; + grid-column: 2/10; +} + +.minimal-header-name a { + text-decoration: none; +} +.minimal-header-name a:hover, .minimal-header-name a:focus { + text-decoration: underline; +} + +.main-content { + -ms-grid-column: 2; + -ms-grid-column-span: 6; + grid-column: 2/span 6; + -ms-grid-row: 2; + -ms-grid-row-span: 2; + grid-row-start: 2; +} + +.sidebar ul { + padding: 0; +} + +.sidebar dd { + margin-left: 0 !important; +} + +h1 { + padding-top: 33px; +} + +h1 span { + display: block; + font-size: .5em; + margin-bottom: 0.25em; +} + +h2 { + position: relative; +} + +h2 .permalink { + position: absolute; + left: -1em; +} + +h2 .permalink a { + color: var(--grey); + text-decoration: none; +} + +h2 .fragmentlink { + margin-left: -1em; + position: relative; + float: left; +} + +h2 .fragmentlink svg { + visibility: hidden; +} + +h2:hover .fragmentlink svg { + visibility: visible; +} + + +dt div { + font-weight: normal; +} + +.toc-wcag-docs { + padding-left: 1em; +} + +.main-content > .toc-understanding-guideline > li > a { font-weight: bold; -} \ No newline at end of file + margin-top: 2em; + margin-bottom: -.5em; + display: block; + text-decoration: none; +} + +.scquote { + margin: 0; + border: 1px solid var(--line-grey); + padding: 1em; + font-style: normal; +} +.scquote > :first-child { + margin-top: 0; + padding-top: 0; +} + +.minimal-header-container { + background-color: #005a9c; + background-color: var(--w3c-classic); + color: #fff; + color: var(--pure-white); +} +.minimal-header-logo > a { + display: flex; +} +.minimal-header-name > a { + color: inherit; +} + +.note { + background: var(--off-white); + padding: 1em; + border: 1px solid var(--cloudy); +} +.note-title { + font-weight: bold; +} + +/* import inline styles from https://www.w3.org/WAI/drafts/WCAG-understanding-redesign-hack.html */ +.nav a:link { +text-decoration: none; +} +#site-header.minimal-header.with-subtitle { +padding: 1.75em 0 0 0; +} + +.minimal-header-logo img { +margin: 1px 0 1px 0; +} + +#site-header.minimal-header { +margin: 1.2em 0; +align-items: stretch; +} + +#site-header.minimal-header .minimal-header-name, +#site-header.minimal-header .minimal-header-subtitle, +#site-header.minimal-header .minimal-header-link +{ +display: flex; +flex-direction: column; +justify-content: center; +} + +.minimal-header-name { +flex: width 0 0; +} + +.minimal-header-subtitle, +.minimal-header-link { +border-left: 1px solid var(--gold); +padding-left: 8px; +margin-left: 18px; +display: block; +font-size: 80%; +flex: 1 0 0; +} + +.minimal-header-subtitle { +font-style: italic; +} + +.minimal-header-link { +text-decoration: underline !important; +font-weight: normal; +margin-right: 16px; +} + +.nav-container { +margin-bottom: 0; +} + +.nav { +background: none; +} + +.nav-related-info { /* blue bar with the "About:" links */ +background: #005a9c; +color: #fff; +} + +.nav-related-info a { +color: #fff !important; +} + +.nav-page-specific { /* light blue bar with page/section specific navigation/pager */ +margin-bottom: 1.25em; +} + +.nav a:link, .nav a:visited { +color: #036; +color: var(--w3c-blue); +} + +.nav a:hover, .nav a:active { +color: var(--dk-blue); +} + +.nav-hack.sidebar a:hover, +.nav-hack.sidebar a:active +{ +color: var(--dk-blue); +text-decoration: underline; +} + +.standalone-resource-about, .standalone-resource-pager { +margin: 0; +} + +nav.standalone-resource-about { +padding: .5em 0 1.5em 0; +font-style: italic; +} + +.standalone-resource-about dl, .standalone-resource-about dt, .standalone-resource-about dd { +display: inline; +margin: 0; +padding: 0; +} + +.standalone-resource-about dt{ +font-weight: normal; +} + +.standalone-resource-about dl a { +margin: 0; +padding: 0 1em 0 1em; +} + +.standalone-resource-about dd { +border-right: 1px var(--gold) solid; +} + +.standalone-resource-about dd:last-of-type { +border-right: 0; +} + +.standalone-resource-about dd svg { +margin-left: 0.25rem; +vertical-align: middle; +} + +.nav .standalone-resource-pager ul { +align-items: center; +} + +.nav .standalone-resource-pager a, +.nav .standalone-resource-pager span { +margin-left: 0; +margin-right: 1.5em; +} + +.pager-icon { +vertical-align: middle; +padding: 0 0.15em 0.15em 0.15em; +width: 1.65em; +height: 2em; +fill: #005A6A; /* when these are used as actual SVGs */ +} + +.category-icon { +vertical-align: middle; +padding: 0 0.25em 0.25em 0.25em; +width: 2em; +height: 2em; +} + +.standalone-resource-pager { +padding: .7em 0; +} + +.standalone-resource-pager ul { +display: block; +} + +.standalone-resource-pager ul li { +display: inline; +} + +.nav-hack { +font-size: .85em; +/*justify-self: end;*/ +align-self: start; +} +.nav-hack ul { +list-style: none; +padding-left: 0 +} +.nav-hack li:not(:first-child){ +padding-top: 0.4em; +line-height: 1.2; +border-top: 1px solid #BCBCBC; +} +.nav-hack li a { +text-decoration: none; +} +.nav-hack h3 { +margin: 0; +font-size: 1rem; +} + +.nav-hack p { +margin: 0; +} + + +/* skip link */ +.button--skip-link { +background-color: var(--gold) !important; +border-color: var(--gold) !important; +outline-color: currentColor !important; +color: var(--off-black) !important; +font-weight: 600; +font-size: larger; +margin: 0 auto; +position: absolute; +z-index: 20; +left: 0; +right: 0; +top: 0.5em; +width: 10em; +opacity: 1; +transition: transform 0.1875s ease-out, opacity 0.1875s ease-out; +} + +.button--skip-link:not(:focus):not(:hover) { +transform: translateY(-4em); +opacity: 0; +} + +.standalone-resource-navrule { +border:none; +border-top: 1px solid grey +} + +.standalone-resource-about ul, +.standalone-resource-pager ul { +list-style: none; +} + +.nav { +font-size: 95%; +} + +.standalone-resource-about a, +.standalone-resource-pager a, +.standalone-resource-about span, +.standalone-resource-pager span +{ +margin-left:.8em; +margin-right:.8em; +} diff --git a/guidelines/act-mapping.json b/guidelines/act-mapping.json new file mode 100644 index 0000000000..34f95ffe0a --- /dev/null +++ b/guidelines/act-mapping.json @@ -0,0 +1,58 @@ +{ + "act-rules": [{ + "title": "Button has non-empty accessible name", + "permalink": "/standards-guidelines/act/rules/button-non-empty-accessible-name-97a4e1/", + "successCriteria": ["name-role-value"], + "wcagTechniques": [] + }, { + "title": "svg element with explicit role has non-empty accessible name", + "permalink": "/standards-guidelines/act/rules/explicit-SVG-image-non-empty-accessible-name-7d6734/", + "successCriteria": ["non-text-content"], + "wcagTechniques": [] + }, { + "title": "Form field has non-empty accessible name", + "permalink": "/standards-guidelines/act/rules/form-field-non-empty-accessible-name-e086e5/", + "successCriteria": ["name-role-value"], + "wcagTechniques": [] + }, { + "title": "HTML page has lang attribute", + "permalink": "/standards-guidelines/act/rules/html-page-lang-b5c3f8/", + "successCriteria": ["language-of-page"], + "wcagTechniques": ["H57"] + }, { + "title": "HTML page lang attribute has valid language tag", + "permalink": "/standards-guidelines/act/rules/html-page-lang-valid-bf051a/", + "successCriteria": ["language-of-page"], + "wcagTechniques": ["H57"] + }, { + "title": "HTML page lang and xml:lang attributes have matching values", + "permalink": "/standards-guidelines/act/rules/html-page-lang-xml-lang-match-5b7ae0/", + "successCriteria": ["language-of-page"], + "wcagTechniques": [] + }, { + "title": "HTML page has non-empty title", + "permalink": "/standards-guidelines/act/rules/html-page-non-empty-title-2779a5/", + "successCriteria": ["page-titled"], + "wcagTechniques": ["G88", "H25"] + }, { + "title": "Image button has non-empty accessible name", + "permalink": "/standards-guidelines/act/rules/image-button-non-empty-accessible-name-59796f/", + "successCriteria": ["non-text-content", "name-role-value"], + "wcagTechniques": ["G94", "G95"] + }, { + "title": "Image has non-empty accessible name", + "permalink": "/standards-guidelines/act/rules/image-non-empty-accessible-name-23a2a8/", + "successCriteria": ["non-text-content"], + "wcagTechniques": ["G94", "G95"] + }, { + "title": "Link has non-empty accessible name", + "permalink": "/standards-guidelines/act/rules/link-non-empty-accessible-name-c487ae/", + "successCriteria": ["link-purpose-in-context", "link-purpose-link-only", "name-role-value"], + "wcagTechniques": ["G91"] + }, { + "title": "meta viewport allows for zoom", + "permalink": "/standards-guidelines/act/rules/meta-viewport-b4f0c3/", + "successCriteria": ["resize-text", "reflow"], + "wcagTechniques": [] + }] +} diff --git a/guidelines/index.html b/guidelines/index.html index a2d19623d2..bb8e74cf2e 100644 --- a/guidelines/index.html +++ b/guidelines/index.html @@ -3,8 +3,8 @@ - Web Content Accessibility Guidelines (WCAG) 2.2 - + Web Content Accessibility Guidelines (WCAG) 2.1 + @@ -13,20 +13,20 @@
-

Web Content Accessibility Guidelines (WCAG) 2.2 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 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 extends Web Content Accessibility Guidelines 2.1 [[WCAG21]], which was published as a W3C Recommendation June 2018. Content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1. The WG intends that for policies requiring conformance to WCAG 2.0 or WCAG 2.1, WCAG 2.2 can provide an alternate means of conformance. The publication of WCAG 2.2 does not deprecate or supersede WCAG 2.0 or WCAG 2.1. While WCAG 2.0 and WCAG 2.1 remain W3C Recommendations, the W3C advises the use of WCAG 2.2 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.

+

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.

-

This is an Editors' Draft of Web Content Accessibility Guidelines (WCAG) 2.2. WCAG 2.1 is a W3C 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 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).

Introduction

-
+

Background on WCAG 2

-

Web Content Accessibility Guidelines (WCAG) 2.2 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 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 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.

+

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.

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.

@@ -38,7 +38,7 @@

Background on WCAG 2

Where this document refers to WCAG 2 it is intended to mean any and all versions of WCAG that start with 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.

    @@ -49,87 +49,95 @@

    WCAG 2 Layers of Guidance

    Guidelines - Under the principles are guidelines. The 13 guidelines provide the basic goals that authors should work toward in order to make content more accessible to users with different disabilities. The guidelines are not testable, but provide the framework and overall objectives to help authors understand the success criteria and better implement the techniques.

  • -

    Success Criteria - For each guideline, testable success criteria are provided to allow WCAG 2.2 to be used where requirements and conformance testing are necessary such as in design specification, purchasing, regulation, and contractual agreements. In order to meet the needs of different groups and different situations, three levels of conformance are defined: A (lowest), AA, and AAA (highest). Additional information on WCAG levels can be found in Understanding Levels of Conformance.

    +

    Success Criteria - For each guideline, testable success criteria are provided to allow WCAG 2.1 to be used where requirements and conformance testing are necessary such as in design specification, purchasing, regulation, and contractual agreements. In order to meet the needs of different groups and different situations, three levels of conformance are defined: A (lowest), AA, and AAA (highest). Additional information on WCAG levels can be found in Understanding Levels of Conformance.

  • -

    Sufficient and Advisory Techniques - For each of the guidelines and success criteria in the WCAG 2.2 document itself, the working group has also documented a wide variety of techniques. The techniques are informative and fall into two categories: those that are sufficient for meeting the success criteria and those that are advisory. The advisory techniques go beyond what is required by the individual success criteria and allow authors to better address the guidelines. Some advisory techniques address accessibility barriers that are not covered by the testable success criteria. Where common failures are known, these are also documented. See also Sufficient and Advisory Techniques in Understanding WCAG 2.2.

    +

    Sufficient and Advisory Techniques - For each of the guidelines and success criteria in the WCAG 2.1 document itself, the working group has also documented a wide variety of techniques. The techniques are informative and fall into two categories: those that are sufficient for meeting the success criteria and those that are advisory. The advisory techniques go beyond what is required by the individual success criteria and allow authors to better address the guidelines. Some advisory techniques address accessibility barriers that are not covered by the testable success criteria. Where common failures are known, these are also documented. See also Sufficient and Advisory Techniques in Understanding WCAG 2.1.

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.

+

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.

-
-

WCAG 2.2 Supporting Documents

-

The WCAG 2.2 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 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:

+
+

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

    How to Meet WCAG 2.2 - A customizable quick reference to WCAG 2.2 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.1 2.2 and can be filtered in many ways to help authors focus on relevant content.

    +

    How to Meet WCAG 2.1 - A customizable quick reference to WCAG 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 and WCAG 2.1 and can be filtered in many ways to help authors focus on relevant content.

  2. -

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

    +

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

  3. -

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

    +

    Techniques for WCAG 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 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.

-
-

Requirements for WCAG 2.2

-

WCAG 2.2 meets a set of requirements for WCAG 2.2 which, in turn, inherit requirements from previous WCAG 2 versions. 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. 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.

-
-

Comparison with WCAG 2.1

-

WCAG 2.2 was initiated with the goal to continue the work of WCAG 2.1: Improving 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 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 builds on and is backwards compatible with WCAG 2.1, meaning web pages that conform to WCAG 2.2 also conform to WCAG 2.1, which would 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 without losing conformance with previous versions. Authors following more than one version of the guidelines should be aware of the following differences:

-
-

New Features in WCAG 2.2

-

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

-

The following Success Criteria are new in WCAG 2.2:

+
+

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:

+
+

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:

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 has been promoted from Level AA to Level A.

+

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.

-
-

Numbering in WCAG 2.2

-

In order to avoid confusion for implementers for whom backwards compatibility to WCAG 2 versions is important, new success criteria in WCAG 2.2 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, 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 Quick Reference will provide a way to view success criteria grouped by conformance level, along with many other filter and sort options.

+
+

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.

-
-

Conformance to WCAG 2.2

-

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

+
+

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.

-
-

Later Versions of Accessibility Guidelines

-

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

+
+

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.

Perceivable

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

-
+

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.

-
+

Time-based Media

Provide alternatives for time-based media.

@@ -152,7 +160,7 @@

Time-based Media

-
+

Adaptable

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

@@ -170,7 +178,7 @@

Adaptable

-
+

Distinguishable

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

@@ -207,7 +215,7 @@

Distinguishable

Operable

User interface components and navigation must be operable.

-
+

Keyboard Accessible

Make all functionality available from a keyboard.

@@ -221,7 +229,7 @@

Keyboard Accessible

-
+

Enough Time

Provide users enough time to read and use content.

@@ -239,7 +247,7 @@

Enough Time

-
+

Seizures and Physical Reactions

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

@@ -251,7 +259,7 @@

Seizures and Physical Reactions

-
+ -
+

Input Modalities

+

New

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

@@ -299,10 +302,6 @@

Input Modalities

-
- -
-
@@ -310,7 +309,7 @@

Input Modalities

Understandable

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

-
+

Readable

Make text content readable and understandable.

@@ -328,7 +327,7 @@

Readable

-
+

Predictable

Make Web pages appear and operate in predictable ways.

@@ -342,13 +341,9 @@

Predictable

-
- -
-
-
+

Input Assistance

Help users avoid and correct mistakes.

@@ -364,10 +359,6 @@

Input Assistance

-
- -
-
@@ -375,7 +366,7 @@

Input Assistance

Robust

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

-
+

Compatible

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

@@ -391,18 +382,18 @@

Compatible

Conformance

-

This section lists requirements for conformance to WCAG 2.2. 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.

+

This section lists requirements for conformance to WCAG 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.

-
+

Interpreting Normative Requirements

-

The main content of WCAG 2.2 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 main content of WCAG 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]].

Conformance Requirements

-

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

+

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

@@ -471,10 +462,10 @@

Conformance Claims (Optional)

Required Components of a Conformance Claim

-

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

+

Conformance claims are not required. Authors can conform to WCAG 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. -
  2. Guidelines title, version and URI "Web Content Accessibility Guidelines 2.2 at https://www.w3.org/TR/WCAG22/"
    3. +
  3. Guidelines title, version and URI "Web Content Accessibility Guidelines 2.1 at https://www.w3.org/TR/WCAG21/"
  4. Conformance level satisfied: (Level A, AA or AAA)

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

    @@ -495,7 +486,7 @@

    Optional Components of a Conformance Claim

  6. 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.
  7. A list of the specific technologies that are " used but not relied upon."
  8. A list of user agents, including assistive technologies that were used to test the content.
    9. -
  9. A list of specific accessibility characteristics of the content, provided in machine-readable metadata.
    10. +
  10. A list of specific accessibility characteristics of the content, provided in machine-readable metadata.
  11. Information about any additional steps taken that go beyond the success criteria to enhance accessibility.
  12. A machine-readable metadata version of the list of specific technologies that are relied upon.
  13. A machine-readable metadata version of the conformance claim.
    14. @@ -517,7 +508,7 @@

    Statement of Partial Conformance - Third Party Content

    OR

  14. -

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

    +

    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.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.)
      3. @@ -528,7 +519,7 @@

      Statement of Partial Conformance - Third Party Content

      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 at level X if accessibility support existed for the following language(s):"

      +

      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.1 at level X if accessibility support existed for the following language(s):"

@@ -564,8 +555,6 @@

Glossary

-
-
@@ -582,8 +571,6 @@

Glossary

-
-
@@ -592,10 +579,6 @@

Glossary

-
- -
-
@@ -743,16 +726,26 @@

Glossary

Change Log

-

This section shows substantive changes made in WCAG 2.2 since WCAG 2.1. Errata fixes to WCAG 2.1 have also been incorporated into WCAG 2.2.

-

The full commit history to WCAG 2.2 is available.

- +

This section shows changes for WCAG 2.1 since its publication as a W3C Recommendation. These changes are also recorded as errata.

+

Changes since the W3C Recommendation of 05 June 2018:

+
    +
  • In the Status of This Document the paragraph beginning "This document has been reviewed by W3C Members..." appears twice. The first instance of this paragraph has been removed.
    • +
  • In the Introduction, several (but not all) references to "WCAG 2.0" has been changed to "WCAG 2.1".
    • +
  • In the 0.5.2 Numbering in WCAG 2.1, the words "critera" and "ccriteria" have been changed to "criteria".
    • +
  • In 1.4.10 Reflow, the first note had a supernumary "Note" indicator which has been removed.
    • +
  • In 1.4.13 Content on Hover or Focus, the word "dismissable" has been changed to "dismissible".
    • +
  • In 4. Robust, repetition of the word "by" has been removed.
    • +
  • In 5.2.2 Full pages, the third note began with "New" which has been removed.
    • +
  • In 5.3.1 Required Components of a Conformance Claim the editorial note "In WCAG 2.0 this was a dated URI, which may need to be adjusted when this becomes a Rec." has been removed.
    • +
  • In the definition for keyboard interface, the second (of three) note has been changed to be an example of the first note, leaving only two actual notes.
    • +
  • In the definition for technology, the third note has been changed to be an example.
    • +
  • In 7. Input Purposes for User Interface Components, the word "county" has been changed to "country".
    • +
  • In 1.3.4 Orientation, the note referencing "binary display orientation" has been clarified to read "content is not necessarily restricted to landscape or portrait display orientation".
    • +
  • In a note in the definition of accessibility supported, references to "Conformance Criterion" were changed to "Conformance Requirement".
    • +
  • In the definition of relative luminance, the red threshold was updated from 0.03928 to 0.04045.
    • +
  • In 4.1.1 Parsing one note was deleted, and two notes were added, including: "This Success Criterion should be considered as always satisfied for any content using HTML or XML."
    • +
+

The full commit history to WCAG 2.1 is available.

Acknowledgments

diff --git a/guidelines/relative-luminance.html b/guidelines/relative-luminance.html new file mode 100644 index 0000000000..8854c9fca2 --- /dev/null +++ b/guidelines/relative-luminance.html @@ -0,0 +1,362 @@ + + + + + + + MathML version of the relative luminance definition + + +

MathML version of the relative luminance definition

+

The following is a MathML version of the WCAG 2.2 definition of relative luminance. Refer to MathML Software - Browsers for information about browsers and plugins that support MathML which you may need in order to correctly display the information on this page.

+
+
relative luminance
+

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

+
Note
+

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

+
    +
  • +

    If + + + R + + s + R + G + B + + + ≤ + 0.04045 + + then + + R + = + + + R + + s + R + G + B + + + 12.92 + + + else + + R + = + + + ( + + + + R + + s + R + G + B + + + + + 0.055 + + 1.055 + + ) + + 2.4 + + + +

    +
    • +
  • +

    If + + + G + + s + R + G + B + + + ≤ + 0.04045 + + then + + G + = + + + G + + s + R + G + B + + + 12.92 + + + else + + G + = + + + ( + + + + G + + s + R + G + B + + + + + 0.055 + + 1.055 + + ) + + 2.4 + + + +

    +
    • +
  • +

    If + + + B + + s + R + G + B + + + ≤ + 0.04045 + + then + + B + = + + + B + + s + R + G + B + + + 12.92 + + + else + + B + = + + + ( + + + + B + + s + R + G + B + + + + + 0.055 + + 1.055 + + ) + + 2.4 + + + +

    +
    • +

and + + + R + + s + R + G + B + + + , + + G + + s + R + G + B + + + , + + + and + + + + B + + s + R + G + B + + + + are defined as:

    +
  • + + + R + + s + R + G + B + + + = + + + R + + 8 + b + i + t + + + 255 + + +
    • +
  • + + + G + + s + R + G + B + + + = + + + G + + 8 + b + i + t + + + 255 + + +
    • +
  • + + + B + + s + R + G + B + + + = + + + B + + 8 + b + i + t + + + 255 + + +
    • +

(Formula taken from [SRGB].)

+
+
+
Note

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

+ +
Note

Almost all systems used today to view Web content assume sRGB encoding. Unless it + is known that another color space will be used to process and display the content, + authors should evaluate using sRGB colorspace. If using other color spaces, see Understanding Success Criterion 1.4.3. +

+ +
Note

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

+ +
Note

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

+
+
[SRGB]
+
Multimedia systems and equipment - Colour measurement and management - Part 2-1: Colour management - Default RGB colour space - sRGB. IEC. URL: https://webstore.iec.ch/publication/6169
+
+ + diff --git a/guidelines/respec-config.js b/guidelines/respec-config.js index 09acebd9b5..ad0b05237b 100644 --- a/guidelines/respec-config.js +++ b/guidelines/respec-config.js @@ -8,74 +8,71 @@ var respecConfig = { permalinkHide: false, tocIntroductory: true, // specification status (e.g., WD, LC, NOTE, etc.). If in doubt use ED. - specStatus: "ED", + specStatus: "REC", //crEnd: "2012-04-30", //perEnd: "2013-07-23", //publishDate: "2013-08-22", diffTool: "http://www.aptest.com/standards/htmldiff/htmldiff.pl", // the specifications short name, as in https://www.w3.org/TR/short-name/ - shortName: "WCAG22", + shortName: "WCAG21", // if you wish the publication date to be other than today, set this - //publishDate: "2014-12-11", + publishDate: "2023-09-21", copyrightStart: "2020", license: "document", // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date // and its maturity status - //previousPublishDate: "2014-06-12", - //previousMaturity: "WD", - prevRecURI: "https://www.w3.org/TR/WCAG/", + previousPublishDate: "2018-06-05", + previousMaturity: "REC", + prevRecURI: "https://www.w3.org/TR/WCAG20/", //previousDiffURI: "https://www.w3.org/TR/2014/REC-wai-aria-20140320/", // if there a publicly available Editors Draft, this is the link edDraftURI: "https://w3c.github.io/wcag/guidelines/22/", + + // Implementation report + implementationReportURI: "https://www.w3.org/WAI/WCAG21/implementation-report/", // if this is a LCWD, uncomment and set the end of its review period // lcEnd: "2012-02-21", + + // Name of the WG + group: "ag", + github: "w3c/wcag", // editors, add as many as you like // only "name" is required editors: [ { - name: "Chuck Adams", - url: "https://www.oracle.com/", - mailto: "charles.adams@oracle.com", - company: "Oracle", - companyURI: "https://www.oracle.com/", - w3cid: 104852 + name: "Andrew Kirkpatrick", + mailto: "akirkpat@adobe.com", + company: "Adobe", + companyURI: "http://www.adobe.com/", + w3cid: 39770 + }, + { + name: "Joshue O Connor", + mailto: "josh@interaccess.ie", + company: "Invited Expert, InterAccess", + companyURI: "https://interaccess.org/", + w3cid: 41218 }, { name: "Alastair Campbell", - url: "https://www.nomensa.com/", mailto: "acampbell@nomensa.com", company: "Nomensa", companyURI: "https://www.nomensa.com/", w3cid: 44689 }, - { - name: "Rachael Montgomery", - mailto: "rachael@accessiblecommunity.org", - company: "Invited Expert", - w3cid: 90310 - }, { name: "Michael Cooper", - url: 'https://www.w3.org', mailto: "cooper@w3.org", company: "W3C", companyURI: "https://www.w3.org", w3cid: 34017 - }, - { - name: "Andrew Kirkpatrick", - url: "http://www.adobe.com/", - mailto: "akirkpat@adobe.com", - company: "Adobe", - companyURI: "http://www.adobe.com/", - w3cid: 39770 } ], /* @@ -135,7 +132,7 @@ var respecConfig = { ], */ - // errata: 'https://www.w3.org/2010/02/rdfa/errata.html', + errata: 'https://www.w3.org/WAI/WCAG21/errata/', // name of the WG wg: "Accessibility Guidelines Working Group", @@ -154,6 +151,6 @@ var respecConfig = { wgPatentURI: "https://www.w3.org/2004/01/pp-impl/35422/status", maxTocLevel: 4, - postProcess: [addTextSemantics, swapInDefinitions] + postProcess: [postRespec] }; diff --git a/guidelines/sc/20/abbreviations.html b/guidelines/sc/20/abbreviations.html index 69d85cf406..81f0d0be8b 100644 --- a/guidelines/sc/20/abbreviations.html +++ b/guidelines/sc/20/abbreviations.html @@ -1,4 +1,4 @@ -
+

Abbreviations

@@ -7,4 +7,4 @@

Abbreviations

A mechanism for identifying the expanded form or meaning of abbreviations is available.

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/audio-control.html b/guidelines/sc/20/audio-control.html index 7819ff6eef..aaccda2077 100644 --- a/guidelines/sc/20/audio-control.html +++ b/guidelines/sc/20/audio-control.html @@ -1,4 +1,4 @@ -
+

Audio Control

@@ -13,4 +13,4 @@

Audio Control

to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/audio-description-or-media-alternative-prerecorded.html b/guidelines/sc/20/audio-description-or-media-alternative-prerecorded.html index fc1b009b9b..9198805452 100644 --- a/guidelines/sc/20/audio-description-or-media-alternative-prerecorded.html +++ b/guidelines/sc/20/audio-description-or-media-alternative-prerecorded.html @@ -1,4 +1,4 @@ -
+

Audio Description or Media Alternative (Prerecorded)

@@ -8,4 +8,4 @@

Audio Description or Media Alternative (Prerecorded)

video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/audio-description-prerecorded.html b/guidelines/sc/20/audio-description-prerecorded.html index e69ba4569d..d745a2467c 100644 --- a/guidelines/sc/20/audio-description-prerecorded.html +++ b/guidelines/sc/20/audio-description-prerecorded.html @@ -1,4 +1,4 @@ -
+

Audio Description (Prerecorded)

@@ -8,4 +8,4 @@

Audio Description (Prerecorded)

video content in synchronized media.

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/audio-only-and-video-only-prerecorded.html b/guidelines/sc/20/audio-only-and-video-only-prerecorded.html index fea1d134f7..1d00f0b00f 100644 --- a/guidelines/sc/20/audio-only-and-video-only-prerecorded.html +++ b/guidelines/sc/20/audio-only-and-video-only-prerecorded.html @@ -1,4 +1,4 @@ -
+

Audio-only and Video-only (Prerecorded)

@@ -31,4 +31,4 @@

Audio-only and Video-only (Prerecorded)

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/audio-only-live.html b/guidelines/sc/20/audio-only-live.html index 4df1345cb4..f901051281 100644 --- a/guidelines/sc/20/audio-only-live.html +++ b/guidelines/sc/20/audio-only-live.html @@ -1,4 +1,4 @@ -
+

Audio-only (Live)

@@ -8,4 +8,4 @@

Audio-only (Live)

audio-only content is provided.

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/bypass-blocks.html b/guidelines/sc/20/bypass-blocks.html index 4bfedd4f72..5e33982b78 100644 --- a/guidelines/sc/20/bypass-blocks.html +++ b/guidelines/sc/20/bypass-blocks.html @@ -1,4 +1,4 @@ -
+

Bypass Blocks

@@ -7,4 +7,4 @@

Bypass Blocks

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/captions-live.html b/guidelines/sc/20/captions-live.html index a46694ddc8..402d85f656 100644 --- a/guidelines/sc/20/captions-live.html +++ b/guidelines/sc/20/captions-live.html @@ -1,4 +1,4 @@ -
+

Captions (Live)

@@ -8,4 +8,4 @@

Captions (Live)

audio content in synchronized media.

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/captions-prerecorded.html b/guidelines/sc/20/captions-prerecorded.html index eb2f8a4349..0d9206873f 100644 --- a/guidelines/sc/20/captions-prerecorded.html +++ b/guidelines/sc/20/captions-prerecorded.html @@ -1,4 +1,4 @@ -
+

Captions (Prerecorded)

@@ -8,4 +8,4 @@

Captions (Prerecorded)

audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/change-on-request.html b/guidelines/sc/20/change-on-request.html index bfb87593cc..f5d09acf56 100644 --- a/guidelines/sc/20/change-on-request.html +++ b/guidelines/sc/20/change-on-request.html @@ -1,4 +1,4 @@ -
+

Change on Request

@@ -7,4 +7,4 @@

Change on Request

Changes of context are initiated only by user request or a mechanism is available to turn off such changes.

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/consistent-identification.html b/guidelines/sc/20/consistent-identification.html index c1a5e5fcce..789b8d23f6 100644 --- a/guidelines/sc/20/consistent-identification.html +++ b/guidelines/sc/20/consistent-identification.html @@ -1,5 +1,5 @@ -
- +
+

Consistent Identification

AA

@@ -7,4 +7,4 @@

Consistent Identification

Components that have the same functionality within a set of Web pages are identified consistently.

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/consistent-navigation.html b/guidelines/sc/20/consistent-navigation.html index 7a811663da..a1df5d4e8a 100644 --- a/guidelines/sc/20/consistent-navigation.html +++ b/guidelines/sc/20/consistent-navigation.html @@ -1,4 +1,4 @@ -
+

Consistent Navigation

@@ -7,4 +7,4 @@

Consistent Navigation

Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/contrast-enhanced.html b/guidelines/sc/20/contrast-enhanced.html index d25475c349..ba07a2a4db 100644 --- a/guidelines/sc/20/contrast-enhanced.html +++ b/guidelines/sc/20/contrast-enhanced.html @@ -1,4 +1,4 @@ -
+

Contrast (Enhanced)

@@ -38,4 +38,4 @@

Contrast (Enhanced)

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/contrast-minimum.html b/guidelines/sc/20/contrast-minimum.html index 5c022a6e29..744d7f328e 100644 --- a/guidelines/sc/20/contrast-minimum.html +++ b/guidelines/sc/20/contrast-minimum.html @@ -1,4 +1,4 @@ -
+

Contrast (Minimum)

@@ -38,4 +38,4 @@

Contrast (Minimum)

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/error-identification.html b/guidelines/sc/20/error-identification.html index 2f82a6451d..b9549982e5 100644 --- a/guidelines/sc/20/error-identification.html +++ b/guidelines/sc/20/error-identification.html @@ -1,4 +1,4 @@ -
+

Error Identification

@@ -8,4 +8,4 @@

Error Identification

is described to the user in text.

-
\ No newline at end of file +
diff --git a/guidelines/sc/20/error-prevention-all.html b/guidelines/sc/20/error-prevention-all.html index 93729b2349..8fb05bb90e 100644 --- a/guidelines/sc/20/error-prevention-all.html +++ b/guidelines/sc/20/error-prevention-all.html @@ -1,4 +1,4 @@ -
+

Error Prevention (All)

diff --git a/guidelines/sc/20/error-prevention-legal-financial-data.html b/guidelines/sc/20/error-prevention-legal-financial-data.html index 0089039f89..0059cff558 100644 --- a/guidelines/sc/20/error-prevention-legal-financial-data.html +++ b/guidelines/sc/20/error-prevention-legal-financial-data.html @@ -1,4 +1,4 @@ -
+