-
Notifications
You must be signed in to change notification settings - Fork 229
/
index.html
735 lines (498 loc) · 55.3 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
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta charset="UTF-8" />
<title>Web Content Accessibility Guidelines (WCAG) 2.2</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
<script src="../script/wcag.js" class="remove"></script>
<script src="respec-config.js" class="remove"></script>
<script src="../biblio.js" class="remove"></script>
<link rel="stylesheet" type="text/css" href="../css/sources.css" class="remove" />
<link rel="stylesheet" type="text/css" href="guidelines.css" />
</head>
<body>
<section id="abstract">
<p>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.</p>
<p>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 <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG) Overview</a> for an introduction and links to WCAG technical and educational material.</p>
<p>WCAG 2.2 extends <a href="https://www.w3.org/TR/WCAG21/">Web Content Accessibility Guidelines 2.1</a> [[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.</p>
</section>
<section id="sotd">
<p>This is an Editors' Draft of Web Content Accessibility Guidelines (WCAG) 2.2. <a href="https://www.w3.org/TR/WCAG21/">WCAG 2.1 is a W3C Recommendation</a>.</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:public-agwg-comments@w3.org?subject=WCAG%202.2%20public%20comment">public-agwg-comments@w3.org</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>
<section>
<h3>Background on WCAG 2</h3>
<p>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.</p>
<p>WCAG 2.2 is developed through the <a href="https://www.w3.org/WAI/standards-guidelines/w3c-process/">W3C process</a> 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 <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG) Overview</a>.</p>
<p>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 <a href="https://www.w3.org/WAI/standards-guidelines/wcag/#supplement">improving inclusion for people with disabilities, including learning and cognitive disabilities, people with low-vision, and more</a>.</p>
<p>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:</p>
<ul>
<li><strong><a href="https://www.w3.org/WAI/fundamentals/components/">Essential Components of Web Accessibility</a></strong></li>
<li><strong><a href="https://www.w3.org/WAI/standards-guidelines/uaag/">User Agent Accessibility Guidelines (UAAG) Overview</a></strong></li>
<li><strong><a href="https://www.w3.org/WAI/standards-guidelines/atag/">Authoring Tool Accessibility Guidelines (ATAG) Overview</a></strong></li>
</ul>
<p>Where this document refers to <q>WCAG 2</q> it is intended to mean any and all versions of WCAG that start with 2.</p>
</section>
<section>
<h3>WCAG 2 Layers of Guidance</h3>
<p>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 <em>principles</em>, general <em>guidelines</em>, testable <em>success criteria</em> and a rich collection of <em>sufficient techniques</em>, <em>advisory techniques</em>, and <em>documented common failures</em> with examples, resource links and code.</p>
<ul>
<li>
<p><strong>Principles</strong> - At the top are four principles that provide the foundation for Web accessibility: <em>perceivable, operable, understandable, and robust</em>. See also <a href="https://www.w3.org/WAI/WCAG21/Understanding/intro#understanding-the-four-principles-of-accessibility">Understanding the Four Principles of Accessibility</a>.</p>
</li>
<li>
<p><strong>Guidelines</strong> - 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.</p>
</li>
<li>
<p><strong>Success Criteria</strong> - 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 <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance#levels">Understanding Levels of Conformance</a>.</p>
</li>
<li>
<p><strong>Sufficient and Advisory Techniques</strong> - For each of the <em>guidelines</em> and <em>success criteria</em> in the WCAG 2.2 document itself, the working group has also documented a wide variety of <em>techniques</em>. The techniques are informative and fall into two categories: those that are <em>sufficient</em> for meeting the success criteria and those that are <em>advisory</em>. 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 <a href="https://www.w3.org/WAI/WCAG21/Understanding/understanding-techniques">Sufficient and Advisory Techniques in Understanding WCAG 2.2</a>.</p>
</li>
</ul>
<p>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.</p>
<p>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. <a href="https://www.w3.org/WAI/WCAG21/Understanding/understanding-metadata">Metadata</a> may assist users in finding content most suitable for their needs. </p>
</section>
<section>
<h3>WCAG 2.2 Supporting Documents</h3>
<p>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: </p>
<ol class="enumar">
<li>
<p><strong><a href="https://www.w3.org/WAI/WCAG21/quickref/">How to Meet WCAG 2.2</a></strong> - 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.</p>
</li>
<li>
<p><strong><a href="https://www.w3.org/WAI/WCAG21/Understanding/">Understanding WCAG 2.2</a></strong> - 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.</p>
</li>
<li>
<p><strong><a href="https://www.w3.org/WAI/WCAG21/Techniques/">Techniques for WCAG 2.2</a></strong> - A collection of techniques and common failures, each in a separate document that includes a description, examples, code and tests.</p>
</li>
<li>
<p><strong><a href="https://www.w3.org/WAI/standards-guidelines/wcag/docs/">The WCAG Documents</a></strong> - A diagram and description of how the technical documents are related and linked.</p>
</li>
</ol>
<p>See <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG) Overview</a> 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 <a href="https://www.w3.org/WAI/Resources/Overview">WAI Resources</a>.</p>
</section>
<section>
<h3>Requirements for WCAG 2.2</h3>
<p>WCAG 2.2 meets a set of <a href="https://w3c.github.io/wcag/requirements/22/">requirements for WCAG 2.2</a> 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.</p>
</section>
<section>
<h3>Comparison with WCAG 2.1</h3>
<p>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.</p>
<p>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:</p>
<section>
<h4>New Features in WCAG 2.2</h4>
<p>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.</p>
<p>The following Success Criteria are new in WCAG 2.2:</p>
<ul>
<li><a href="#focus-visible-enhanced">Focus visible (enhanced)</a></li>
</ul>
<p>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.</p>
</section>
<section>
<h4>Numbering in WCAG 2.2</h4>
<p>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 <a href="https://www.w3.org/WAI/WCAG21/quickref/">WCAG 2.2 Quick Reference</a> will provide a way to view success criteria grouped by conformance level, along with many other filter and sort options.</p>
</section>
<section>
<h4>Conformance to WCAG 2.2</h4>
<p>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. </p>
</section>
</section>
<section>
<h3>Later Versions of Accessibility Guidelines</h3>
<p>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. </p>
</section>
</section>
<section class="principle" id="perceivable">
<h2> Perceivable </h2>
<p>Information and user interface components must be presentable to users in ways they can perceive.</p>
<section class="guideline">
<h3>Text Alternatives</h3>
<p>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.</p>
<section data-include="sc/20/non-text-content.html" data-include-replace="true"></section>
</section>
<section class="guideline">
<h3>Time-based Media</h3>
<p>Provide alternatives for time-based media.</p>
<section data-include="sc/20/audio-only-and-video-only-prerecorded.html" data-include-replace="true"></section>
<section data-include="sc/20/captions-prerecorded.html" data-include-replace="true"></section>
<section data-include="sc/20/audio-description-or-media-alternative-prerecorded.html" data-include-replace="true"></section>
<section data-include="sc/20/captions-live.html" data-include-replace="true"></section>
<section data-include="sc/20/audio-description-prerecorded.html" data-include-replace="true"></section>
<section data-include="sc/20/sign-language-prerecorded.html" data-include-replace="true"></section>
<section data-include="sc/20/extended-audio-description-prerecorded.html" data-include-replace="true"></section>
<section data-include="sc/20/media-alternative-prerecorded.html" data-include-replace="true"></section>
<section data-include="sc/20/audio-only-live.html" data-include-replace="true"></section>
</section>
<section class="guideline">
<h3>Adaptable</h3>
<p>Create content that can be presented in different ways (for example simpler layout) without losing information or structure.</p>
<section data-include="sc/20/info-and-relationships.html" data-include-replace="true"></section>
<section data-include="sc/20/meaningful-sequence.html" data-include-replace="true"></section>
<section data-include="sc/20/sensory-characteristics.html" data-include-replace="true"></section>
<section data-include="sc/21/orientation.html" data-include-replace="true"></section>
<section data-include="sc/21/identify-input-purpose.html" data-include-replace="true"></section>
<section data-include="sc/21/identify-purpose.html" data-include-replace="true"></section>
</section>
<section class="guideline">
<h3>Distinguishable</h3>
<p>Make it easier for users to see and hear content including separating foreground from background.</p>
<section data-include="sc/20/use-of-color.html" data-include-replace="true"></section>
<section data-include="sc/20/audio-control.html" data-include-replace="true"></section>
<section data-include="sc/20/contrast-minimum.html" data-include-replace="true"></section>
<section data-include="sc/20/resize-text.html" data-include-replace="true"></section>
<section data-include="sc/20/images-of-text.html" data-include-replace="true"></section>
<section data-include="sc/20/contrast-enhanced.html" data-include-replace="true"></section>
<section data-include="sc/20/low-or-no-background-audio.html" data-include-replace="true"></section>
<section data-include="sc/20/visual-presentation.html" data-include-replace="true"></section>
<section data-include="sc/20/images-of-text-no-exception.html" data-include-replace="true"></section>
<section data-include="sc/21/reflow.html" data-include-replace="true"></section>
<section data-include="sc/21/non-text-contrast.html" data-include-replace="true"></section>
<section data-include="sc/21/text-spacing.html" data-include-replace="true"></section>
<section data-include="sc/21/content-on-hover-or-focus.html" data-include-replace="true"></section>
</section>
</section>
<section class="principle" id="operable">
<h2>Operable </h2>
<p>User interface components and navigation must be operable.</p>
<section class="guideline">
<h3>Keyboard Accessible</h3>
<p>Make all functionality available from a keyboard.</p>
<section data-include="sc/20/keyboard.html" data-include-replace="true"></section>
<section data-include="sc/20/no-keyboard-trap.html" data-include-replace="true"></section>
<section data-include="sc/20/keyboard-no-exception.html" data-include-replace="true"></section>
<section data-include="sc/21/character-key-shortcuts.html" data-include-replace="true"></section>
</section>
<section class="guideline">
<h3>Enough Time</h3>
<p>Provide users enough time to read and use content.</p>
<section data-include="sc/20/timing-adjustable.html" data-include-replace="true"></section>
<section data-include="sc/20/pause-stop-hide.html" data-include-replace="true"></section>
<section data-include="sc/20/no-timing.html" data-include-replace="true"></section>
<section data-include="sc/20/interruptions.html" data-include-replace="true"></section>
<section data-include="sc/20/re-authenticating.html" data-include-replace="true"></section>
<section data-include="sc/21/timeouts.html" data-include-replace="true"></section>
</section>
<section class="guideline">
<h3>Seizures and Physical Reactions</h3>
<p>Do not design content in a way that is known to cause seizures or physical reactions.</p>
<section data-include="sc/20/three-flashes-or-below-threshold.html" data-include-replace="true"></section>
<section data-include="sc/20/three-flashes.html" data-include-replace="true"></section>
<section data-include="sc/21/animation-from-interactions.html" data-include-replace="true"></section>
</section>
<section class="guideline">
<h3>Navigable</h3>
<p>Provide ways to help users navigate, find content, and determine where they are.</p>
<section data-include="sc/20/bypass-blocks.html" data-include-replace="true"></section>
<section data-include="sc/20/page-titled.html" data-include-replace="true"></section>
<section data-include="sc/20/focus-order.html" data-include-replace="true"></section>
<section data-include="sc/20/link-purpose-in-context.html" data-include-replace="true"></section>
<section data-include="sc/20/multiple-ways.html" data-include-replace="true"></section>
<section data-include="sc/20/headings-and-labels.html" data-include-replace="true"></section>
<section data-include="sc/22/focus-visible.html" data-include-replace="true"></section>
<section data-include="sc/20/location.html" data-include-replace="true"></section>
<section data-include="sc/20/link-purpose-link-only.html" data-include-replace="true"></section>
<section data-include="sc/20/section-headings.html" data-include-replace="true"></section>
<section data-include="sc/22/focus-visible-enhanced.html" data-include-replace="true"></section>
</section>
<section class="guideline">
<h3>Input Modalities</h3>
<p>Make it easier for users to operate functionality through various inputs beyond keyboard.</p>
<section data-include="sc/21/pointer-gestures.html" data-include-replace="true"></section>
<section data-include="sc/21/pointer-cancellation.html" data-include-replace="true"></section>
<section data-include="sc/21/label-in-name.html" data-include-replace="true"></section>
<section data-include="sc/21/motion-actuation.html" data-include-replace="true"></section>
<section data-include="sc/21/target-size.html" data-include-replace="true"></section>
<section data-include="sc/21/concurrent-input-mechanisms.html" data-include-replace="true"></section>
<section data-include="sc/22/dragging.html" data-include-replace="true"></section>
</section>
</section>
<section class="principle" id="understandable">
<h2> Understandable </h2>
<p>Information and the operation of the user interface must be understandable.</p>
<section class="guideline">
<h3>Readable</h3>
<p>Make text content readable and understandable.</p>
<section data-include="sc/20/language-of-page.html" data-include-replace="true"></section>
<section data-include="sc/20/language-of-parts.html" data-include-replace="true"></section>
<section data-include="sc/20/unusual-words.html" data-include-replace="true"></section>
<section data-include="sc/20/abbreviations.html" data-include-replace="true"></section>
<section data-include="sc/20/reading-level.html" data-include-replace="true"></section>
<section data-include="sc/20/pronunciation.html" data-include-replace="true"></section>
</section>
<section class="guideline">
<h3>Predictable</h3>
<p>Make Web pages appear and operate in predictable ways.</p>
<section data-include="sc/20/on-focus.html" data-include-replace="true"></section>
<section data-include="sc/20/on-input.html" data-include-replace="true"></section>
<section data-include="sc/20/consistent-navigation.html" data-include-replace="true"></section>
<section data-include="sc/20/consistent-identification.html" data-include-replace="true"></section>
<section data-include="sc/20/change-on-request.html" data-include-replace="true"></section>
<section data-include="sc/22/findable-help.html" data-include-replace="true"></section>
</section>
<section class="guideline">
<h3>Input Assistance</h3>
<p>Help users avoid and correct mistakes.</p>
<section data-include="sc/20/error-identification.html" data-include-replace="true"></section>
<section data-include="sc/20/labels-or-instructions.html" data-include-replace="true"></section>
<section data-include="sc/20/error-suggestion.html" data-include-replace="true"></section>
<section data-include="sc/20/error-prevention-legal-financial-data.html" data-include-replace="true"></section>
<section data-include="sc/20/help.html" data-include-replace="true"></section>
<section data-include="sc/20/error-prevention-all.html" data-include-replace="true"></section>
<section data-include="sc/22/accessible-authentication.html" data-include-replace="true"></section>
</section>
</section>
<section class="principle" id="robust">
<h2> Robust </h2>
<p>Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.</p>
<section class="guideline">
<h3>Compatible</h3>
<p>Maximize compatibility with current and future user agents, including assistive technologies.</p>
<section data-include="sc/20/parsing.html" data-include-replace="true"></section>
<section data-include="sc/20/name-role-value.html" data-include-replace="true"></section>
<section data-include="sc/21/status-messages.html" data-include-replace="true"></section>
</section>
</section>
<section id="conformance">
<h1>Conformance</h1>
<p>This section lists requirements for <a>conformance</a> 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 <a>accessibility supported</a>, since only accessibility-supported ways of using technologies can be <a>relied upon</a> for conformance. <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance">Understanding Conformance</a> includes further explanation of the accessibility-supported concept.</p>
<section>
<h2>Interpreting Normative Requirements</h2>
<p>The main content of WCAG 2.2 is <a>normative</a> and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as "non-normative", diagrams, examples, and notes are <a>informative</a> (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim.</p>
<p>The key words MAY, MUST, MUST NOT, NOT RECOMMENDED, RECOMMENDED, SHOULD, and SHOULD NOT are to be interpreted as described in [[RFC2119]].</p>
</section>
<section id="conformance-reqs">
<h2>Conformance Requirements</h2>
<p>In order for a Web page to conform to WCAG 2.2, all of the following conformance requirements must be satisfied:</p>
<section id="cc1">
<h3>Conformance Level</h3>
<p>One of the following levels of conformance is met in full.</p>
<ul>
<li>For Level A conformance (the minimum level of conformance), the <a>Web page</a>
<a>satisfies</a> all the Level A Success Criteria, or a <a>conforming alternate version</a> is provided.</li>
<li>For Level AA conformance, the Web page satisfies all the Level A and Level AA Success Criteria, or a Level AA conforming alternate version is provided.</li>
<li>For Level AAA conformance, the Web page satisfies all the Level A, Level AA and Level AAA Success Criteria, or a Level AAA conforming alternate version is provided.</li>
</ul>
<p class="note">Although conformance can only be achieved at the stated levels, authors are encouraged to report (in their claim) any progress toward meeting success criteria from all levels beyond the achieved level of conformance.</p>
<p class="note">It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content.</p>
</section>
<section id="cc2">
<h3>Full pages</h3>
<p><a>Conformance</a> (and conformance level) is for full <a>Web page(s)</a> only, and cannot be achieved if part of a Web page is excluded.</p>
<p class="note">For the purpose of determining conformance, alternatives to part of a page's content are considered part of the page when the alternatives can be obtained directly from the page, e.g., a long description or an alternative presentation of a video.</p>
<p class="note">Authors of Web pages that cannot conform due to content outside of the author's control may consider a <a href="#conformance-partial">Statement of Partial Conformance</a>.</p>
<p class="note">A full page includes each variation of the page that is automatically presented by the page for various screen sizes (e.g. variations in a responsive Web page). Each of these variations needs to conform (or needs to have a conforming alternate version) in order for the entire page to conform.</p>
</section>
<section id="cc3">
<h3>Complete processes</h3>
<p>When a <a>Web page</a> is one of a series of Web pages presenting a <a>process</a> (i.e., a sequence of steps that need to be completed in order to accomplish an activity), all Web pages in the process conform at the specified level or better. (Conformance is not possible at a particular level if any page in the process does not conform at that level or better.)</p>
<p class="example">An online store has a series of pages that are used to select and purchase products. All pages in the series from start to finish (checkout) conform in order for any page that is part of the process to conform.</p>
</section>
<section id="cc4">
<h3>Only Accessibility-Supported Ways of Using Technologies</h3>
<p>Only <a>accessibility-supported</a> ways of using <a>technologies</a> are <a>relied upon</a> to satisfy the success criteria. Any information or functionality that is provided in a way that is not accessibility supported is also available in a way that is accessibility supported. (See <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance#accessibility-support">Understanding accessibility support</a>.)</p>
</section>
<section id="cc5">
<h3>Non-Interference</h3>
<p>If <a> technologies </a> are used in a way that is not <a>accessibility supported</a>, or if they are used in a non-conforming way, then they do not block the ability of users to access the rest of the page. In addition, the <a>Web page</a> as a whole continues to meet the conformance requirements under each of the following conditions:</p>
<ol>
<li>when any technology that is not <a>relied upon</a> is turned on in a user agent,</li>
<li>when any technology that is not relied upon is turned off in a user agent, and</li>
<li>when any technology that is not relied upon is not supported by a user agent</li>
</ol>
<p>In addition, the following success criteria apply to all content on the page, including content that is not otherwise relied upon to meet conformance, because failure to meet them could interfere with any use of the page:</p>
<ul>
<li><strong>1.4.2 - Audio Control</strong>,</li>
<li><strong>2.1.2 - No Keyboard Trap</strong>,</li>
<li><strong>2.3.1 - Three Flashes or Below Threshold</strong>, and</li>
<li><strong>2.2.2 - Pause, Stop, Hide</strong>.</li>
</ul>
<p class="note">If a page cannot conform (for example, a conformance test page or an example page), it cannot be included in the scope of conformance or in a conformance claim.</p>
<p>For more information, including examples, see <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance#conformance-requirements">Understanding Conformance Requirements</a>.</p>
</section>
</section>
<section id="conformance-claims">
<h2>Conformance Claims (Optional) </h2>
<p>Conformance is defined only for <a>Web pages</a>. However, a conformance claim may be made to cover one page, a series of pages, or multiple related Web pages.</p>
<section id="conformance-required">
<h3>Required Components of a Conformance Claim</h3>
<p>Conformance claims are <strong>not required</strong>. Authors can conform to WCAG 2.2 without making a claim. However, if a conformance claim is made, then the conformance claim <strong>must</strong> include the following information:</p>
<ol>
<li><strong>Date</strong> of the claim</li>
<li><strong>Guidelines title, version and URI </strong> "Web Content Accessibility Guidelines 2.2 at <a href="https://www.w3.org/TR/WCAG22/">https://www.w3.org/TR/WCAG22/</a>"</li>
<li><strong>Conformance level</strong> satisfied: (Level A, AA or AAA)</li>
<li>
<p><strong>A concise description of the Web pages</strong>, such as a list of URIs for which the claim is made, including whether subdomains are included in the claim.</p>
<p class="note">The Web pages may be described by list or by an expression that describes all of the URIs included in the claim.</p>
<p class="note">Web-based products that do not have a URI prior to installation on the customer's Web site may have a statement that the product would conform when installed.</p>
</li>
<li>A list of the <strong>
<a>Web content technologies</a>
<a>relied upon</a></strong>.</li>
</ol>
<p class="note">If a conformance logo is used, it would constitute a claim and must be accompanied by the required components of a conformance claim listed above.</p>
</section>
<section id="conformance-optional">
<h3>Optional Components of a Conformance Claim </h3>
<p>In addition to the required components of a conformance claim above, consider providing additional information to assist users. Recommended additional information includes:</p>
<ul>
<li>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.</li>
<li>A list of the specific technologies that are " <em>used but not <a>relied upon</a></em>."</li>
<li>A list of user agents, including assistive technologies that were used to test the content.</li>
<li>A list of specific accessibility characteristics of the content, provided in machine-readable metadata.</li>
<li>Information about any additional steps taken that go beyond the success criteria to enhance accessibility.</li>
<li>A machine-readable metadata version of the list of specific technologies that are <a>relied upon</a>.</li>
<li>A machine-readable metadata version of the conformance claim.</li>
</ul>
<p class="note">Refer to <a href="https://www.w3.org/WAI/WCAG21/Understanding/conformance#conformance-claims">Understanding Conformance Claims</a> for more information and example conformance claims.</p>
<p class="note">Refer to <a href="https://www.w3.org/WAI/WCAG21/Understanding/understanding-metadata">Understanding Metadata</a> for more information about the use of metadata in conformance claims.</p>
</section>
</section>
<section id="conformance-partial">
<h2>Statement of Partial Conformance - Third Party Content</h2>
<p>Sometimes, Web pages are created that will later have additional content added to them. For example, an email program, a blog, an article that allows users to add comments, or applications supporting user-contributed content. Another example would be a page, such as a portal or news site, composed of content aggregated from multiple contributors, or sites that automatically insert content from other sources over time, such as when advertisements are inserted dynamically.</p>
<p>In these cases, it is not possible to know at the time of original posting what the uncontrolled content of the pages will be. It is important to note that the uncontrolled content can affect the accessibility of the controlled content as well. Two options are available:</p>
<ol>
<li>
<p>A determination of conformance can be made based on best knowledge. If a page of this type is monitored and repaired (non-conforming content is removed or brought into conformance) within two business days, then a determination or claim of conformance can be made since, except for errors in externally contributed content which are corrected or removed when encountered, the page conforms. No conformance claim can be made if it is not possible to monitor or correct non-conforming content;</p>
<p><strong>OR</strong></p>
</li>
<li>
<p>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:</p>
<ol>
<li>It is not content that is under the author's control.</li>
<li>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.)</li>
</ol>
</li>
</ol>
</section>
<section id="conformance-partial-lang">
<h2>Statement of Partial Conformance - Language</h2>
<p>A "statement of partial conformance due to language" may be made when the page does not conform, but would conform if <a>accessibility support</a> 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):"</p>
</section>
</section>
<section id="glossary">
<h1>Glossary</h1>
<dl id="terms">
<dt data-include="terms/20/abbreviation.html" data-include-replace="true"></dt>
<dt data-include="terms/20/accessibility-supported.html" data-include-replace="true"></dt>
<dt data-include="terms/20/alternative-for-time-based-media.html" data-include-replace="true"></dt>
<dt data-include="terms/20/ambiguous-to-users-in-general.html" data-include-replace="true"></dt>
<dt data-include="terms/20/ascii-art.html" data-include-replace="true"></dt>
<dt data-include="terms/20/assistive-technology.html" data-include-replace="true"></dt>
<dt data-include="terms/20/audio.html" data-include-replace="true"></dt>
<dt data-include="terms/20/audio-description.html" data-include-replace="true"></dt>
<dt data-include="terms/20/audio-only.html" data-include-replace="true"></dt>
<dt data-include="terms/20/blinking.html" data-include-replace="true"></dt>
<dt data-include="terms/20/blocks-of-text.html" data-include-replace="true"></dt>
<dt data-include="terms/20/captcha.html" data-include-replace="true"></dt>
<dt data-include="terms/20/captions.html" data-include-replace="true"></dt>
<dt data-include="terms/20/changes-of-context.html" data-include-replace="true"></dt>
<dt data-include="terms/22/cognitive-function-test.html" data-include-replace="true"></dt>
<dt data-include="terms/20/conformance.html" data-include-replace="true"></dt>
<dt data-include="terms/20/conforming-alternate-version.html" data-include-replace="true"></dt>
<dt data-include="terms/20/content.html" data-include-replace="true"></dt>
<dt data-include="terms/20/context-sensitive-help.html" data-include-replace="true"></dt>
<dt data-include="terms/20/contrast-ratio.html" data-include-replace="true"></dt>
<dt data-include="terms/20/correct-reading-sequence.html" data-include-replace="true"></dt>
<dt data-include="terms/21/css-pixel.html" data-include-replace="true"></dt>
<dt data-include="terms/21/down-event.html" data-include-replace="true"></dt>
<dt data-include="terms/22/dragging-movement.html" data-include-replace="true"></dt>
<dt data-include="terms/20/emergency.html" data-include-replace="true"></dt>
<dt data-include="terms/20/essential.html" data-include-replace="true"></dt>
<dt data-include="terms/20/extended-audio-description.html" data-include-replace="true"></dt>
<dt data-include="terms/20/flash.html" data-include-replace="true"></dt>
<dt data-include="terms/22/focus.html" data-include-replace="true"></dt>
<dt data-include="terms/22/focus-indication-area.html" data-include-replace="true"></dt>
<dt data-include="terms/20/functionality.html" data-include-replace="true"></dt>
<dt data-include="terms/20/general-flash-and-red-flash-thresholds.html" data-include-replace="true"></dt>
<dt data-include="terms/20/human-language.html" data-include-replace="true"></dt>
<dt data-include="terms/20/idiom.html" data-include-replace="true"></dt>
<dt data-include="terms/20/image-of-text.html" data-include-replace="true"></dt>
<dt data-include="terms/20/informative.html" data-include-replace="true"></dt>
<dt data-include="terms/20/input-error.html" data-include-replace="true"></dt>
<dt data-include="terms/20/jargon.html" data-include-replace="true"></dt>
<dt data-include="terms/20/keyboard-interface.html" data-include-replace="true"></dt>
<dt data-include="terms/21/keyboard-shortcut.html" data-include-replace="true"></dt>
<dt data-include="terms/20/label.html" data-include-replace="true"></dt>
<dt data-include="terms/20/large-scale.html" data-include-replace="true"></dt>
<dt data-include="terms/20/legal-commitments.html" data-include-replace="true"></dt>
<dt data-include="terms/20/link-purpose.html" data-include-replace="true"></dt>
<dt data-include="terms/20/live.html" data-include-replace="true"></dt>
<dt data-include="terms/20/lower-secondary-education-level.html" data-include-replace="true"></dt>
<dt data-include="terms/20/mechanism.html" data-include-replace="true"></dt>
<dt data-include="terms/20/media-alternative-for-text.html" data-include-replace="true"></dt>
<dt data-include="terms/21/motion-animation.html" data-include-replace="true"></dt>
<dt data-include="terms/20/name.html" data-include-replace="true"></dt>
<dt data-include="terms/20/navigated-sequentially.html" data-include-replace="true"></dt>
<dt data-include="terms/20/non-text-content.html" data-include-replace="true"></dt>
<dt data-include="terms/20/normative.html" data-include-replace="true"></dt>
<dt data-include="terms/20/on-a-full-screen-window.html" data-include-replace="true"></dt>
<dt data-include="terms/20/paused.html" data-include-replace="true"></dt>
<dt data-include="terms/21/pointer-input.html" data-include-replace="true"></dt>
<dt data-include="terms/20/prerecorded.html" data-include-replace="true"></dt>
<dt data-include="terms/20/presentation.html" data-include-replace="true"></dt>
<dt data-include="terms/20/primary-education-level.html" data-include-replace="true"></dt>
<dt data-include="terms/20/process.html" data-include-replace="true"></dt>
<dt data-include="terms/20/programmatically-determined.html" data-include-replace="true"></dt>
<dt data-include="terms/20/programmatically-determined-link-context.html" data-include-replace="true"></dt>
<dt data-include="terms/20/programmatically-set.html" data-include-replace="true"></dt>
<dt data-include="terms/20/pure-decoration.html" data-include-replace="true"></dt>
<dt data-include="terms/20/real-time-event.html" data-include-replace="true"></dt>
<dt data-include="terms/21/region.html" data-include-replace="true"></dt>
<dt data-include="terms/20/relationships.html" data-include-replace="true"></dt>
<dt data-include="terms/20/relative-luminance.html" data-include-replace="true"></dt>
<dt data-include="terms/20/relied-upon.html" data-include-replace="true"></dt>
<dt data-include="terms/20/role.html" data-include-replace="true"></dt>
<dt data-include="terms/20/same-functionality.html" data-include-replace="true"></dt>
<dt data-include="terms/20/same-relative-order.html" data-include-replace="true"></dt>
<dt data-include="terms/20/satisfies-a-success-criterion.html" data-include-replace="true"></dt>
<dt data-include="terms/20/section.html" data-include-replace="true"></dt>
<dt data-include="terms/21/set-of-web-pages.html" data-include-replace="true"></dt>
<dt data-include="terms/20/sign-language.html" data-include-replace="true"></dt>
<dt data-include="terms/20/sign-language-interpretation.html" data-include-replace="true"></dt>
<dt data-include="terms/21/single-pointer.html" data-include-replace="true"></dt>
<dt data-include="terms/20/specific-sensory-experience.html" data-include-replace="true"></dt>
<dt data-include="terms/21/state.html" data-include-replace="true"></dt>
<dt data-include="terms/21/status-message.html" data-include-replace="true"></dt>
<dt data-include="terms/20/structure.html" data-include-replace="true"></dt>
<dt data-include="terms/21/style-property.html" data-include-replace="true"></dt>
<dt data-include="terms/20/supplemental-content.html" data-include-replace="true"></dt>
<dt data-include="terms/20/synchronized-media.html" data-include-replace="true"></dt>
<dt data-include="terms/21/target.html" data-include-replace="true"></dt>
<dt data-include="terms/20/technology.html" data-include-replace="true"></dt>
<dt data-include="terms/20/text.html" data-include-replace="true"></dt>
<dt data-include="terms/20/text-alternative.html" data-include-replace="true"></dt>
<dt data-include="terms/21/up-event.html" data-include-replace="true"></dt>
<dt data-include="terms/20/used-in-an-unusual-or-restricted-way.html" data-include-replace="true"></dt>
<dt data-include="terms/20/user-agent.html" data-include-replace="true"></dt>
<dt data-include="terms/20/user-controllable.html" data-include-replace="true"></dt>
<dt data-include="terms/20/user-interface-component.html" data-include-replace="true"></dt>
<dt data-include="terms/21/user-inactivity.html" data-include-replace="true"></dt>
<dt data-include="terms/20/video.html" data-include-replace="true"></dt>
<dt data-include="terms/20/video-only.html" data-include-replace="true"></dt>
<dt data-include="terms/20/viewport.html" data-include-replace="true"></dt>
<dt data-include="terms/20/visually-customized.html" data-include-replace="true"></dt>
<dt data-include="terms/20/web-page.html" data-include-replace="true"></dt>
</dl>
</section>
<div data-include="input-purposes.html" data-include-replace="true"></div>
<section class="appendix" id="changelog">
<h2>Change Log</h2>
<p>This section shows substantive changes made in WCAG 2.2 since WCAG 2.1. <a href="https://www.w3.org/WAI/WCAG21/errata/">Errata fixes to WCAG 2.1</a> have also been incorporated into WCAG 2.2.</p>
<p>The full <a href="https://github.com/w3c/wcag/commits/master/guidelines">commit history to WCAG 2.2</a> is available.</p>
<ul>
<li>2020-01-14: Added <a href="#focus-visible-enhanced">Focus Visible Enhanced</a>.</li>
</ul>
</section>
<section class="appendix informative section" id="acknowledgements">
<h3>Acknowledgments</h3>
<p>Additional information about participation in the Accessibility Guidelines Working Group (AG WG) can be found on the <a href="https://www.w3.org/WAI/GL/">Working Group home page</a>.</p>
<div data-include="../acknowledgements/ag-wg-active.html" data-include-replace="true"></div>
<div data-include="../acknowledgements/ag-contributors.html" data-include-replace="true"></div>
<div data-include="../acknowledgements/funders.html" data-include-replace="true"></div>
</section>
</body>
</html>