-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
118 lines (109 loc) · 9.15 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta charset="UTF-8"/>
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"/>
<title>Understanding WCAG 2.2</title>
<link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/2016/base"/>
<link rel="stylesheet" type="text/css" href="understanding.css"/>
</head>
<body>
<div class="head">
<a href="https://www.w3.org/" class="logo">
<img alt="W3C" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" width="72" height="48"/>
</a>
<h1 id="title" class="title p-name">Understanding WCAG 2.2</h1>
<h2>Updated <span class="generate-date"/></h2>
<ul id="masthead">
<li><strong>Authors:</strong> <a href="https://www.w3.org/WAI/GL/">Accessibility Guidelines Working Group</a></li>
<li><strong>Editors:</strong> <a href="mailto:[email protected]">Alastair Campbell, Michael Cooper, Andrew Kirkpatrick</a></li>
<li><strong>Editors' Draft:</strong> <a href="https://w3c.github.io/wcag/understanding/">https://w3c.github.io/wcag/understanding/</a></li>
<li><strong>Official Version:</strong> <a href="https://www.w3.org/WAI/WCAG22/Understanding/">https://www.w3.org/WAI/WCAG22/Understanding/</a></li>
<li><strong>File Issues</strong>: <a href="https://github.com/w3c/wcag/issues/">https://github.com/w3c/wcag/issues/</a></li>
</ul>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2017-<span class="generate-year">2018</span>
<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>).
<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
<a rel="license" href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
rules apply.
</p>
<hr title="Separator for header"/>
</div>
<section id="abstract">
<h2>Abstract</h2>
<p>Understanding WCAG 2.2 is a guide to understanding and using <a href="https://www.w3.org/TR/WCAG22/">Web Content Accessibility Guidelines (WCAG) 2.2</a> [[WCAG22]]. It is part of a set of documents that support WCAG 2.2. Please note that the contents of this document are informative (they provide guidance), and not normative (they do not set requirements for conforming to WCAG 2.2). See <a href="https://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG) Overview</a> for an introduction to WCAG, supporting technical documents, and educational material.</p>
</section>
<section id="sotd">
<h2>Status of This Document</h2>
<p>This is the official version of "Understanding WCAG 2.2", and is referenced by <a href="https://www.w3.org/TR/WCAG22/">Web Content Accessibility Guidelines 2.2</a>. This resource is maintained as needed to update interpretive guidance and reference techniques to meet the guidelines.</p>
<p>To comment, <a href="https://github.com/w3c/wcag/issues/new">file an issue in the <abbr title="World Wide Web Consortium">W3C</abbr> WCAG GitHub repository</a>. 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 <a href="mailto:[email protected]?subject=WCAG%202.2%20public%20comment">[email protected]</a> (<a href="https://lists.w3.org/Archives/Public/public-agwg-comments/">comment archive</a>). </p>
</section>
<section class="informative introductory" id="intro">
<h2>Introduction</h2>
<p>Understanding WCAG 2.2 is a guide to understanding and using <a href="https://www.w3.org/TR/WCAG22/">Web Content Accessibility Guidelines 2.2</a> [[WCAG22]] Although the normative definition and requirements for WCAG 2.2 can all be found in the WCAG 2.2 document itself, the concepts and provisions may be new to some people. Understanding WCAG 2.2 provides a non-normative extended commentary on each guideline and each Success Criterion to help readers better understand the intent and how the guidelines and Success Criteria work together. It also provides examples of techniques or combinations of techniques that the Working Group has identified as being sufficient to meet each Success Criterion. Links are then provided to write-ups for each of the techniques.</p>
<section>
<h3>Relationship to Understanding WCAG 2.0</h3>
<p><a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/">Understanding WCAG 2.0</a> [[UNDERSTANDING-WCAG20]] is a substantial resource to support <a href="https://www.w3.org/TR/WCAG20/">Web Content Accessibility Guidelines 2.0</a> [[WCAG20]]. Understanding WCAG 2.2 is a parallel resource that supports the new success criteria in WCAG 2.2. At this stage, it only includes content related to new features of WCAG 2.0. Future versions <em>may</em> include content relevant to WCAG 2.0, depending on how WCAG 2.2 evolves and what structure is determined to provide optimal support.</p>
<p>Unlike Understanding WCAG 2.0, this document has not been published as a Technical Report. This change reduces the formality of the document and increases the ability of the Accessibility Guidelines Working Group to maintain the content and optimize the structure. The Working Group considers the content to be authoritative. If feedback indicates the need, the document could be published as a Technical Report in the future.</p>
</section>
<section>
<h3>Structure of Understanding WCAG 2.2</h3>
<p>This is not an introductory document. It is a detailed technical description of the guidelines and their Success Criteria. See <a href="https://www.w3.org/WAI/intro/wcag">Web Content Accessibility Guidelines (WCAG) Overview</a> for an introduction to WCAG, supporting technical documents, and educational material. </p>
<p>Understanding WCAG 2.2 is organized by guideline. There is an <em>Understanding Guideline X.X</em> section for each guideline. The intent and any advisory techniques that are related to the guideline but not specifically related to any of its Success Criteria are listed there as well.</p>
<p>The <em>Understanding Guidelines X.X</em> section is then followed by a <em>Understanding Success Criterion X.X.X</em> section for each Success Criterion of that guideline. These sections each contain:</p>
<ul>
<li>
<p>The Success Criterion as it appears in WCAG 2.2</p>
</li>
<li>
<p>Intent of the Success Criterion</p>
</li>
<li>
<p>Benefits (how the Success Criterion helps people with disabilities)</p>
</li>
<li>
<p>Examples</p>
</li>
<li>
<p> Related Resources </p>
</li>
<li>
<p>Techniques or combinations of techniques that are sufficient to meet the guidelines</p>
</li>
<li>
<p>Failures of this Success Criterion</p>
</li>
<li>
<p>Additional advisory techniques that go beyond what is required to meet the Success Criterion but can be used to make some or all types of content more accessible. Use of advisory techniques does not impact the level of conformance claimed. </p>
</li>
<li>
<p>Key terms for this Success Criterion (taken from the WCAG 2.2 Glossary)</p>
</li>
</ul>
<p>Links are provided from each Guideline in WCAG 2.2 directly to each <em>Understanding Guideline X.X</em> in this document. Similarly, there is a link from each Success Criterion in WCAG 2.2 to the <em>Understanding Success Criterion X.X.X</em> section in this document. </p>
</section>
<section>
<h3>Techniques for WCAG 2.2</h3>
<p>Techniques specific to WCAG 2.2 are added to the the techniques for WCAG 2.0, it is one set. The <a href="../techniques/#changelog">Techniques change log</a> lists the new techniques added since WCAG 2.2 was published.</p>
</section>
</section>
<div data-include="toc.html" data-include-replace="true"></div>
<section id="changelog">
<h2>Understanding documents change Log</h2>
<p>A list of significantly updated Understanding documents since WCAG 2.2 was published:</p>
<ol>
<li><time datetime="2019-01-17">Jan 18th 2019</time>: Updated <a href="./non-text-contrast">Understanding Non-text contrast</a>, based on the changes from <a href="https://github.com/w3c/wcag/pull/550">Pull request 550</a>.</li>
</ol>
<p>For a more detailed view of recent changes to the informative documents see the <a href="https://github.com/w3c/wcag/commits/master">github updates</a>.</p>
</section>
<div data-include="../acknowledgements.html" data-include-replace="true">
<p>Acknowledgements</p>
</div>
</body>
</html>