WCAG
187 KB
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
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US"><head><title>Web Content Accessibility Guidelines (WCAG) 2.0</title><link media="print" type="text/css" rel="stylesheet" href="print.css"/><link rel="stylesheet" type="text/css" href="additional.css"/><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-REC"/></head><body><p align="center">[<a href="#contents">contents</a>] </p><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"/></a></p>
<h1><a name="title" id="title"> </a>Web Content Accessibility Guidelines (WCAG) 2.0</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"> </a>W3C Recommendation 11 December 2008</h2><dl><dt>This version:</dt><dd>
<a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/">http://www.w3.org/TR/2008/REC-WCAG20-20081211/</a>
</dd><dt>Latest version:</dt><dd>
<a href="http://www.w3.org/TR/WCAG20/">http://www.w3.org/TR/WCAG20/</a>
</dd><dt>Previous version:</dt><dd>
<a href="http://www.w3.org/TR/2008/PR-WCAG20-20081103/">http://www.w3.org/TR/2008/PR-WCAG20-20081103/</a>
</dd><dt>Editors:</dt><dd>Ben Caldwell, Trace R&D Center, University of Wisconsin-Madison</dd><dd>Michael Cooper, W3C</dd><dd>Loretta Guarino Reid, Google, Inc.</dd><dd>Gregg Vanderheiden, Trace R&D Center, University of Wisconsin-Madison</dd><dt>Previous Editors:</dt><dd>Wendy Chisholm (until July 2006 while at W3C)</dd><dd>John Slatin (until June 2006 while at Accessibility Institute, University of Texas at Austin)</dd><dd>Jason White (until June 2005 while at University of Melbourne)</dd></dl><p>Please refer to the <a href="http://www.w3.org/WAI/WCAG20/errata/"><strong>errata</strong></a> for this document, which may
include normative corrections.</p><p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=WCAG20"><strong>translations</strong></a>.</p>
<p>This document is also available in non-normative formats, available from <a href="/WAI/WCAG20/versions/guidelines/">Alternate Versions of Web Content Accessibility Guidelines 2.0</a>.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2008 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
<h2><a name="abstract" id="abstract"> </a>Abstract</h2><p>Web Content Accessibility Guidelines (WCAG) 2.0 covers a wide range of recommendations for making Web content more accessible.
Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general.
</p><p>WCAG 2.0 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. <span>See <a href="http://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG) Overview</a> for an introduction and links to WCAG technical and educational material.</span>
</p><p><span>WCAG 2.0 succeeds <a href="http://www.w3.org/TR/WCAG10/">Web Content Accessibility Guidelines 1.0</a>
<a href="#WCAG10">[WCAG10]</a>, which was published as a W3C Recommendation May 1999. Although it is possible to conform either to WCAG 1.0 or to WCAG 2.0 (or both), the W3C recommends that new and updated content use WCAG 2.0. The W3C also recommends that Web accessibility policies reference WCAG 2.0. </span></p></div><div>
<h2><a name="status" id="status"> </a>Status of this Document</h2><p><em>This section describes the status of this document at the time of its
publication. Other documents may supersede this document. A list of current
W3C publications and the latest revision of this technical report can be
found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at <a href="http://www.w3.org/TR/">http://www.w3.org/TR/</a>.</em></p><p>This is the Web Content Accessibility Guidelines (WCAG) 2.0 <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#RecsW3C"> W3C Recommendation</a> from the <a href="http://www.w3.org/WAI/GL/">Web Content Accessibility
Guidelines Working Group</a>.</p><p>This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.</p><p>WCAG 2.0 is supported by the associated non-normative
documents, <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/">Understanding
WCAG 2.0</a> and <a href="http://www.w3.org/TR/WCAG20-TECHS/">Techniques for
WCAG 2.0</a>. Although those documents do not have the formal status that
WCAG 2.0 itself has, they provide information important to understanding and
implementing WCAG.</p><p>The Working Group requests that any comments be made using the provided <a href="http://www.w3.org/WAI/WCAG20/comments/">online comment
form</a>. If this is not possible, comments can also be sent to <a href="mailto:public-comments-wcag20@w3.org">public-comments-wcag20@w3.org</a>.
The <a href="http://lists.w3.org/Archives/Public/public-comments-wcag20/">archives
for the public comments list</a> are publicly available. Comments received on the WCAG 2.0 Recommendation cannot result in changes to this version of the guidelines, but may be addressed in errata or future versions of WCAG. The Working Group does not plan to make formal responses to comments. Archives of the <a href="http://lists.w3.org/Archives/Public/w3c-wai-gl/">WCAG WG mailing list
discussions</a> are publicly available, and future work undertaken by the Working Group may address comments received on this document.</p><p>This document has been produced as part of the W3C <a href="http://www.w3.org/WAI/">Web Accessibility Initiative</a> (WAI). The
goals of the WCAG Working Group are discussed in the <a href="http://www.w3.org/2004/04/wcag-charter">WCAG Working Group
charter</a>. The WCAG Working Group is part of the <a href="http://www.w3.org/WAI/Technical/Activity">WAI Technical
Activity</a>.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004
W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/35422/status" rel="disclosure">public
list of any patent disclosures</a> made in connection with the deliverables
of the group; that page also includes instructions for disclosing a patent.
An individual who has actual knowledge of a patent which the individual
believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
6 of the W3C Patent Policy</a>. </p></div><div class="toc">
<hr/><h2><a name="contents" id="contents"> </a>Table of Contents</h2><ul class="toc"><li><a href="#intro">Introduction </a><ul class="toc"><li><a href="#intro-layers-guidance">WCAG 2.0 Layers of Guidance</a></li><li><a href="#intro-related-docs">
WCAG 2.0 Supporting Documents
</a></li><li><a href="#new-terms">Important Terms in WCAG 2.0</a></li></ul></li><li><a href="#guidelines">WCAG 2.0 Guidelines</a><ul class="toc"><li><a href="#perceivable">1 Perceivable</a><ul class="toc"><li>1.1 <a href="#text-equiv">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.</a></li><li>1.2 <a href="#media-equiv">Provide alternatives for time-based media.</a></li><li>1.3 <a href="#content-structure-separation">Create content that can be presented in different ways (for example simpler layout) without losing information or structure.</a></li><li>1.4 <a href="#visual-audio-contrast">
Make it easier for users to see and hear content including separating foreground from background.
</a></li></ul></li><li><a href="#operable">2 Operable</a><ul class="toc"><li>2.1 <a href="#keyboard-operation">
Make all functionality available from a keyboard.
</a></li><li>2.2 <a href="#time-limits">
Provide users enough time to read and use content.
</a></li><li>2.3 <a href="#seizure">Do not design content in a way that is known to cause seizures.</a></li><li>2.4 <a href="#navigation-mechanisms">
Provide ways to help users navigate, find content, and determine where they are.
</a></li></ul></li><li><a href="#understandable">3 Understandable</a><ul class="toc"><li>3.1 <a href="#meaning">
Make text content readable and understandable.
</a></li><li>3.2 <a href="#consistent-behavior">
Make Web pages appear and operate in predictable ways.
</a></li><li>3.3 <a href="#minimize-error">
Help users avoid and correct mistakes.
</a></li></ul></li><li><a href="#robust">4 Robust</a><ul class="toc"><li>4.1 <a href="#ensure-compat">Maximize compatibility with current and future user agents, including assistive technologies.</a></li></ul></li></ul></li><li><a href="#conformance">Conformance</a><ul class="toc"><li><a href="#conformance-reqs">Conformance Requirements</a></li><li><a href="#conformance-claims">Conformance Claims (Optional)
</a></li><li><a href="#conformance-partial">Statement of Partial Conformance - Third Party Content</a></li><li><a href="#conformance-partial-lang">Statement of Partial Conformance - Language</a></li></ul></li></ul>
<h3><a name="appendices" id="appendices"> </a>Appendices</h3><ul class="toc"><li>Appendix A: <a href="#glossary">Glossary</a> (Normative)</li> <li>Appendix B: <a href="#acknowledgments">Acknowledgments</a></li> <li>Appendix C: <a href="#references">References</a></li> </ul></div><hr/><div class="front"><div class="div1">
<h2><a name="intro" id="intro"> </a>Introduction </h2><p>This section is <a title="definition: informative" href="#informativedef" class="termref">informative</a>. </p><p>Web Content Accessibility Guidelines (WCAG) 2.0 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.0 is developed through the <a href="http://www.w3.org/WAI/intro/w3c-process.php">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.0 builds on WCAG 1.0 <a href="#WCAG10">[WCAG10]</a> 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="http://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG) Overview</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><p>
<strong>
<a href="http://www.w3.org/WAI/intro/components">Essential Components of Web Accessibility</a>
</strong>
</p></li><li><p>
<strong>
<a href="http://www.w3.org/WAI/intro/uaag.php">User Agent Accessibility Guidelines (UAAG) Overview</a>
</strong>
</p></li><li><p>
<strong>
<a href="http://www.w3.org/WAI/intro/atag.php">Authoring Tool Accessibility Guidelines (ATAG) Overview</a>
</strong>
</p></li></ul><div class="div2"> <h3><a name="intro-layers-guidance" id="intro-layers-guidance"> </a>WCAG 2.0 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, 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="http://www.w3.org/TR/UNDERSTANDING-WCAG20/intro.html#introduction-fourprincs-head">Understanding the Four Principles of Accessibility</a>.</p></li><li><p>
<strong>Guidelines</strong> - Under the principles are guidelines. The 12 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.0 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="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-levels-head">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.0 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="http://www.w3.org/TR/UNDERSTANDING-WCAG20/intro.html#introduction-layers-techs-head">Sufficient and Advisory Techniques in Understanding WCAG 2.0</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="http://www.w3.org/TR/UNDERSTANDING-WCAG20/appendixC.html#understanding-metadata">Metadata</a> may assist users in finding content most suitable for their needs.
</p></div><div class="div2"> <h3><a name="intro-related-docs" id="intro-related-docs"> </a>
WCAG 2.0 Supporting Documents
</h3><p>The WCAG 2.0 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.0 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="/WAI/WCAG20/quickref/">How to Meet WCAG 2.0</a></strong>
- A customizable quick reference to WCAG 2.0 that includes all of the guidelines, success criteria, and techniques for authors to use as they are developing and evaluating Web content.
</p></li><li><p>
<strong>
<a href="/TR/UNDERSTANDING-WCAG20/">Understanding WCAG 2.0</a>
</strong> - A guide to understanding and implementing WCAG 2.0. There is a short "Understanding" document for each guideline and success criterion in WCAG 2.0 as well as key topics.</p></li><li><p>
<strong>
<a href="/TR/WCAG20-TECHS/">Techniques for WCAG 2.0</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="http://www.w3.org/WAI/intro/wcag20">The WCAG 2.0 Documents</a></strong> - A diagram and description of how the technical documents are related and linked.</p></li></ol><p>See <a href="http://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (WCAG) Overview</a> for a description of the WCAG 2.0 supporting material, including education resources related to WCAG 2.0. <span>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="http://www.w3.org/WAI/Resources/Overview">WAI Resources</a>.</span></p></div><div class="div2"> <h3><a name="new-terms" id="new-terms"> </a>Important Terms in WCAG 2.0</h3><p>
WCAG 2.0 includes three important terms that are different from WCAG 1.0.
Each of these is introduced briefly below and defined more fully in the glossary.
</p><dl><dt class="label">Web Page</dt><dd><p>It is important to note that, in this standard, the term "<a title="definition: Web page" href="#webpagedef" class="termref">Web page</a>" includes much more than static HTML pages. It also includes the increasingly dynamic Web pages that are emerging on the Web, including "pages" that can present entire virtual interactive communities. For example, the term "Web page" includes an immersive, interactive movie-like experience found at a single URI. For more information, see <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-web-page-head">Understanding "Web Page"</a>.</p></dd><dt class="label">Programmatically Determined</dt><dd><p>Several success criteria require that content (or certain aspects of content) can be "<a title="definition: programmatically determined (programmatically determinable)" href="#programmaticallydetermineddef" class="termref">programmatically determined</a>." This means that the content is delivered in such a way that <a title="definition: user agent" href="#useragentdef" class="termref">user agents</a>, including <a title="definition: assistive technology (as used in this document)" href="#atdef" class="termref">assistive technologies</a>, can extract and present this information to users in different modalities. For more information, see <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-programmatically-determined-head">Understanding Programmatically Determined</a>.
</p></dd><dt class="label">Accessibility Supported</dt><dd><p>Using a technology in a way that is accessibility supported means that it works with assistive technologies (AT) and the accessibility features of operating systems, browsers, and other user agents. Technology features can only be <a title="definition: relied upon (technologies that are)" href="#reliedupondef" class="termref">relied upon</a> to conform to WCAG 2.0 success criteria if they are used in a way that is "<a title="definition: accessibility supported" href="#accessibility-supporteddef" class="termref">accessibility supported</a>". Technology features can be used in ways that are not accessibility supported (do not work with assistive technologies, etc.) as long as they are not relied upon to conform to any success criterion (i.e., the same information or functionality is also available another way that is supported). </p><p>
The definition of "accessibility supported" is provided in the <a href="#glossary">Appendix A: Glossary</a> section of these guidelines. For more information, see <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-accessibility-support-head">Understanding Accessibility Support</a>. </p></dd></dl></div></div></div><div class="body"><div class="div1">
<h2><a name="guidelines" id="guidelines"> </a>WCAG 2.0 Guidelines</h2><p>This section is <a title="definition: normative" href="#normativedef" class="termref">normative</a>.</p><div class="div2"> <h2 class="principle"><a name="perceivable" id="perceivable"> </a>Principle 1: Perceivable - Information and user interface components must be presentable to users in ways they can perceive.</h2><div class="div3"><div class="guideline"><h3><a name="text-equiv" id="text-equiv"> </a> Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.</h3><p class="und-gl-link"><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv.html">Understanding Guideline 1.1</a></p></div><div class="req"><div class="sc" id="text-equiv-all"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.1.1 Non-text Content:</strong> All <a title="definition: non-text content" href="#non-text-contentdef" class="termref">non-text content</a> that is presented to the user has a <a title="definition: text alternative" href="#text-altdef" class="termref">text alternative</a> that serves the equivalent purpose, except for the situations listed below.
(Level A)
</p><ul><li><p>
<strong class="sc-handle">Controls, Input: </strong> If non-text content is a control or accepts user input, then it has a <a title="definition: name" href="#namedef" class="termref">name</a> that describes its purpose. (Refer to <a href="#ensure-compat">Guideline 4.1</a> for additional requirements for controls and content that accepts user input.)
</p></li><li><p>
<strong class="sc-handle">Time-Based Media: </strong> If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to <a href="#media-equiv">Guideline 1.2</a> for additional requirements for media.)
</p></li><li><p>
<strong class="sc-handle">Test: </strong> If non-text content is a test or exercise that would be invalid if presented in <a title="definition: text" href="#textdef" class="termref">text</a>, then text alternatives at least provide descriptive identification of the non-text content.
</p></li><li><p>
<strong class="sc-handle">Sensory: </strong> If non-text content is primarily intended to create a <a title="definition: specific sensory experience" href="#sensoryexpdef" class="termref">specific sensory experience</a>, then text alternatives at least provide descriptive identification of the non-text content.
</p></li><li><p>
<strong class="sc-handle">
<a title="definition: CAPTCHA" href="#CAPTCHAdef" class="termref">CAPTCHA</a>: </strong>If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception
are provided to accommodate different disabilities.</p></li><li><p>
<strong class="sc-handle">Decoration, Formatting, Invisible: </strong>If non-text content is <a title="definition: pure decoration" href="#puredecdef" class="termref">pure decoration</a>, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by <a title="definition: assistive technology (as used in this document)" href="#atdef" class="termref">assistive technology</a>.</p></li></ul></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-text-equiv-all" class="HTMlink" title="How to Meet Success Criterion 1.1.1">How to Meet 1.1.1</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv-all.html" class="HTMlink" title="Understanding Success Criterion 1.1.1">Understanding 1.1.1</a></p></div></div></div></div><div class="div3"><div class="guideline"><h3><a name="media-equiv" id="media-equiv"> </a> Guideline 1.2 Time-based Media: Provide alternatives for time-based media.</h3><p class="und-gl-link"><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv.html">Understanding Guideline 1.2</a></p></div><div class="req"><div class="sc" id="media-equiv-av-only-alt"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.2.1 Audio-only and Video-only (Prerecorded):</strong> For <a title="definition: prerecorded" href="#prerecordeddef" class="termref">prerecorded</a> <a title="definition: audio-only" href="#audio-onlydef" class="termref">audio-only</a> and prerecorded <a title="definition: video-only" href="#video-onlydef" class="termref">video-only</a> media, the following are true, except when the audio or video is a <a title="definition: media alternative for text" href="#multimedia-alt-textdef" class="termref">media alternative for text</a> and is clearly labeled as such:
(Level A)
</p><ul><li><p><strong class="sc-handle">Prerecorded Audio-only: </strong>An <a title="definition: alternative for time-based media" href="#alt-time-based-mediadef" class="termref">alternative for time-based media</a> is provided that presents equivalent information for prerecorded audio-only content.</p></li><li><p><strong class="sc-handle">Prerecorded Video-only: </strong>Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.</p></li></ul></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-av-only-alt" class="HTMlink" title="How to Meet Success Criterion 1.2.1">How to Meet 1.2.1</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-av-only-alt.html" class="HTMlink" title="Understanding Success Criterion 1.2.1">Understanding 1.2.1</a></p></div></div><div class="sc" id="media-equiv-captions"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.2.2 Captions (Prerecorded):</strong>
<a title="definition: captions" href="#captionsdef" class="termref">Captions</a> are provided for all <a title="definition: prerecorded" href="#prerecordeddef" class="termref">prerecorded</a> <a title="definition: audio" href="#audiodef" class="termref">audio</a> content in <a title="definition: synchronized media" href="#synchronizedmediadef" class="termref">synchronized media</a>, except when the media is a <a title="definition: media alternative for text" href="#multimedia-alt-textdef" class="termref">media alternative for text</a> and is clearly labeled as such.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-captions" class="HTMlink" title="How to Meet Success Criterion 1.2.2">How to Meet 1.2.2</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-captions.html" class="HTMlink" title="Understanding Success Criterion 1.2.2">Understanding 1.2.2</a></p></div></div><div class="sc" id="media-equiv-audio-desc"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.2.3 Audio Description or Media Alternative (Prerecorded):</strong>
An <a title="definition: alternative for time-based media" href="#alt-time-based-mediadef" class="termref">alternative for time-based media</a> or <a title="definition: audio description" href="#audiodescdef" class="termref">audio description</a> of the <a title="definition: prerecorded" href="#prerecordeddef" class="termref">prerecorded</a> <a title="definition: video" href="#videodef" class="termref">video</a> content is provided for <a title="definition: synchronized media" href="#synchronizedmediadef" class="termref">synchronized media</a>, except when the media is a <a title="definition: media alternative for text" href="#multimedia-alt-textdef" class="termref">media alternative for text</a> and is clearly labeled as such.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-audio-desc" class="HTMlink" title="How to Meet Success Criterion 1.2.3">How to Meet 1.2.3</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-audio-desc.html" class="HTMlink" title="Understanding Success Criterion 1.2.3">Understanding 1.2.3</a></p></div></div></div><div class="bp"><div class="sc" id="media-equiv-real-time-captions"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.2.4 Captions (Live):</strong>
<a title="definition: captions" href="#captionsdef" class="termref">Captions</a> are provided for all <a title="definition: live" href="#livedef" class="termref">live</a> <a title="definition: audio" href="#audiodef" class="termref">audio</a> content in <a title="definition: synchronized media" href="#synchronizedmediadef" class="termref">synchronized media</a>.
(Level AA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-real-time-captions" class="HTMlink" title="How to Meet Success Criterion 1.2.4">How to Meet 1.2.4</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-real-time-captions.html" class="HTMlink" title="Understanding Success Criterion 1.2.4">Understanding 1.2.4</a></p></div></div><div class="sc" id="media-equiv-audio-desc-only"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.2.5 Audio Description (Prerecorded):</strong>
<a title="definition: audio description" href="#audiodescdef" class="termref">Audio description</a> is provided for all <a title="definition: prerecorded" href="#prerecordeddef" class="termref">prerecorded</a> <a title="definition: video" href="#videodef" class="termref">video</a> content in <a title="definition: synchronized media" href="#synchronizedmediadef" class="termref">synchronized media</a>.
(Level AA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-audio-desc-only" class="HTMlink" title="How to Meet Success Criterion 1.2.5">How to Meet 1.2.5</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-audio-desc-only.html" class="HTMlink" title="Understanding Success Criterion 1.2.5">Understanding 1.2.5</a></p></div></div></div><div class="additional"><div class="sc" id="media-equiv-sign"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.2.6 Sign Language (Prerecorded):</strong>
<a title="definition: sign language interpretation" href="#sign-languageinterpdef" class="termref">Sign language interpretation</a> is provided for all <a title="definition: prerecorded" href="#prerecordeddef" class="termref">prerecorded</a> <a title="definition: audio" href="#audiodef" class="termref">audio</a> content in <a title="definition: synchronized media" href="#synchronizedmediadef" class="termref">synchronized media</a>.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-sign" class="HTMlink" title="How to Meet Success Criterion 1.2.6">How to Meet 1.2.6</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-sign.html" class="HTMlink" title="Understanding Success Criterion 1.2.6">Understanding 1.2.6</a></p></div></div><div class="sc" id="media-equiv-extended-ad"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.2.7 Extended Audio Description (Prerecorded):</strong>
Where pauses in foreground audio are insufficient to allow <a title="definition: audio description" href="#audiodescdef" class="termref">audio descriptions</a> to convey the sense of the video, <a title="definition: extended audio description" href="#extended-addef" class="termref">extended audio description</a> is provided for all <a title="definition: prerecorded" href="#prerecordeddef" class="termref">prerecorded</a> <a title="definition: video" href="#videodef" class="termref">video</a> content in <a title="definition: synchronized media" href="#synchronizedmediadef" class="termref">synchronized media</a>.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-extended-ad" class="HTMlink" title="How to Meet Success Criterion 1.2.7">How to Meet 1.2.7</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-extended-ad.html" class="HTMlink" title="Understanding Success Criterion 1.2.7">Understanding 1.2.7</a></p></div></div><div class="sc" id="media-equiv-text-doc"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.2.8 Media Alternative (Prerecorded):</strong>
An <a title="definition: alternative for time-based media" href="#alt-time-based-mediadef" class="termref">alternative for time-based media</a> is provided for all <a title="definition: prerecorded" href="#prerecordeddef" class="termref">prerecorded</a> <a title="definition: synchronized media" href="#synchronizedmediadef" class="termref">synchronized media</a> and for all prerecorded <a title="definition: video-only" href="#video-onlydef" class="termref">video-only</a> media.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-text-doc" class="HTMlink" title="How to Meet Success Criterion 1.2.8">How to Meet 1.2.8</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-text-doc.html" class="HTMlink" title="Understanding Success Criterion 1.2.8">Understanding 1.2.8</a></p></div></div><div class="sc" id="media-equiv-live-audio-only"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.2.9 Audio-only (Live):</strong> An <a title="definition: alternative for time-based media" href="#alt-time-based-mediadef" class="termref">alternative for time-based media</a> that presents equivalent information for <a title="definition: live" href="#livedef" class="termref">live</a> <a title="definition: audio-only" href="#audio-onlydef" class="termref">audio-only</a> content is provided.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-media-equiv-live-audio-only" class="HTMlink" title="How to Meet Success Criterion 1.2.9">How to Meet 1.2.9</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-live-audio-only.html" class="HTMlink" title="Understanding Success Criterion 1.2.9">Understanding 1.2.9</a></p></div></div></div></div><div class="div3"><div class="guideline"><h3><a name="content-structure-separation" id="content-structure-separation"> </a> Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.</h3><p class="und-gl-link"><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation.html">Understanding Guideline 1.3</a></p></div><div class="req"><div class="sc" id="content-structure-separation-programmatic"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.3.1 Info and Relationships:</strong> Information, <a title="definition: structure" href="#structuredef" class="termref">structure</a>,
and <a title="definition: relationships" href="#relationshipsdef" class="termref">relationships</a> conveyed through <a title="definition: presentation" href="#presentationdef" class="termref">presentation</a> can be <a title="definition: programmatically determined (programmatically determinable)" href="#programmaticallydetermineddef" class="termref">programmatically determined</a> or are available in text.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-content-structure-separation-programmatic" class="HTMlink" title="How to Meet Success Criterion 1.3.1">How to Meet 1.3.1</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-programmatic.html" class="HTMlink" title="Understanding Success Criterion 1.3.1">Understanding 1.3.1</a></p></div></div><div class="sc" id="content-structure-separation-sequence"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.3.2 Meaningful Sequence:</strong> When the sequence in which content is presented affects its meaning, a <a title="definition: correct reading sequence" href="#correct-reading-sequencedef" class="termref">correct reading sequence</a> can be <a title="definition: programmatically determined (programmatically determinable)" href="#programmaticallydetermineddef" class="termref">programmatically determined</a>.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-content-structure-separation-sequence" class="HTMlink" title="How to Meet Success Criterion 1.3.2">How to Meet 1.3.2</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-sequence.html" class="HTMlink" title="Understanding Success Criterion 1.3.2">Understanding 1.3.2</a></p></div></div><div class="sc" id="content-structure-separation-understanding"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.3.3 Sensory Characteristics:</strong>
Instructions provided for understanding
and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.
(Level A)
</p><div class="note"><p class="prefix"><em>Note: </em>For requirements related to color, refer to <a href="#visual-audio-contrast">Guideline 1.4</a>.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-content-structure-separation-understanding" class="HTMlink" title="How to Meet Success Criterion 1.3.3">How to Meet 1.3.3</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/content-structure-separation-understanding.html" class="HTMlink" title="Understanding Success Criterion 1.3.3">Understanding 1.3.3</a></p></div></div></div></div><div class="div3"><div class="guideline"><h3><a name="visual-audio-contrast" id="visual-audio-contrast"> </a> Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
</h3><p class="und-gl-link"><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast.html">Understanding Guideline 1.4</a></p></div><div class="req"><div class="sc" id="visual-audio-contrast-without-color"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.4.1 Use of Color:</strong>
Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
(Level A)
</p><div class="note"><p class="prefix"><em>Note: </em>This success criterion addresses color perception specifically. Other forms of perception are covered in <a href="#content-structure-separation">Guideline 1.3</a> including programmatic access to color and other visual presentation coding.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-visual-audio-contrast-without-color" class="HTMlink" title="How to Meet Success Criterion 1.4.1">How to Meet 1.4.1</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-without-color.html" class="HTMlink" title="Understanding Success Criterion 1.4.1">Understanding 1.4.1</a></p></div></div><div class="sc" id="visual-audio-contrast-dis-audio"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.4.2 Audio Control:</strong>
If any audio on a Web page plays automatically for more than 3 seconds, either a <a title="definition: mechanism" href="#mechanismdef" class="termref">mechanism</a> is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.
(Level A)
</p><div class="note"><p class="prefix"><em>Note: </em>Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion. See <a href="#cc5">Conformance Requirement 5: Non-Interference</a>.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-visual-audio-contrast-dis-audio" class="HTMlink" title="How to Meet Success Criterion 1.4.2">How to Meet 1.4.2</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-dis-audio.html" class="HTMlink" title="Understanding Success Criterion 1.4.2">Understanding 1.4.2</a></p></div></div></div><div class="bp"><div class="sc" id="visual-audio-contrast-contrast"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.4.3 Contrast (Minimum):</strong>
<span>The visual presentation of </span><a title="definition: text" href="#textdef" class="termref">text</a> and <a title="definition: image of text" href="#images-of-textdef" class="termref">images of text</a> has a <a title="definition: contrast ratio" href="#contrast-ratiodef" class="termref">contrast ratio</a> of at least <span>4.</span>5:1, except for the following:
(Level AA)
</p><ul><li><p>
<strong class="sc-handle">Large Text: </strong>
<a title="definition: large scale (text)" href="#larger-scaledef" class="termref">Large-scale</a> text and images of large-scale text have a contrast ratio of at least 3:1;</p></li><li><p>
<strong class="sc-handle">Incidental: </strong> Text or images of text that are part of an inactive <a title="definition: user interface component" href="#user-interface-componentdef" class="termref">user interface component</a>, that are <a title="definition: pure decoration" href="#puredecdef" class="termref">pure decoration</a>, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.</p></li><li><p>
<strong class="sc-handle">Logotypes: </strong>
Text that is part of a logo or brand name has no minimum contrast requirement.</p></li></ul></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-visual-audio-contrast-contrast" class="HTMlink" title="How to Meet Success Criterion 1.4.3">How to Meet 1.4.3</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html" class="HTMlink" title="Understanding Success Criterion 1.4.3">Understanding 1.4.3</a></p></div></div><div class="sc" id="visual-audio-contrast-scale"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.4.4 Resize text:</strong>
Except for <a title="definition: captions" href="#captionsdef" class="termref">captions</a> and <a title="definition: image of text" href="#images-of-textdef" class="termref">images of text</a>, <a title="definition: text" href="#textdef" class="termref">text</a> can be resized without <a title="definition: assistive technology (as used in this document)" href="#atdef" class="termref">assistive technology</a> up to 200 percent without loss of content or functionality.
(Level AA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-visual-audio-contrast-scale" class="HTMlink" title="How to Meet Success Criterion 1.4.4">How to Meet 1.4.4</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.html" class="HTMlink" title="Understanding Success Criterion 1.4.4">Understanding 1.4.4</a></p></div></div><div class="sc" id="visual-audio-contrast-text-presentation"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.4.5 Images of Text:</strong> If the technologies being used can achieve the visual presentation, <a title="definition: text" href="#textdef" class="termref">text</a> is used to convey information rather than <a title="definition: image of text" href="#images-of-textdef" class="termref">images of text</a> except for the following:
(Level AA)
</p><ul><li><p>
<strong>Customizable:</strong> The image of text can be <a title="definition: visually customized" href="#visually-customizeddef" class="termref">visually customized</a> to the user's requirements;</p></li><li><p>
<strong>Essential:</strong> A particular presentation of text is <a title="definition: essential" href="#essentialdef" class="termref">essential</a> to the information being conveyed.</p></li></ul><div class="note"><p class="prefix"><em>Note: </em>Logotypes (text that is part of a logo or brand name) are considered essential.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-visual-audio-contrast-text-presentation" class="HTMlink" title="How to Meet Success Criterion 1.4.5">How to Meet 1.4.5</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-text-presentation.html" class="HTMlink" title="Understanding Success Criterion 1.4.5">Understanding 1.4.5</a></p></div></div></div><div class="additional"><div class="sc" id="visual-audio-contrast7"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.4.6 Contrast (Enhanced):</strong>
<span>The visual presentation of </span><a title="definition: text" href="#textdef" class="termref">text</a> and <a title="definition: image of text" href="#images-of-textdef" class="termref">images of text</a> has a <a title="definition: contrast ratio" href="#contrast-ratiodef" class="termref">contrast ratio</a> of at least 7:1, except for the following:
(Level AAA)
</p><ul><li><p>
<strong class="sc-handle">Large Text: </strong>
<a title="definition: large scale (text)" href="#larger-scaledef" class="termref">Large-scale</a> text and images of large-scale text have a contrast ratio of at least <span>4.</span>5:1;</p></li><li><p>
<strong class="sc-handle">Incidental: </strong> Text or images of text that are part of an inactive <a title="definition: user interface component" href="#user-interface-componentdef" class="termref">user interface component</a>, that are <a title="definition: pure decoration" href="#puredecdef" class="termref">pure decoration</a>, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.</p></li><li><p>
<strong class="sc-handle">Logotypes: </strong>
Text that is part of a logo or brand name has no minimum contrast requirement.</p></li></ul></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-visual-audio-contrast7" class="HTMlink" title="How to Meet Success Criterion 1.4.6">How to Meet 1.4.6</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast7.html" class="HTMlink" title="Understanding Success Criterion 1.4.6">Understanding 1.4.6</a></p></div></div><div class="sc" id="visual-audio-contrast-noaudio"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.4.7 Low or No Background Audio:</strong> For <a title="definition: prerecorded" href="#prerecordeddef" class="termref">prerecorded</a> <a title="definition: audio-only" href="#audio-onlydef" class="termref">audio-only</a> content that (1) contains primarily speech in the foreground, (2) is not an audio <a title="definition: CAPTCHA" href="#CAPTCHAdef" class="termref">CAPTCHA</a> or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true:
(Level AAA)
</p><ul><li><p><strong class="sc-handle">No Background: </strong>The audio does not contain background sounds.</p></li><li><p><strong class="sc-handle">Turn Off: </strong>The background sounds can be turned off.</p></li><li><p><strong class="sc-handle">20 dB: </strong> The background sounds are at least 20 decibels lower than the
foreground speech content, with the exception of occasional sounds that last for only one or two seconds.</p><div class="note"><p class="prefix"><em>Note: </em>Per the definition of "decibel," background sound that meets this requirement will be approximately four times quieter than the foreground speech content. </p></div></li></ul></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-visual-audio-contrast-noaudio" class="HTMlink" title="How to Meet Success Criterion 1.4.7">How to Meet 1.4.7</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-noaudio.html" class="HTMlink" title="Understanding Success Criterion 1.4.7">Understanding 1.4.7</a></p></div></div><div class="sc" id="visual-audio-contrast-visual-presentation"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.4.8 Visual Presentation:</strong> For the visual presentation of <a title="definition: blocks of text" href="#blockstextdef" class="termref">blocks of text</a>, a <a title="definition: mechanism" href="#mechanismdef" class="termref">mechanism</a> is available to achieve the following:
(Level AAA)
</p><ol class="enumar"><li><p>Foreground and background colors can be selected by the user.</p></li><li><p>Width is no more than 80 characters or glyphs (40 if <acronym title="Chinese, Japanese and Korean">CJK</acronym>).</p></li><li><p>Text is not justified (aligned to both the left and the right margins).</p></li><li><p>Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.</p></li><li><p>Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text <a title="definition: on a full-screen window" href="#fullscreenwindowdef" class="termref">on a full-screen window</a>.</p></li></ol></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-visual-audio-contrast-visual-presentation" class="HTMlink" title="How to Meet Success Criterion 1.4.8">How to Meet 1.4.8</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-visual-presentation.html" class="HTMlink" title="Understanding Success Criterion 1.4.8">Understanding 1.4.8</a></p></div></div><div class="sc" id="visual-audio-contrast-text-images"><div class="scinner"><p class="sctxt"><strong class="sc-handle">1.4.9 Images of Text (No Exception):</strong> <a title="definition: image of text" href="#images-of-textdef" class="termref">Images of text</a> are only used for <a title="definition: pure decoration" href="#puredecdef" class="termref">pure decoration</a> or where a particular presentation of <a title="definition: text" href="#textdef" class="termref">text</a> is <a title="definition: essential" href="#essentialdef" class="termref">essential</a> to the information being conveyed.
(Level AAA)
</p><div class="note"><p class="prefix"><em>Note: </em>Logotypes (text that is part of a logo or brand name) are considered essential.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-visual-audio-contrast-text-images" class="HTMlink" title="How to Meet Success Criterion 1.4.9">How to Meet 1.4.9</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-text-images.html" class="HTMlink" title="Understanding Success Criterion 1.4.9">Understanding 1.4.9</a></p></div></div></div></div></div><div class="div2"> <h2 class="principle"><a name="operable" id="operable"> </a>Principle 2: Operable - User interface components and navigation must be operable.</h2><div class="div3"><div class="guideline"><h3><a name="keyboard-operation" id="keyboard-operation"> </a> Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
</h3><p class="und-gl-link"><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation.html">Understanding Guideline 2.1</a></p></div><div class="req"><div class="sc" id="keyboard-operation-keyboard-operable"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.1.1 Keyboard:</strong> All <a title="definition: functionality" href="#functiondef" class="termref">functionality</a> of the content is operable through a <a title="definition: keyboard interface" href="#keybrd-interfacedef" class="termref">keyboard interface</a> without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.
(Level A)
</p><div class="note"><p class="prefix"><em>Note 1:
</em>This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.</p><p class="prefix"><em>Note 2:
</em>This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-keyboard-operation-keyboard-operable" class="HTMlink" title="How to Meet Success Criterion 2.1.1">How to Meet 2.1.1</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-keyboard-operable.html" class="HTMlink" title="Understanding Success Criterion 2.1.1">Understanding 2.1.1</a></p></div></div><div class="sc" id="keyboard-operation-trapping"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.1.2 No Keyboard Trap:</strong> If keyboard focus can be moved to a component of the page using a <a title="definition: keyboard interface" href="#keybrd-interfacedef" class="termref">keyboard interface</a>, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.
(Level A)
</p><div class="note"><p class="prefix"><em>Note: </em>Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See <a href="#cc5">Conformance Requirement 5: Non-Interference</a>.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-keyboard-operation-trapping" class="HTMlink" title="How to Meet Success Criterion 2.1.2">How to Meet 2.1.2</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-trapping.html" class="HTMlink" title="Understanding Success Criterion 2.1.2">Understanding 2.1.2</a></p></div></div></div><div class="additional"><div class="sc" id="keyboard-operation-all-funcs"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.1.3 Keyboard (No Exception):</strong> All <a title="definition: functionality" href="#functiondef" class="termref">functionality</a> of the content is operable through a <a title="definition: keyboard interface" href="#keybrd-interfacedef" class="termref">keyboard interface</a> without requiring specific timings for individual keystrokes.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-keyboard-operation-all-funcs" class="HTMlink" title="How to Meet Success Criterion 2.1.3">How to Meet 2.1.3</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation-all-funcs.html" class="HTMlink" title="Understanding Success Criterion 2.1.3">Understanding 2.1.3</a></p></div></div></div></div><div class="div3"><div class="guideline"><h3><a name="time-limits" id="time-limits"> </a> Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
</h3><p class="und-gl-link"><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits.html">Understanding Guideline 2.2</a></p></div><div class="req"><div class="sc" id="time-limits-required-behaviors"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.2.1 Timing Adjustable:</strong> For each time limit that is
set by the content, at least one of the following is true:
(Level A)
</p><ul><li><p>
<strong class="sc-handle">Turn off: </strong>The user is allowed to turn off the time limit
before encountering it; or
</p></li><li><p>
<strong class="sc-handle">Adjust: </strong>The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or</p></li><li><p>
<strong class="sc-handle">Extend: </strong>The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or</p></li><li><p>
<strong class="sc-handle">Real-time Exception: </strong>The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or</p></li><li><p>
<strong class="sc-handle">Essential Exception: </strong>The time limit is <a title="definition: essential" href="#essentialdef" class="termref">essential</a> and extending it would invalidate the activity; or
</p></li><li><p>
<strong class="sc-handle">20 Hour Exception: </strong>The time limit is longer than 20 hours.
</p></li></ul><div class="note"><p class="prefix"><em>Note: </em>This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with <a href="#consistent-behavior-receive-focus">
Success Criterion 3.2.1</a>, which puts limits on changes of content or context as a result of user action.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-time-limits-required-behaviors" class="HTMlink" title="How to Meet Success Criterion 2.2.1">How to Meet 2.2.1</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-required-behaviors.html" class="HTMlink" title="Understanding Success Criterion 2.2.1">Understanding 2.2.1</a></p></div></div><div class="sc" id="time-limits-pause"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.2.2 Pause, Stop, Hide:</strong>
For moving, <a title="definition: blinking" href="#blinksdef" class="termref">blinking</a>, scrolling, or auto-updating information, all of the following are true:
(Level A)
</p><ul><li><p><strong class="sc-handle">Moving, blinking, scrolling: </strong>For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to <a title="definition: paused" href="#pauseddef" class="termref">pause</a>, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is <a title="definition: essential" href="#essentialdef" class="termref">essential</a>; and</p></li><li><p><strong class="sc-handle">Auto-updating: </strong>For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.</p></li></ul><div class="note"><p class="prefix"><em>Note 1:
</em>For requirements related to flickering or flashing content, refer to <a href="#seizure">Guideline 2.3</a>.</p><p class="prefix"><em>Note 2:
</em>Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See <a href="#cc5">Conformance Requirement 5: Non-Interference</a>.</p><p class="prefix"><em>Note 3:
</em>Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.
</p><p class="prefix"><em>Note 4:
</em>An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-time-limits-pause" class="HTMlink" title="How to Meet Success Criterion 2.2.2">How to Meet 2.2.2</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-pause.html" class="HTMlink" title="Understanding Success Criterion 2.2.2">Understanding 2.2.2</a></p></div></div></div><div class="additional"><div class="sc" id="time-limits-no-exceptions"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.2.3 No Timing:</strong> Timing is not an <a title="definition: essential" href="#essentialdef" class="termref">essential</a> part of the event or activity presented by the content, except for non-interactive <a title="definition: synchronized media" href="#synchronizedmediadef" class="termref">synchronized media</a> and
<a title="definition: real-time event" href="#real-time-eventsdef" class="termref">real-time events</a>.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-time-limits-no-exceptions" class="HTMlink" title="How to Meet Success Criterion 2.2.3">How to Meet 2.2.3</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-no-exceptions.html" class="HTMlink" title="Understanding Success Criterion 2.2.3">Understanding 2.2.3</a></p></div></div><div class="sc" id="time-limits-postponed"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.2.4 Interruptions:</strong> Interruptions can be postponed or suppressed by the user, except interruptions involving an <a title="definition: emergency" href="#emergencydef" class="termref">emergency</a>.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-time-limits-postponed" class="HTMlink" title="How to Meet Success Criterion 2.2.4">How to Meet 2.2.4</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-postponed.html" class="HTMlink" title="Understanding Success Criterion 2.2.4">Understanding 2.2.4</a></p></div></div><div class="sc" id="time-limits-server-timeout"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.2.5 Re-authenticating:</strong> When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-time-limits-server-timeout" class="HTMlink" title="How to Meet Success Criterion 2.2.5">How to Meet 2.2.5</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-server-timeout.html" class="HTMlink" title="Understanding Success Criterion 2.2.5">Understanding 2.2.5</a></p></div></div></div></div><div class="div3"><div class="guideline"><h3><a name="seizure" id="seizure"> </a> Guideline 2.3 Seizures: Do not design content in a way that is known to cause seizures.</h3><p class="und-gl-link"><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/seizure.html">Understanding Guideline 2.3</a></p></div><div class="req"><div class="sc" id="seizure-does-not-violate"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.3.1 Three Flashes or Below Threshold:</strong>
<a title="definition: Web page" href="#webpagedef" class="termref">Web pages</a> do not contain anything that flashes more than three times in any one second period, or the <a title="definition: flash" href="#flash-def" class="termref">flash</a> is below the <a title="definition: general flash and red flash thresholds" href="#general-thresholddef" class="termref">general flash and red flash thresholds</a>.
(Level A)
</p><div class="note"><p class="prefix"><em>Note: </em>Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See <a href="#cc5">Conformance Requirement 5: Non-Interference</a>.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-seizure-does-not-violate" class="HTMlink" title="How to Meet Success Criterion 2.3.1">How to Meet 2.3.1</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/seizure-does-not-violate.html" class="HTMlink" title="Understanding Success Criterion 2.3.1">Understanding 2.3.1</a></p></div></div></div><div class="additional"><div class="sc" id="seizure-three-times"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.3.2 Three Flashes:</strong>
<a title="definition: Web page" href="#webpagedef" class="termref">Web pages</a> do not contain anything that <a title="definition: flash" href="#flash-def" class="termref">flashes</a> more than three times in any one second period.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-seizure-three-times" class="HTMlink" title="How to Meet Success Criterion 2.3.2">How to Meet 2.3.2</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/seizure-three-times.html" class="HTMlink" title="Understanding Success Criterion 2.3.2">Understanding 2.3.2</a></p></div></div></div></div><div class="div3"><div class="guideline"><h3><a name="navigation-mechanisms" id="navigation-mechanisms"> </a> Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
</h3><p class="und-gl-link"><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms.html">Understanding Guideline 2.4</a></p></div><div class="req"><div class="sc" id="navigation-mechanisms-skip"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.4.1 Bypass Blocks:</strong> A <a title="definition: mechanism" href="#mechanismdef" class="termref">mechanism</a> is available to bypass blocks of content that are repeated on multiple <a title="definition: Web page" href="#webpagedef" class="termref">Web pages</a>.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-navigation-mechanisms-skip" class="HTMlink" title="How to Meet Success Criterion 2.4.1">How to Meet 2.4.1</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-skip.html" class="HTMlink" title="Understanding Success Criterion 2.4.1">Understanding 2.4.1</a></p></div></div><div class="sc" id="navigation-mechanisms-title"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.4.2 Page Titled:</strong>
<a title="definition: Web page" href="#webpagedef" class="termref">Web pages</a> have titles that describe topic or purpose.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-navigation-mechanisms-title" class="HTMlink" title="How to Meet Success Criterion 2.4.2">How to Meet 2.4.2</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-title.html" class="HTMlink" title="Understanding Success Criterion 2.4.2">Understanding 2.4.2</a></p></div></div><div class="sc" id="navigation-mechanisms-focus-order"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.4.3 Focus Order:</strong> If a <a title="definition: Web page" href="#webpagedef" class="termref">Web page</a> can be <a title="definition: navigated sequentially" href="#nav-seqdef" class="termref">navigated sequentially</a> and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-navigation-mechanisms-focus-order" class="HTMlink" title="How to Meet Success Criterion 2.4.3">How to Meet 2.4.3</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html" class="HTMlink" title="Understanding Success Criterion 2.4.3">Understanding 2.4.3</a></p></div></div><div class="sc" id="navigation-mechanisms-refs"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.4.4 Link Purpose (In Context):</strong>
The <a title="definition: link purpose" href="#linkpurposedef" class="termref">purpose of each link</a> can be determined from the link text alone or from the link text together with its <a title="definition: programmatically determined link context" href="#pdlinkcontextdef" class="termref">programmatically determined link context</a>, except where the purpose of the link would be <a title="definition: ambiguous to users in general" href="#ambiguouslinkdef" class="termref">ambiguous to users in general</a>.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-navigation-mechanisms-refs" class="HTMlink" title="How to Meet Success Criterion 2.4.4">How to Meet 2.4.4</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html" class="HTMlink" title="Understanding Success Criterion 2.4.4">Understanding 2.4.4</a></p></div></div></div><div class="bp"><div class="sc" id="navigation-mechanisms-mult-loc"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.4.5 Multiple Ways:</strong> More than one way is available to locate a <a title="definition: Web page" href="#webpagedef" class="termref">Web page</a>
within a <a title="definition: set of Web pages" href="#set-of-web-pagesdef" class="termref">set of Web pages</a>
except where the Web Page is the result of, or a step in, a <a title="definition: process" href="#processdef" class="termref">process</a>.
(Level AA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-navigation-mechanisms-mult-loc" class="HTMlink" title="How to Meet Success Criterion 2.4.5">How to Meet 2.4.5</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-mult-loc.html" class="HTMlink" title="Understanding Success Criterion 2.4.5">Understanding 2.4.5</a></p></div></div><div class="sc" id="navigation-mechanisms-descriptive"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.4.6 Headings and Labels:</strong>
Headings and <a title="definition: label" href="#labeldef" class="termref">labels</a> describe topic or purpose.
(Level AA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-navigation-mechanisms-descriptive" class="HTMlink" title="How to Meet Success Criterion 2.4.6">How to Meet 2.4.6</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-descriptive.html" class="HTMlink" title="Understanding Success Criterion 2.4.6">Understanding 2.4.6</a></p></div></div><div class="sc" id="navigation-mechanisms-focus-visible"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.4.7 Focus Visible:</strong> Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
(Level AA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-navigation-mechanisms-focus-visible" class="HTMlink" title="How to Meet Success Criterion 2.4.7">How to Meet 2.4.7</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html" class="HTMlink" title="Understanding Success Criterion 2.4.7">Understanding 2.4.7</a></p></div></div></div><div class="additional"><div class="sc" id="navigation-mechanisms-location"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.4.8 Location:</strong> Information about the user's location within a <a title="definition: set of Web pages" href="#set-of-web-pagesdef" class="termref">set of Web pages</a> is available.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-navigation-mechanisms-location" class="HTMlink" title="How to Meet Success Criterion 2.4.8">How to Meet 2.4.8</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-location.html" class="HTMlink" title="Understanding Success Criterion 2.4.8">Understanding 2.4.8</a></p></div></div><div class="sc" id="navigation-mechanisms-link"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.4.9 Link Purpose (Link Only):</strong>
A <a title="definition: mechanism" href="#mechanismdef" class="termref">mechanism</a> is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be <a title="definition: ambiguous to users in general" href="#ambiguouslinkdef" class="termref">ambiguous to users in general</a>.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-navigation-mechanisms-link" class="HTMlink" title="How to Meet Success Criterion 2.4.9">How to Meet 2.4.9</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-link.html" class="HTMlink" title="Understanding Success Criterion 2.4.9">Understanding 2.4.9</a></p></div></div><div class="sc" id="navigation-mechanisms-headings"><div class="scinner"><p class="sctxt"><strong class="sc-handle">2.4.10 Section Headings:</strong>
<a title="definition: section" href="#sectiondef" class="termref">Section</a> headings are used to organize the content.
(Level AAA)
</p><div class="note"><p class="prefix"><em>Note 1:
</em>"Heading" is used in its general sense and includes titles and other ways to add a heading to different types of content.
</p><p class="prefix"><em>Note 2:
</em>This success criterion covers sections within writing, not <a title="definition: user interface component" href="#user-interface-componentdef" class="termref">user interface components</a>. User Interface components are covered under <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/#ensure-compat-rsv">Success Criterion 4.1.2</a>.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-navigation-mechanisms-headings" class="HTMlink" title="How to Meet Success Criterion 2.4.10">How to Meet 2.4.10</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-headings.html" class="HTMlink" title="Understanding Success Criterion 2.4.10">Understanding 2.4.10</a></p></div></div></div></div></div><div class="div2"> <h2 class="principle"><a name="understandable" id="understandable"> </a>Principle 3: Understandable - Information and the operation of user interface must be understandable.</h2><div class="div3"><div class="guideline"><h3><a name="meaning" id="meaning"> </a> Guideline 3.1 Readable:
Make text content readable and understandable.
</h3><p class="und-gl-link"><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning.html">Understanding Guideline 3.1</a></p></div><div class="req"><div class="sc" id="meaning-doc-lang-id"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.1.1 Language of Page:</strong> The default
<a title="definition: human language" href="#human-langdef" class="termref">human language</a>
of each
<a title="definition: Web page" href="#webpagedef" class="termref">Web page</a>
can be <a title="definition: programmatically determined (programmatically determinable)" href="#programmaticallydetermineddef" class="termref">programmatically determined</a>.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-meaning-doc-lang-id" class="HTMlink" title="How to Meet Success Criterion 3.1.1">How to Meet 3.1.1</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-doc-lang-id.html" class="HTMlink" title="Understanding Success Criterion 3.1.1">Understanding 3.1.1</a></p></div></div></div><div class="bp"><div class="sc" id="meaning-other-lang-id"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.1.2 Language of Parts:</strong> The <a title="definition: human language" href="#human-langdef" class="termref">human language</a> of each passage or phrase in the
content can be <a title="definition: programmatically determined (programmatically determinable)" href="#programmaticallydetermineddef" class="termref">programmatically determined</a>
except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.
(Level AA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-meaning-other-lang-id" class="HTMlink" title="How to Meet Success Criterion 3.1.2">How to Meet 3.1.2</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-other-lang-id.html" class="HTMlink" title="Understanding Success Criterion 3.1.2">Understanding 3.1.2</a></p></div></div></div><div class="additional"><div class="sc" id="meaning-idioms"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.1.3 Unusual Words:</strong> A <a title="definition: mechanism" href="#mechanismdef" class="termref">mechanism</a> is available for identifying specific definitions of words or phrases <a title="definition: used in an unusual or restricted way" href="#unusual-restricteddef" class="termref">used in an unusual or restricted way</a>, including <a title="definition: idiom" href="#idiomsdef" class="termref">idioms</a> and <a title="definition: jargon" href="#jargondef" class="termref">jargon</a>.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-meaning-idioms" class="HTMlink" title="How to Meet Success Criterion 3.1.3">How to Meet 3.1.3</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-idioms.html" class="HTMlink" title="Understanding Success Criterion 3.1.3">Understanding 3.1.3</a></p></div></div><div class="sc" id="meaning-located"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.1.4 Abbreviations:</strong> A <a title="definition: mechanism" href="#mechanismdef" class="termref">mechanism</a> for identifying the expanded form or meaning of <a title="definition: abbreviation" href="#abbreviationsdef" class="termref">abbreviations</a> is available.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-meaning-located" class="HTMlink" title="How to Meet Success Criterion 3.1.4">How to Meet 3.1.4</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-located.html" class="HTMlink" title="Understanding Success Criterion 3.1.4">Understanding 3.1.4</a></p></div></div><div class="sc" id="meaning-supplements"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.1.5 Reading Level:</strong> When text requires reading ability more advanced than the <a title="definition: lower secondary education level" href="#lowseceddef" class="termref">lower secondary education level</a> after removal of proper names and titles, <a title="definition: supplemental content" href="#suppcontentdef" class="termref">supplemental content</a>,
or a version
that does not require reading ability more advanced than the lower secondary education level, is available.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-meaning-supplements" class="HTMlink" title="How to Meet Success Criterion 3.1.5">How to Meet 3.1.5</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-supplements.html" class="HTMlink" title="Understanding Success Criterion 3.1.5">Understanding 3.1.5</a></p></div></div><div class="sc" id="meaning-pronunciation"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.1.6 Pronunciation:</strong> A <a title="definition: mechanism" href="#mechanismdef" class="termref">mechanism</a> is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-meaning-pronunciation" class="HTMlink" title="How to Meet Success Criterion 3.1.6">How to Meet 3.1.6</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-pronunciation.html" class="HTMlink" title="Understanding Success Criterion 3.1.6">Understanding 3.1.6</a></p></div></div></div></div><div class="div3"><div class="guideline"><h3><a name="consistent-behavior" id="consistent-behavior"> </a> Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
</h3><p class="und-gl-link"><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior.html">Understanding Guideline 3.2</a></p></div><div class="req"><div class="sc" id="consistent-behavior-receive-focus"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.2.1 On Focus:</strong> When any component receives focus, it does not
initiate a <a title="definition: changes of context" href="#context-changedef" class="termref">change of context</a>.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-consistent-behavior-receive-focus" class="HTMlink" title="How to Meet Success Criterion 3.2.1">How to Meet 3.2.1</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-receive-focus.html" class="HTMlink" title="Understanding Success Criterion 3.2.1">Understanding 3.2.1</a></p></div></div><div class="sc" id="consistent-behavior-unpredictable-change"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.2.2 On Input:</strong> Changing the setting of any
<a title="definition: user interface component" href="#user-interface-componentdef" class="termref">user interface component</a>
does not automatically cause a <a title="definition: changes of context" href="#context-changedef" class="termref">change of context</a>
unless the user has been advised of the behavior before using the component.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-consistent-behavior-unpredictable-change" class="HTMlink" title="How to Meet Success Criterion 3.2.2">How to Meet 3.2.2</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-unpredictable-change.html" class="HTMlink" title="Understanding Success Criterion 3.2.2">Understanding 3.2.2</a></p></div></div></div><div class="bp"><div class="sc" id="consistent-behavior-consistent-locations"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.2.3 Consistent Navigation:</strong> Navigational mechanisms that are repeated on multiple <a title="definition: Web page" href="#webpagedef" class="termref">Web pages</a> within a <a title="definition: set of Web pages" href="#set-of-web-pagesdef" class="termref">set of Web pages</a>
occur in the <a title="definition: same relative order" href="#samerelorderdef" class="termref">same relative order</a> each time they are repeated, unless a change is initiated by the user.
(Level AA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-consistent-behavior-consistent-locations" class="HTMlink" title="How to Meet Success Criterion 3.2.3">How to Meet 3.2.3</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-consistent-locations.html" class="HTMlink" title="Understanding Success Criterion 3.2.3">Understanding 3.2.3</a></p></div></div><div class="sc" id="consistent-behavior-consistent-functionality"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.2.4 Consistent Identification:</strong> Components that have the <a title="definition: same functionality " href="#samefunctionalitydef" class="termref">same functionality</a> within a set of <a title="definition: Web page" href="#webpagedef" class="termref">Web pages</a> are identified consistently.
(Level AA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-consistent-behavior-consistent-functionality" class="HTMlink" title="How to Meet Success Criterion 3.2.4">How to Meet 3.2.4</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-consistent-functionality.html" class="HTMlink" title="Understanding Success Criterion 3.2.4">Understanding 3.2.4</a></p></div></div></div><div class="additional"><div class="sc" id="consistent-behavior-no-extreme-changes-context"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.2.5 Change on Request:</strong>
<a title="definition: changes of context" href="#context-changedef" class="termref">Changes of context</a> are initiated only by user request or a <a title="definition: mechanism" href="#mechanismdef" class="termref">mechanism</a> is available to turn off such changes.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-consistent-behavior-no-extreme-changes-context" class="HTMlink" title="How to Meet Success Criterion 3.2.5">How to Meet 3.2.5</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-no-extreme-changes-context.html" class="HTMlink" title="Understanding Success Criterion 3.2.5">Understanding 3.2.5</a></p></div></div></div></div><div class="div3"><div class="guideline"><h3><a name="minimize-error" id="minimize-error"> </a> Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
</h3><p class="und-gl-link"><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error.html">Understanding Guideline 3.3</a></p></div><div class="req"><div class="sc" id="minimize-error-identified"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.3.1 Error Identification:</strong> If an <a title="definition: input error" href="#input-errordef" class="termref">input error</a> is automatically detected, the item that is in error is identified and the error is
described to the user in text.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-minimize-error-identified" class="HTMlink" title="How to Meet Success Criterion 3.3.1">How to Meet 3.3.1</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-identified.html" class="HTMlink" title="Understanding Success Criterion 3.3.1">Understanding 3.3.1</a></p></div></div><div class="sc" id="minimize-error-cues"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.3.2 Labels or Instructions:</strong>
<a title="definition: label" href="#labeldef" class="termref">Labels</a> or instructions are provided when content requires user input.
(Level A)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-minimize-error-cues" class="HTMlink" title="How to Meet Success Criterion 3.3.2">How to Meet 3.3.2</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html" class="HTMlink" title="Understanding Success Criterion 3.3.2">Understanding 3.3.2</a></p></div></div></div><div class="bp"><div class="sc" id="minimize-error-suggestions"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.3.3 Error Suggestion:</strong> If an <a title="definition: input error" href="#input-errordef" class="termref">input error</a> is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.
(Level AA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-minimize-error-suggestions" class="HTMlink" title="How to Meet Success Criterion 3.3.3">How to Meet 3.3.3</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-suggestions.html" class="HTMlink" title="Understanding Success Criterion 3.3.3">Understanding 3.3.3</a></p></div></div><div class="sc" id="minimize-error-reversible"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.3.4 Error Prevention (Legal, Financial, Data):</strong> For <a title="definition: Web page" href="#webpagedef" class="termref">Web pages</a> that cause <a title="definition: legal commitments" href="#legalcommitmentsdef" class="termref">legal commitments</a> or financial transactions for the user to occur, that modify or delete <a title="definition: user-controllable" href="#user-controllabledef" class="termref">user-controllable</a> data in data storage systems, or that submit user test responses, at least one of the following is true:
(Level AA)
</p><ol class="enumar"><li><p>
<strong class="sc-handle">Reversible: </strong> Submissions are reversible.</p></li><li><p>
<strong class="sc-handle">Checked: </strong> Data entered by the user is checked for <a title="definition: input error" href="#input-errordef" class="termref">input errors</a> and the user is provided an opportunity to correct them.</p></li><li><p>
<strong class="sc-handle">Confirmed: </strong> A <a title="definition: mechanism" href="#mechanismdef" class="termref">mechanism</a> is available for reviewing, confirming, and correcting information before finalizing the submission.</p></li></ol></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-minimize-error-reversible" class="HTMlink" title="How to Meet Success Criterion 3.3.4">How to Meet 3.3.4</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-reversible.html" class="HTMlink" title="Understanding Success Criterion 3.3.4">Understanding 3.3.4</a></p></div></div></div><div class="additional"><div class="sc" id="minimize-error-context-help"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.3.5 Help:</strong>
<a title="definition: context-sensitive help" href="#context-sensitivehelpdef" class="termref">Context-sensitive help</a> is available.
(Level AAA)
</p></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-minimize-error-context-help" class="HTMlink" title="How to Meet Success Criterion 3.3.5">How to Meet 3.3.5</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-context-help.html" class="HTMlink" title="Understanding Success Criterion 3.3.5">Understanding 3.3.5</a></p></div></div><div class="sc" id="minimize-error-reversible-all"><div class="scinner"><p class="sctxt"><strong class="sc-handle">3.3.6 Error Prevention (All):</strong> For <a title="definition: Web page" href="#webpagedef" class="termref">Web pages</a> that require the user to submit information, at least one of the following is true:
(Level AAA)
</p><ol class="enumar"><li><p>
<strong class="sc-handle">Reversible: </strong> Submissions are reversible.</p></li><li><p>
<strong class="sc-handle">Checked: </strong> Data entered by the user is checked for <a title="definition: input error" href="#input-errordef" class="termref">input errors</a> and the user is provided an opportunity to correct them.</p></li><li><p>
<strong class="sc-handle">Confirmed: </strong> A <a title="definition: mechanism" href="#mechanismdef" class="termref">mechanism</a> is available for reviewing, confirming, and correcting information before finalizing the submission.</p></li></ol></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-minimize-error-reversible-all" class="HTMlink" title="How to Meet Success Criterion 3.3.6">How to Meet 3.3.6</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-reversible-all.html" class="HTMlink" title="Understanding Success Criterion 3.3.6">Understanding 3.3.6</a></p></div></div></div></div></div><div class="div2"> <h2 class="principle"><a name="robust" id="robust"> </a>Principle 4: Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.</h2><div class="div3"><div class="guideline"><h3><a name="ensure-compat" id="ensure-compat"> </a> Guideline 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies.</h3><p class="und-gl-link"><a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat.html">Understanding Guideline 4.1</a></p></div><div class="req"><div class="sc" id="ensure-compat-parses"><div class="scinner"><p class="sctxt"><strong class="sc-handle">4.1.1 Parsing:</strong> In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.
(Level A)
</p><div class="note"><p class="prefix"><em>Note: </em>Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-ensure-compat-parses" class="HTMlink" title="How to Meet Success Criterion 4.1.1">How to Meet 4.1.1</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-parses.html" class="HTMlink" title="Understanding Success Criterion 4.1.1">Understanding 4.1.1</a></p></div></div><div class="sc" id="ensure-compat-rsv"><div class="scinner"><p class="sctxt"><strong class="sc-handle">4.1.2 Name, Role, Value:</strong> For all <a title="definition: user interface component" href="#user-interface-componentdef" class="termref">user interface components</a> (including but not limited to: form elements, links and components generated by scripts), the <a title="definition: name" href="#namedef" class="termref">name</a> and <a title="definition: role" href="#roledef" class="termref">role</a> can be <a title="definition: programmatically determined (programmatically determinable)" href="#programmaticallydetermineddef" class="termref">programmatically determined</a>; states, properties, and values that can be set by the user can be <a title="definition: programmatically set" href="#programmaticallysetdef" class="termref">programmatically set</a>; and notification of changes to these items is available to <a title="definition: user agent" href="#useragentdef" class="termref">user agents</a>, including <a title="definition: assistive technology (as used in this document)" href="#atdef" class="termref">assistive technologies</a>.
(Level A)
</p><div class="note"><p class="prefix"><em>Note: </em>This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.</p></div></div><div class="doclinks"><p class="supportlinks"><a href="http://www.w3.org/WAI/WCAG20/quickref/#qr-ensure-compat-rsv" class="HTMlink" title="How to Meet Success Criterion 4.1.2">How to Meet 4.1.2</a> <span class="screenreader">|</span> <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html" class="HTMlink" title="Understanding Success Criterion 4.1.2">Understanding 4.1.2</a></p></div></div></div></div></div></div><div class="div1">
<h2><a name="conformance" id="conformance"> </a>Conformance</h2><p>This section is <a title="definition: normative" href="#normativedef" class="termref">normative</a>. </p><p>This section lists requirements for <a title="definition: conformance" href="#conformancedef" class="termref">conformance</a> to WCAG 2.0. It also gives information about how to make conformance claims, which are optional. Finally, it describes what it means to be <a title="definition: accessibility supported" href="#accessibility-supporteddef" class="termref">accessibility supported</a>, since only accessibility-supported ways of using technologies can be <a title="definition: relied upon (technologies that are)" href="#reliedupondef" class="termref">relied upon</a> for conformance. <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html">Understanding Conformance</a> includes further explanation of the accessibility-supported concept.</p><div class="div2"> <h3><a name="conformance-reqs" id="conformance-reqs"> </a>Conformance Requirements</h3><p>In order for a Web page to conform to WCAG 2.0, all of the following conformance requirements must be satisfied:</p><div class="div3"><a name="cc1" id="cc1"> </a><p class="sctxt"><strong class="sc-handle">1. Conformance Level:</strong> One of the following levels of conformance is met in full.
</p><ul><li><p>
<strong class="sc-handle">Level A: </strong>For Level A conformance (the minimum level of conformance), the <a title="definition: Web page" href="#webpagedef" class="termref">Web page</a> <a title="definition: satisfies a success criterion" href="#satisfiesdef" class="termref">satisfies</a> all the Level A Success Criteria, or a <a title="definition: conforming alternate version" href="#conforming-alternate-versiondef" class="termref">conforming alternate version</a> is provided.
</p></li><li><p>
<strong class="sc-handle">Level AA: </strong>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.
</p></li><li><p>
<strong class="sc-handle">Level AAA: </strong>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.
</p></li></ul><div class="note"><p class="prefix"><em>Note 1:
</em>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="prefix"><em>Note 2:
</em>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></div></div><div class="div3"><a name="cc2" id="cc2"> </a><p class="sctxt"><strong class="sc-handle">2. Full pages:</strong> <a title="definition: conformance" href="#conformancedef" class="termref">Conformance</a> (and conformance level) is for full <a title="definition: Web page" href="#webpagedef" class="termref">Web page(s)</a> only, and cannot be achieved if part of a Web page is excluded.
</p><div class="note"><p class="prefix"><em>Note 1:
</em>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="prefix"><em>Note 2:
</em><span>Authors of </span>Web pages that cannot conform due to content outside of the author's control may consider a <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/#conformance-partial">Statement of Partial Conformance</a>.</p></div></div><div class="div3"><a name="cc3" id="cc3"> </a><p class="sctxt"><strong class="sc-handle">3. Complete processes:</strong> When a <a title="definition: Web page" href="#webpagedef" class="termref">Web page</a> is one of a series of Web pages presenting a <a title="definition: process" href="#processdef" class="termref">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><div class="example"><p class="prefix"><em>Example: </em>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></div></div><div class="div3"><a name="cc4" id="cc4"> </a><p class="sctxt"><strong class="sc-handle">4. Only Accessibility-Supported Ways of Using Technologies:</strong> Only
<a title="definition: accessibility supported" href="#accessibility-supporteddef" class="termref">accessibility-supported</a> ways of using <a title="definition: technology (Web content)" href="#technologydef" class="termref">technologies</a> are <a title="definition: relied upon (technologies that are)" href="#reliedupondef" class="termref">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="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-accessibility-support-head">Understanding accessibility support</a>.)
</p></div><div class="div3"><a name="cc5" id="cc5"> </a><p class="sctxt"><strong class="sc-handle">5. Non-Interference:</strong> If <a title="definition: technology (Web content)" href="#technologydef" class="termref">
technologies</a> are used in a way that is not <a title="definition: accessibility supported" href="#accessibility-supporteddef" class="termref">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 title="definition: Web page" href="#webpagedef" class="termref">Web page</a> as a whole continues to meet the conformance requirements under each of the following conditions:
</p><ol class="enumar"><li><p>when any technology that is not <a title="definition: relied upon (technologies that are)" href="#reliedupondef" class="termref">relied upon</a> is turned on in a user agent,</p></li><li><p>when any technology that is not relied upon is turned off in a user agent, and</p></li><li><p>when any technology that is not relied upon is not supported by a user agent</p></li></ol><p class="sctxt">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><p><strong>1.4.2 - Audio Control</strong>,</p></li><li><p><strong>2.1.2 - No Keyboard Trap</strong>,</p></li><li><p><strong>2.3.1 - Three Flashes or Below Threshold</strong>, and</p></li><li><p><strong>2.2.2 - Pause, Stop, Hide</strong>.</p></li></ul></div><div class="div3"><div class="note"><p class="prefix"><em>Note: </em>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></div><p class="sctxt">For more information, including examples, see <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-conformance-requirements-head">Understanding Conformance Requirements</a>.
</p></div></div><div class="div2"> <h3><a name="conformance-claims" id="conformance-claims"> </a>Conformance Claims (Optional)
</h3><p>Conformance is defined only for <a title="definition: Web page" href="#webpagedef" class="termref">Web pages</a>. However, a conformance claim may be made to cover one page, a series of pages, or multiple related Web pages.</p><div class="div3"><h4><a name="conformance-required" id="conformance-required"> </a>Required Components of a Conformance Claim</h4><p class="sctxt">Conformance claims are <strong>not required</strong>. Authors can conform to WCAG 2.0 without making a claim. However, if a conformance claim is made, then the conformance claim <strong>must</strong> include the following information:</p><ol class="enumar"><li><p>
<strong>Date</strong> of the claim</p></li><li><p>
<strong>Guidelines title, version and URI
</strong> "Web Content Accessibility Guidelines 2.0 at <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/">http://www.w3.org/TR/2008/REC-WCAG20-20081211/</a>"
</p></li><li><p>
<strong>Conformance level</strong> satisfied: (Level A, AA or AAA)
</p></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><div class="note"><p class="prefix"><em>Note 1:
</em>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="prefix"><em>Note 2:
</em>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></div></li><li><p>A list of the <strong>
<a title="definition: technology (Web content)" href="#technologydef" class="termref">Web content technologies</a> <a title="definition: relied upon (technologies that are)" href="#reliedupondef" class="termref">relied upon</a></strong>.</p></li></ol><div class="note"><p class="prefix"><em>Note: </em>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></div></div><div class="div3"><h4><a name="conformance-optional" id="conformance-optional"> </a>Optional Components of a Conformance Claim </h4><p class="sctxt">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><p>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.
</p></li><li><p>A list of the specific technologies that are "<em>used but not <a title="definition: relied upon (technologies that are)" href="#reliedupondef" class="termref">relied upon</a></em>."</p></li><li><p>A list of user agents, including assistive technologies that were used to test the content.
</p></li><li><p>Information about any additional steps taken that go beyond the success criteria to enhance accessibility.</p></li><li><p>A machine-readable metadata version of the list of specific technologies that are <a title="definition: relied upon (technologies that are)" href="#reliedupondef" class="termref">relied upon</a>.
</p></li><li><p>A machine-readable metadata version of the conformance claim.</p></li></ul><div class="note"><p class="prefix"><em>Note 1:
</em>Refer to <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-conformance-claims-head">Understanding Conformance Claims</a> for more information and example conformance claims.</p><p class="prefix"><em>Note 2:
</em>Refer to <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/appendixC.html#understanding-metadata">Understanding Metadata</a> for more information about the use of metadata in conformance claims.</p></div></div></div><div class="div2"> <h3><a name="conformance-partial" id="conformance-partial"> </a>Statement of Partial Conformance - Third Party Content</h3><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 class="sctxt">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 class="enumar"><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.0 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 class="enumla"><li><p>It is not content that is under the author's control.</p></li><li><p>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.)</p></li></ol></li></ol></div><div class="div2"> <h3><a name="conformance-partial-lang" id="conformance-partial-lang"> </a>Statement of Partial Conformance - Language</h3><p> A "statement of partial conformance due to language" may be made when the page does not conform, but would conform if <a title="definition: accessibility supported" href="#accessibility-supporteddef" class="termref">accessibility support</a> existed for (all of) the language(s) used on the page. The form of that statement would be, "This page<span> does not conform, but</span> would conform to WCAG 2.0 at level X if accessibility support existed for the following language(s):"</p></div></div></div><div class="back"><div class="div1">
<h2><a name="glossary" id="glossary"> </a>Appendix A: Glossary</h2><p>This section is <a title="definition: normative" href="#normativedef" class="termref">normative</a>. </p><dl><dt class="label"><a name="abbreviationsdef" id="abbreviationsdef"> </a>abbreviation</dt><dd><p>shortened form of a word, phrase, or name where the abbreviation has not become part of the language
</p><div class="note"><p class="prefix"><em>Note 1:
</em>This includes initialisms and acronyms where:</p><ol class="enumar"><li><p>
<strong>initialisms</strong> are shortened forms of a name or phrase made from the initial letters of words or syllables contained in that name or phrase</p><div class="note"><p class="prefix"><em>Note 1:
</em>Not defined in all languages. </p></div><div class="example"><p class="prefix"><em>Example 1:
</em>SNCF is a French initialism that contains the initial letters of the <span lang="fr" xml:lang="fr">Société Nationale des Chemins de Fer</span>, the French national railroad. </p><p class="prefix"><em>Example 2:
</em>ESP is an initialism for extrasensory perception.</p></div></li><li><p>
<strong>acronyms</strong>
are abbreviated forms made from the initial letters or parts of other words (in a name or phrase) which may be pronounced as a word
</p><div class="example"><p class="prefix"><em>Example: </em>NOAA is an acronym made from the initial letters of the National Oceanic and Atmospheric Administration in the United States.</p></div></li></ol><p class="prefix"><em>Note 2:
</em>Some companies have adopted what used to be an initialism as their company name. In these cases, the new name of the company is the letters (for example, Ecma) and the word is no longer considered an abbreviation.</p></div></dd><dt class="label"><a name="accessibility-supporteddef" id="accessibility-supporteddef"> </a>accessibility supported</dt><dd><p>supported by users' <a title="definition: assistive technology (as used in this document)" href="#atdef" class="termref">assistive technologies</a> as well as the accessibility features in browsers and other <a title="definition: user agent" href="#useragentdef" class="termref">user agents</a>
</p><p>To qualify as an accessibility-supported use of a Web content technology (or feature of a technology), both 1 and 2 must be satisfied for a Web content technology (or feature):
</p><ol class="enumar"><li><p>
<strong>The way that the <a title="definition: technology (Web content)" href="#technologydef" class="termref">Web content technology</a> is used must be supported by users' assistive technology (AT).</strong> This means that the way that the technology is used has been tested for interoperability with users' assistive technology in the <a title="definition: human language" href="#human-langdef" class="termref">human language(s)</a> of the content,</p><p>
<strong>AND</strong>
</p></li><li><p>
<strong>The Web content technology must have accessibility-supported user agents that are available to users.</strong> This means that at least one of the following four statements is true:</p><ol class="enumla"><li><p>The technology is supported natively in widely-distributed user agents that are also accessibility supported (such as HTML and CSS); </p><p>
<strong>OR</strong>
</p></li><li><p>The technology is supported in a widely-distributed plug-in that is also accessibility supported; </p><p>
<strong>OR</strong>
</p></li><li><p>The content is available in a closed environment, such as a university or corporate network, where the user agent required by the technology and used by the organization is also accessibility supported; </p><p>
<strong>OR</strong>
</p></li><li><p>The user agent(s) that support the technology are accessibility supported and are available for download or purchase in a way that:</p><ul><li><p>does not cost a person with a disability any more than a person without a disability <strong>and</strong></p></li><li><p>is as easy to find and obtain for a person with a disability as it is for a person without disabilities.</p></li></ul></li></ol></li></ol><div class="note"><p class="prefix"><em>Note 1:
</em>The WCAG Working group and the W3C do not specify which or how much support by assistive technologies there must be for a particular use of a Web technology in order for it to be classified as accessibility supported. (See <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-support-level-head">Level of Assistive Technology Support Needed for "Accessibility Support"</a>.)</p><p class="prefix"><em>Note 2:
</em>Web technologies can be used in ways that are not accessibility supported as long as they are not <a title="definition: relied upon (technologies that are)" href="#reliedupondef" class="termref">relied upon</a> and the page as a whole meets the conformance requirements, including <a href="#cc4">Conformance Requirement 4: Only Accessibility-Supported Ways of Using Technologies</a> and <a href="#cc5">Conformance Requirement 5: Non-Interference</a>, are met.</p><p class="prefix"><em>Note 3:
</em>When a <a title="definition: technology (Web content)" href="#technologydef" class="termref">Web Technology</a> is used in a way that is "accessibility supported," it does not imply that the entire technology or all uses of the technology are supported. Most technologies, including HTML, lack support for at least one feature or use. Pages conform to WCAG only if the uses of the technology that are accessibility supported can be relied upon to meet WCAG requirements.</p><p class="prefix"><em>Note 4:
</em>When citing Web content technologies that have multiple versions, the version(s) supported should be specified.</p><p class="prefix"><em>Note 5:
</em>One way for authors to locate uses of a technology that are accessibility supported would be to consult compilations of uses that are documented to be accessibility supported. (See <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-documented-lists-head">Understanding Accessibility-Supported Web Technology Uses</a>.) Authors, companies, technology vendors, or others may document accessibility-supported ways of using Web content technologies. However, all ways of using technologies in the documentation would need to meet the definition of accessibility-supported Web content technologies above.
</p></div></dd><dt class="label"><a name="alt-time-based-mediadef" id="alt-time-based-mediadef"> </a>alternative for time-based media</dt><dd><p>document including correctly sequenced text descriptions of time-based visual and auditory information and providing a means for achieving the outcomes of any time-based interaction
</p><div class="note"><p class="prefix"><em>Note: </em>A screenplay used to create the synchronized media content would meet this definition only if it was corrected to accurately represent the final synchronized media after editing.</p></div></dd><dt class="label"><a name="ambiguouslinkdef" id="ambiguouslinkdef"> </a>ambiguous to users in general</dt><dd><p>the purpose cannot be determined from the link and all information of the Web page presented to the user simultaneously with the link (i.e., readers without disabilities would not know what a link would do until they activated it)</p><div class="example"><p class="prefix"><em>Example: </em>The word guava in the following sentence "One of the notable exports is guava" is a link. The link could lead to a definition of guava, a chart listing the quantity of guava exported or a photograph of people harvesting guava. Until the link is activated, all readers are unsure and the person with a disability is not at any disadvantage.</p></div></dd><dt class="label"><a name="asciiartdef" id="asciiartdef"> </a>ASCII art</dt><dd><p>picture created by a spatial arrangement of characters or glyphs (typically from the 95 printable characters defined by ASCII).
</p></dd><dt class="label"><a name="atdef" id="atdef"> </a>assistive technology (as used in this document)</dt><dd><p>hardware and/or software that acts as a <a title="definition: user agent" href="#useragentdef" class="termref">user agent</a>, or along with a mainstream user agent, to provide functionality to meet the requirements of users with disabilities that go beyond those offered by mainstream user agents
</p><div class="note"><p class="prefix"><em>Note 1:
</em>
functionality provided by assistive technology includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation mechanisms, and content transformations (e.g., to make tables more accessible).
</p><p class="prefix"><em>Note 2:
</em>Assistive technologies often communicate data and messages with mainstream user agents by using and monitoring <acronym title="Application Programming Interfaces">APIs</acronym>.
</p><p class="prefix"><em>Note 3:
</em>The distinction between mainstream user agents and assistive technologies is not absolute. Many mainstream user agents provide some features to assist individuals with disabilities. The basic difference is that mainstream user agents target broad and diverse audiences that usually include people with and without disabilities. Assistive technologies target narrowly defined populations of users with specific disabilities. The assistance provided by an assistive technology is more specific and appropriate to the needs of its target users. The mainstream user agent may provide important functionality to assistive technologies like retrieving Web content from program objects or parsing markup into identifiable bundles.
</p></div><div class="example"><p class="prefix"><em>Example: </em>Assistive technologies that are important in the context of this document include the following:</p><ul><li><p>screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc. in order to improve the visual readability of rendered text and images;</p></li><li><p>screen readers, which are used by people who are blind to read textual information through synthesized speech or braille;</p></li><li><p>text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech;</p></li><li><p>speech recognition software, which may be used by people who have some physical disabilities;</p></li><li><p>alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices.);</p></li><li><p>alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations.</p></li></ul></div></dd><dt class="label"><a name="audiodef" id="audiodef"> </a>audio</dt><dd><p>the technology of sound reproduction</p><div class="note"><p class="prefix"><em>Note: </em>Audio can be created synthetically (including speech synthesis), recorded from real world sounds, or both.</p></div></dd><dt class="label"><a name="audiodescdef" id="audiodescdef"> </a>audio description</dt><dd><p>narration added to the soundtrack to describe important visual details that cannot be understood from the main soundtrack alone </p><div class="note"><p class="prefix"><em>Note 1:
</em>
Audio description of <a title="definition: video" href="#videodef" class="termref">video</a> provides information about actions, characters, scene changes, on-screen text, and other visual content.
</p><p class="prefix"><em>Note 2:
</em>In standard audio description, narration is added during existing pauses in dialogue. (See also <a title="definition: extended audio description" href="#extended-addef" class="termref">extended audio description</a>.)</p><p class="prefix"><em>Note 3:
</em>Where all of the <a title="definition: video" href="#videodef" class="termref">video</a> information is already provided in existing <a title="definition: audio" href="#audiodef" class="termref">audio</a>, no additional audio description is necessary.</p><p class="prefix"><em>Note 4:
</em>Also called "video description" and "descriptive narration."</p></div></dd><dt class="label"><a name="audio-onlydef" id="audio-onlydef"> </a>audio-only</dt><dd><p>a time-based presentation that contains only <a title="definition: audio" href="#audiodef" class="termref">audio</a> (no <a title="definition: video" href="#videodef" class="termref">video</a> and no interaction)</p></dd><dt class="label"><a name="blinksdef" id="blinksdef"> </a>blinking</dt><dd><p>switch back and forth between two visual states in a way that is meant to draw attention
</p><div class="note"><p class="prefix"><em>Note: </em>See also <a title="definition: flash" href="#flash-def" class="termref">flash</a>. It is possible for something to be large enough and blink brightly enough at the right frequency to be also classified as a flash.
</p></div></dd><dt class="label"><a name="blockstextdef" id="blockstextdef"> </a>blocks of text</dt><dd><p>more than one sentence of text</p></dd><dt class="label"><a name="CAPTCHAdef" id="CAPTCHAdef"> </a>CAPTCHA</dt><dd><p>initialism for "Completely Automated Public Turing test to tell Computers and Humans Apart"</p><div class="note"><p class="prefix"><em>Note 1:
</em>CAPTCHA tests often involve asking the user to type in text that is displayed in an obscured image or audio file.</p><p class="prefix"><em>Note 2:
</em>A Turing test is any system of tests designed to differentiate a human from a computer. It is named after famed computer scientist Alan Turing. The term was coined by researchers at Carnegie Mellon University. <a href="#CAPTCHA">[CAPTCHA]</a>
</p></div></dd><dt class="label"><a name="captionsdef" id="captionsdef"> </a>captions</dt><dd><p>synchronized visual and/or <a title="definition: text alternative" href="#text-altdef" class="termref">text alternative</a> for both speech and non-speech audio information needed to understand the media content</p><div class="note"><p class="prefix"><em>Note 1:
</em>Captions are similar to dialogue-only subtitles except captions convey not only the content of spoken dialogue, but also equivalents for non-dialogue audio information needed to understand the program content, including sound effects, music, laughter, speaker identification and location.</p><p class="prefix"><em>Note 2:
</em>Closed Captions are equivalents that can be turned on and off with some players.</p><p class="prefix"><em>Note 3:
</em>Open Captions are any captions that cannot be turned off. For example, if the captions are visual equivalent <a title="definition: image of text" href="#images-of-textdef" class="termref">images of text</a> embedded in <a title="definition: video" href="#videodef" class="termref">video</a>.</p><p class="prefix"><em>Note 4:
</em>Captions should not obscure or obstruct relevant information in the video.</p><p class="prefix"><em>Note 5:
</em>In some countries, captions are called subtitles.</p><p class="prefix"><em>Note 6:
</em>
<a title="definition: audio description" href="#audiodescdef" class="termref">Audio descriptions</a> can be, but do not need to be, captioned since they are descriptions of information that is already presented visually.</p></div></dd><dt class="label"><a name="context-changedef" id="context-changedef"> </a>changes of context</dt><dd><p>major changes in the content of the <a title="definition: Web page" href="#webpagedef" class="termref">Web page</a> that, if made without user awareness, can disorient users who are not able to view the entire page simultaneously</p><p>Changes in context include changes of:</p><ol class="enumar"><li><p>
<a title="definition: user agent" href="#useragentdef" class="termref">user agent</a>;</p></li><li><p>
<a title="definition: viewport" href="#viewportdef" class="termref">viewport</a>;</p></li><li><p>focus;</p></li><li><p>
<a title="definition: content (Web content)" href="#contentdef" class="termref">content</a> that changes the meaning of the <a title="definition: Web page" href="#webpagedef" class="termref">Web page</a>.</p></li></ol><div class="note"><p class="prefix"><em>Note: </em>A change of content is not always a change of context. Changes in content, such as an expanding outline, dynamic menu, or a tab control do not necessarily change the context, unless they also change one of the above (e.g., focus).</p></div><div class="example"><p class="prefix"><em>Example: </em>Opening a new window, moving focus to a different component, going to a new page (including anything that would look to a user as if they had moved to a new page) or significantly re-arranging the content of a page are examples of changes of context.</p></div></dd><dt class="label"><a name="conformancedef" id="conformancedef"> </a>conformance</dt><dd><p>
satisfying all the requirements of a given standard, guideline or specification
</p></dd><dt class="label"><a name="conforming-alternate-versiondef" id="conforming-alternate-versiondef"> </a>conforming alternate version</dt><dd><p>version that</p><ol class="enumar"><li><p>conforms at the designated level, and</p></li><li><p>provides all of the same information and <a title="definition: functionality" href="#functiondef" class="termref">functionality</a> in the same <a title="definition: human language" href="#human-langdef" class="termref">human language</a>, and</p></li><li><p> is as up to date as the non-conforming content, and </p></li><li><p>for which at least one of the following is true:</p><ol class="enumla"><li><p>the conforming version can be reached from the non-conforming page via an <a title="definition: accessibility supported" href="#accessibility-supporteddef" class="termref">accessibility-supported</a>
<a title="definition: mechanism" href="#mechanismdef" class="termref">mechanism</a>, or</p></li><li><p>the non-conforming version can only be reached from the conforming version, or</p></li><li><p>the non-conforming version can only be reached from a conforming page that also provides a mechanism to reach the conforming version</p></li></ol></li></ol><div class="note"><p class="prefix"><em>Note 1:
</em>In this definition, "can only be reached" means that there is some mechanism, such as a conditional redirect, that prevents a user from "reaching" (loading) the non-conforming page unless the user had just come from the conforming version.</p><p class="prefix"><em>Note 2:
</em>The alternate version does not need to be matched page for page with the original (e.g., the conforming alternate version may consist of multiple pages).</p><p class="prefix"><em>Note 3:
</em>If multiple language versions are available, then conforming alternate versions are required for each language offered.</p><p class="prefix"><em>Note 4:
</em>Alternate versions may be provided to accommodate different technology environments or user groups. Each version should be as conformant as possible. One version would need to be fully conformant in order to meet <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/#cc1">conformance requirement 1</a>.</p><p class="prefix"><em>Note 5:
</em>The conforming alternative version does not need to reside within the scope of conformance, or even on the same Web site, as long as it is as freely available as the non-conforming version. </p><p class="prefix"><em>Note 6:
</em>Alternate versions should not be confused with <a title="definition: supplemental content" href="#suppcontentdef" class="termref">supplementary content</a>, which support the original page and enhance comprehension.</p><p class="prefix"><em>Note 7:
</em>Setting user preferences within the content to produce a conforming version is an acceptable mechanism for reaching another version as long as the method used to set the preferences is accessibility supported.</p></div><p class="circref">See <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-conforming-alt-versions-head">Understanding Conforming Alternate Versions</a>
</p></dd><dt class="label"><a name="contentdef" id="contentdef"> </a>content (Web content)</dt><dd><p>
information and sensory experience to be communicated to the user by means of a <a title="definition: user agent" href="#useragentdef" class="termref">user agent</a>, including
code or markup that defines the content's
<a title="definition: structure" href="#structuredef" class="termref">structure</a>, <a title="definition: presentation" href="#presentationdef" class="termref">presentation</a>, and interactions
</p></dd><dt class="label"><a name="context-sensitivehelpdef" id="context-sensitivehelpdef"> </a>context-sensitive help</dt><dd><p>help text that provides information related to the function currently being performed</p><div class="note"><p class="prefix"><em>Note: </em>Clear labels can act as context-sensitive help.</p></div></dd><dt class="label"><a name="contrast-ratiodef" id="contrast-ratiodef"> </a>contrast ratio</dt><dd><p>(L1 + 0.05) / (L2 + 0.05), where</p><ul><li><p>L1 is the
<a title="definition: relative luminance" href="#relativeluminancedef" class="termref">relative luminance</a> of the lighter of the colors, and</p></li><li><p>L2 is the
<a title="definition: relative luminance" href="#relativeluminancedef" class="termref">relative luminance</a> of the darker of the colors.</p></li></ul><div class="note"><p class="prefix"><em>Note 1:
</em>Contrast ratios can range from 1 to 21 (commonly written 1:1 to 21:1).</p><p class="prefix"><em>Note 2:
</em>Because authors do not have control over user settings as to how text is rendered (for example font smoothing or anti-aliasing), the contrast ratio for text can be evaluated with anti-aliasing turned off.</p><p class="prefix"><em>Note 3:
</em>For the purpose of Success Criteria 1.4.3 and 1.4.6, contrast is measured with respect to the specified background over which the text is rendered in normal usage. If no background color is specified, then white is assumed. </p><p class="prefix"><em>Note 4:
</em>Background color is the specified color of content over which the text is to be rendered in normal usage. It is a failure if no background color is specified when the text color is specified, because the user's default background color is unknown and cannot be evaluated for sufficient contrast. For the same reason, it is a failure if no text color is specified when a background color is specified. </p><p class="prefix"><em>Note 5:
</em>When there is a border around the letter, the border can add contrast and would be used in calculating the contrast between the letter and its background. A narrow border around the letter would be used as the letter. A wide border around the letter that fills in the inner details of the letters acts as a halo and would be considered background.</p><p class="prefix"><em>Note 6:
</em>WCAG conformance should be evaluated for color pairs specified in the content that an author would expect to appear adjacent in typical presentation. Authors need not consider unusual presentations, such as color changes made by the user agent, except where caused by authors' code.</p></div></dd><dt class="label"><a name="correct-reading-sequencedef" id="correct-reading-sequencedef"> </a>correct reading sequence</dt><dd><p>any sequence where words and paragraphs are presented in an order that does not change the meaning of the content </p></dd><dt class="label"><a name="emergencydef" id="emergencydef"> </a>emergency</dt><dd><p>a sudden, unexpected situation or occurrence that requires immediate action to preserve health, safety, or property </p></dd><dt class="label"><a name="essentialdef" id="essentialdef"> </a>essential</dt><dd><p>if removed, would fundamentally change the information or functionality of the content, <strong>and</strong> information and functionality cannot be achieved in another way that would conform </p></dd><dt class="label"><a name="extended-addef" id="extended-addef"> </a>extended audio description</dt><dd><p>audio description that is added to an audiovisual presentation by pausing the <a title="definition: video" href="#videodef" class="termref">video</a> so that there is time to add additional description</p><div class="note"><p class="prefix"><em>Note: </em>This technique is only used when the sense of the <a title="definition: video" href="#videodef" class="termref">video</a> would be lost without the additional <a title="definition: audio description" href="#audiodescdef" class="termref">audio description</a> and the pauses between dialogue/narration are too short.</p></div></dd><dt class="label"><a name="flash-def" id="flash-def"> </a>flash</dt><dd><p>a pair of opposing changes in <a title="definition: relative luminance" href="#relativeluminancedef" class="termref">relative luminance</a> that can cause seizures in some people if it is large enough and in the right frequency range</p><div class="note"><p class="prefix"><em>Note 1:
</em>See <a title="definition: general flash and red flash thresholds" href="#general-thresholddef" class="termref">general flash and red flash thresholds</a> for information about types of flash that are not allowed.</p><p class="prefix"><em>Note 2:
</em>See also <a title="definition: blinking" href="#blinksdef" class="termref">blinking</a>.</p></div></dd><dt class="label"><a name="functiondef" id="functiondef"> </a>functionality</dt><dd><p>
<a title="definition: process" href="#processdef" class="termref">processes</a> and outcomes achievable through user action</p></dd><dt class="label"><a name="general-thresholddef" id="general-thresholddef"> </a>general flash and red flash thresholds</dt><dd><p>a <a title="definition: flash" href="#flash-def" class="termref">flash</a> or rapidly changing image sequence is below the threshold (i.e., content <strong>passes</strong>) if any of the following are true:</p><ol class="enumar"><li><p>there are no more than three
<strong>general flashes</strong> and / or no more than three <strong>red flashes</strong>
within any one-second period; or</p></li><li><p>the combined area of flashes occurring concurrently
occupies no more than a total of .006 steradians within any 10 degree visual field on the screen (25% of any 10 degree visual field on the screen) at typical viewing distance
</p></li></ol><p> where:</p><ul><li><p>A <strong>general flash</strong> is defined as a pair of opposing changes in <a title="definition: relative luminance" href="#relativeluminancedef" class="termref">relative luminance</a> of 10% or more of the maximum relative luminance where the relative luminance of the darker image is below 0.80; and where "a pair of opposing changes" is an increase followed by a decrease, or a decrease followed by an increase, and</p></li><li><p>A <strong>red flash</strong> is defined as any pair of opposing transitions involving a saturated red.</p></li></ul><p>
<em>Exception:</em> Flashing that is a fine, balanced, pattern such as white noise or an alternating checkerboard pattern with "squares" smaller than 0.1 degree (of visual field at typical viewing distance) on a side does not violate the thresholds.</p><div class="note"><p class="prefix"><em>Note 1:
</em>For general software or Web content, using a 341 x 256 pixel rectangle anywhere on the displayed screen area when the content is viewed at 1024 x 768 pixels will provide a good estimate of a 10 degree visual field for standard screen sizes and viewing distances (e.g., 15-17 inch screen at 22-26 inches). (Higher resolutions displays showing the same rendering of the content yield smaller and safer images so it is lower resolutions that are used to define the thresholds.)</p><p class="prefix"><em>Note 2:
</em>A transition is the change in relative luminance (or relative luminance/color for red flashing) between adjacent peaks and valleys in a plot of relative luminance (or relative luminance/color for red flashing) measurement against time. A flash consists of two opposing transitions. </p><p class="prefix"><em>Note 3:
</em>The current working definition in the field for <strong>"pair of opposing transitions involving a saturated red"</strong> is where, for either or both states involved in each transition, R/(R+ G + B) >= 0.8, and the change in the value of (R-G-B)x320 is > 20 (negative values of (R-G-B)x320 are set to zero) for both transitions. R, G, B values range from 0-1 as specified in “relative luminance” definition. <a href="#HARDING-BINNIE">[HARDING-BINNIE]</a></p><p class="prefix"><em>Note 4:
</em>Tools are available that will carry out analysis from video screen capture. However, no tool is necessary to evaluate for this condition if flashing is less than or equal to 3 flashes in any one second. Content automatically passes (see #1 and #2 above).</p></div></dd><dt class="label"><a name="human-langdef" id="human-langdef"> </a>human language</dt><dd><p>
language that is spoken, written or signed (through visual or tactile means) to communicate with humans
</p><div class="note"><p class="prefix"><em>Note: </em>See also <a title="definition: sign language" href="#sign-languagedef" class="termref">sign language</a>.</p></div></dd><dt class="label"><a name="idiomsdef" id="idiomsdef"> </a>idiom</dt><dd><p>phrase whose meaning cannot be deduced from the meaning of the individual words and the specific words cannot be changed without losing the meaning</p><div class="note"><p class="prefix"><em>Note: </em>idioms cannot be translated directly, word for word, without losing their (cultural or language-dependent) meaning.
</p></div><div class="example"><p class="prefix"><em>Example 1:
</em>In English, "spilling the beans" means "revealing a secret." However, "knocking over the beans" or "spilling the vegetables" does not mean the same thing.</p><p class="prefix"><em>Example 2:
</em>In Japanese, the phrase "<span lang="jp" xml:lang="jp">さじを投げる</span>" literally translates into "he throws a spoon," but it means that there is nothing he can do and finally he gives up.
</p><p class="prefix"><em>Example 3:
</em>In Dutch, "<span lang="ne" xml:lang="ne">Hij ging met de kippen op stok</span>" literally translates into "He went to roost with the chickens," but it means that he went to bed early.</p></div></dd><dt class="label"><a name="images-of-textdef" id="images-of-textdef"> </a>image of text</dt><dd><p>text that has been rendered in a non-text form (e.g., an image) in order to achieve a particular visual effect </p><div class="note"><p class="prefix"><em>Note: </em>This does not include <a title="definition: text" href="#textdef" class="termref">text</a> that is part of a picture that contains significant other visual content.</p></div><div class="example"><p class="prefix"><em>Example: </em>A person's name on a nametag in a photograph.</p></div></dd><dt class="label"><a name="informativedef" id="informativedef"> </a>informative</dt><dd><p>for information purposes and not required for conformance</p><div class="note"><p class="prefix"><em>Note: </em>Content required for <a title="definition: conformance" href="#conformancedef" class="termref">conformance</a> is referred to as "<a title="definition: normative" href="#normativedef" class="termref">normative</a>."</p></div></dd><dt class="label"><a name="input-errordef" id="input-errordef"> </a>input error</dt><dd><p>information provided by the user that is not accepted</p><div class="note"><p class="prefix"><em>Note: </em> This includes:</p><ol class="enumar"><li><p>Information that is required by the <a title="definition: Web page" href="#webpagedef" class="termref">Web page</a> but omitted by the user</p></li><li><p>Information that is provided by the user but that falls outside the required data format or values</p></li></ol></div></dd><dt class="label"><a name="jargondef" id="jargondef"> </a>jargon</dt><dd><p>words used in a particular way by people in a particular field</p><div class="example"><p class="prefix"><em>Example: </em>The word StickyKeys is jargon from the field of assistive technology/accessibility.</p></div></dd><dt class="label"><a name="keybrd-interfacedef" id="keybrd-interfacedef"> </a>keyboard interface</dt><dd><p>interface used by software to obtain keystroke input</p><div class="note"><p class="prefix"><em>Note 1:
</em>A keyboard interface allows users to provide keystroke input to programs even if the native technology does not contain a keyboard.</p><div class="example"><p class="prefix"><em>Example: </em>A touchscreen PDA has a keyboard interface built into its operating system as well as a connector for external keyboards. Applications on the PDA can use the interface to obtain keyboard input either from an external keyboard or from other applications that provide simulated keyboard output, such as handwriting interpreters or speech-to-text applications with "keyboard emulation" functionality.</p></div><p class="prefix"><em>Note 2:
</em>Operation of the application (or parts of the application) through a keyboard-operated mouse emulator, such as MouseKeys, does not qualify as operation through a keyboard interface because operation of the program is through its pointing device interface, not through its keyboard interface.</p></div></dd><dt class="label"><a name="labeldef" id="labeldef"> </a>label</dt><dd><p>
<a title="definition: text" href="#textdef" class="termref">text</a>
or other component with a <a title="definition: text alternative" href="#text-altdef" class="termref">text alternative</a>
that is presented to a user to identify a component within Web <a title="definition: content (Web content)" href="#contentdef" class="termref">content</a>
</p><div class="note"><p class="prefix"><em>Note 1:
</em>
A label is presented to all users whereas the <a title="definition: name" href="#namedef" class="termref">name</a> may be hidden and only exposed by assistive technology. In many (but not all) cases the name and the label are the same.
</p><p class="prefix"><em>Note 2:
</em>The term label is not limited to the label element in HTML.
</p></div></dd><dt class="label"><a name="larger-scaledef" id="larger-scaledef"> </a>large scale (text)</dt><dd><p>with at least 18 point or 14 point bold or font size that would yield equivalent size for Chinese, Japanese and Korean (CJK) fonts
</p><div class="note"><p class="prefix"><em>Note 1:
</em>Fonts with extraordinarily thin strokes or unusual features and characteristics that reduce the familiarity of their letter forms are harder to read, especially at lower contrast levels.</p><p class="prefix"><em>Note 2:
</em>Font size is the size when the content is delivered. It does not include resizing that may be done by a user.</p><p class="prefix"><em>Note 3:
</em>The actual size of the character that a user sees is dependent both on the author-defined size and the user's display or user-agent settings. For many mainstream body text fonts, 14 and 18 point is roughly equivalent to 1.2 and 1.5 em or to 120% or 150% of the default size for body text (assuming that the body font is 100%), but authors would need to check this for the particular fonts in use. When fonts are defined in relative units, the actual point size is calculated by the user agent for display. The point size should be obtained from the user agent, or calculated based on font metrics as the user agent does, when evaluating this success criterion. Users who have low vision would be responsible for choosing appropriate settings.
</p><p class="prefix"><em>Note 4:
</em>When using text without specifying the font size, the smallest font size used on major browsers for unspecified text would be a reasonable size to assume for the font. If a level 1 heading is rendered in 14pt bold or higher on major browsers, then it would be reasonable to assume it is large text. Relative scaling can be calculated from the default sizes in a similar fashion. </p><p class="prefix"><em>Note 5:
</em>The 18 and 14 point sizes for roman texts are taken from the minimum size for large print (14pt) and the larger standard font size (18pt). For other fonts such as CJK languages, the "equivalent" sizes would be the minimum large print size used for those languages and the next larger standard large print size.</p></div></dd><dt class="label"><a name="legalcommitmentsdef" id="legalcommitmentsdef"> </a>legal commitments</dt><dd><p>transactions where the person incurs a legally binding obligation or benefit</p><div class="example"><p class="prefix"><em>Example: </em>A marriage license, a stock trade (financial and legal), a will, a loan, adoption, signing up for the army, a contract of any type, etc.</p></div></dd><dt class="label"><a name="linkpurposedef" id="linkpurposedef"> </a>link purpose</dt><dd><p>nature of the result obtained by activating a hyperlink</p></dd><dt class="label"><a name="livedef" id="livedef"> </a>live</dt><dd><p>information captured from a real-world event and transmitted to the receiver with no more than a broadcast delay</p><div class="note"><p class="prefix"><em>Note 1:
</em>A broadcast delay is a short (usually automated) delay, for example used in order to give the broadcaster time to queue or censor the audio (or video) feed, but not sufficient to allow significant editing.</p><p class="prefix"><em>Note 2:
</em>If information is completely computer generated, it is not live.</p></div></dd><dt class="label"><a name="lowseceddef" id="lowseceddef"> </a>lower secondary education level</dt><dd><p>the two or three year period of education that begins after completion of six years of school and ends nine years after the beginning of <a title="definition: primary education level" href="#primseceddef" class="termref">primary education</a>
</p><div class="note"><p class="prefix"><em>Note: </em>This definition is based on the International Standard Classification of Education <a href="#UNESCO">[UNESCO]</a>.</p></div></dd><dt class="label"><a name="mechanismdef" id="mechanismdef"> </a>mechanism</dt><dd><p>
<a title="definition: process" href="#processdef" class="termref">process</a> or technique for achieving a result</p><div class="note"><p class="prefix"><em>Note 1:
</em>The mechanism may be explicitly provided in the content, or may be <a title="definition: relied upon (technologies that are)" href="#reliedupondef" class="termref">relied upon</a> to be provided by either the platform or by <a title="definition: user agent" href="#useragentdef" class="termref">user agents</a>, including <a title="definition: assistive technology (as used in this document)" href="#atdef" class="termref">assistive technologies</a>.</p><p class="prefix"><em>Note 2:
</em>The mechanism needs to meet all success criteria for the conformance level claimed.
</p></div></dd><dt class="label"><a name="multimedia-alt-textdef" id="multimedia-alt-textdef"> </a>media alternative for text</dt><dd><p>media that presents no more information than is already presented in text (directly or via text alternatives)
</p><div class="note"><p class="prefix"><em>Note: </em>A media alternative for text is provided for those who benefit from alternate representations of text. Media alternatives for text may be audio-only, video-only (including sign-language video), or audio-video.</p></div></dd><dt class="label"><a name="namedef" id="namedef"> </a>name</dt><dd><p>text by which software can identify a component within Web content to the user</p><div class="note"><p class="prefix"><em>Note 1:
</em>The name may be hidden and only exposed by assistive technology, whereas a <a title="definition: label" href="#labeldef" class="termref">label</a> is presented to all users.
In many (but not all) cases, the label and the name are the same.
</p><p class="prefix"><em>Note 2:
</em>This is unrelated to the name attribute in HTML.</p></div></dd><dt class="label"><a name="nav-seqdef" id="nav-seqdef"> </a>navigated sequentially</dt><dd><p>navigated in the order defined for advancing focus (from one element to the next) using a <a title="definition: keyboard interface" href="#keybrd-interfacedef" class="termref">keyboard interface</a>
</p></dd><dt class="label"><a name="non-text-contentdef" id="non-text-contentdef"> </a>non-text content</dt><dd><p>any content that is not a sequence of characters that can be <a title="definition: programmatically determined (programmatically determinable)" href="#programmaticallydetermineddef" class="termref">programmatically determined</a> or where the sequence is not expressing something in <a title="definition: human language" href="#human-langdef" class="termref">human language</a>
</p><div class="note"><p class="prefix"><em>Note: </em>This includes <a title="definition: ASCII art" href="#asciiartdef" class="termref">ASCII Art</a> (which is a pattern of characters), emoticons,
leetspeak (which uses character substitution), and images representing text</p></div></dd><dt class="label"><a name="normativedef" id="normativedef"> </a>normative</dt><dd><p>required for conformance</p><div class="note"><p class="prefix"><em>Note 1:
</em>One may conform in a variety of well-defined ways to this document.</p><p class="prefix"><em>Note 2:
</em>Content identified as "<a title="definition: informative" href="#informativedef" class="termref">informative</a>" or "non-normative" is never required for conformance.</p></div></dd><dt class="label"><a name="fullscreenwindowdef" id="fullscreenwindowdef"> </a>on a full-screen window</dt><dd><p>on the most common sized desktop/laptop display with the viewport maximized</p><div class="note"><p class="prefix"><em>Note: </em>Since people generally keep their computers for several years, it is best not to rely on the latest desktop/laptop display resolutions but to consider the common desktop/laptop display resolutions over the course of several years when making this evaluation.
</p></div></dd><dt class="label"><a name="pauseddef" id="pauseddef"> </a>paused</dt><dd><p>stopped by user request and not resumed until requested by user</p></dd><dt class="label"><a name="prerecordeddef" id="prerecordeddef"> </a>prerecorded</dt><dd><p>information that is not <a title="definition: live" href="#livedef" class="termref">live</a></p></dd><dt class="label"><a name="presentationdef" id="presentationdef"> </a>presentation</dt><dd><p>
rendering of the <a title="definition: content (Web content)" href="#contentdef" class="termref">content</a> in a form to be perceived by users
</p></dd><dt class="label"><a name="primseceddef" id="primseceddef"> </a>primary education level</dt><dd><p>six year time period that begins between the ages of five and seven, possibly without any previous education</p><div class="note"><p class="prefix"><em>Note: </em>This definition is based on the International Standard Classification of Education <a href="#UNESCO">[UNESCO]</a>.</p></div></dd><dt class="label"><a name="processdef" id="processdef"> </a>process</dt><dd><p>series of user actions where each action is required in order to complete an activity</p><div class="example"><p class="prefix"><em>Example 1:
</em>Successful use of a series of Web pages on a shopping site requires users to view alternative products, prices and offers, select products, submit an order, provide shipping information and provide payment information.</p><p class="prefix"><em>Example 2:
</em>An account registration page requires successful completion of a Turing test before the registration form can be accessed.</p></div></dd><dt class="label"><a name="programmaticallydetermineddef" id="programmaticallydetermineddef"> </a>programmatically determined (programmatically determinable)</dt><dd><p>determined by software from author-supplied data provided in a
way that different
<a title="definition: user agent" href="#useragentdef" class="termref">user agents</a>, including <a title="definition: assistive technology (as used in this document)" href="#atdef" class="termref">assistive technologies</a>, can extract and present this information to users in different modalities
</p><div class="example"><p class="prefix"><em>Example 1:
</em>Determined in a markup language from elements and attributes that are accessed directly by commonly available assistive technology.</p><p class="prefix"><em>Example 2:
</em>Determined from technology-specific data structures in a non-markup language and exposed to assistive technology via an accessibility <acronym title="Application Programming Interface">API</acronym> that is supported by commonly available assistive technology. </p></div></dd><dt class="label"><a name="pdlinkcontextdef" id="pdlinkcontextdef"> </a>programmatically determined link context</dt><dd><p>additional information that can be <a title="definition: programmatically determined (programmatically determinable)" href="#programmaticallydetermineddef" class="termref">programmatically determined</a> from <a title="definition: relationships" href="#relationshipsdef" class="termref">relationships</a> with a link, combined with the link text, and presented to users in different modalities
</p><div class="example"><p class="prefix"><em>Example: </em>In HTML, information that is programmatically determinable from a link in English includes text that is in the same paragraph, list, or table cell as the link or in a table header cell that is associated with the table cell that contains the link.
</p></div><div class="note"><p class="prefix"><em>Note: </em>Since screen readers interpret punctuation, they can also provide the context from the current sentence, when the focus is on a link in that sentence.
</p></div></dd><dt class="label"><a name="programmaticallysetdef" id="programmaticallysetdef"> </a>programmatically set</dt><dd><p>set by software using methods that are supported by user agents, including assistive technologies
</p></dd><dt class="label"><a name="puredecdef" id="puredecdef"> </a>pure decoration</dt><dd><p>serving only an aesthetic purpose, providing no information, and having no functionality</p><div class="note"><p class="prefix"><em>Note: </em>Text is only purely decorative if the words can be rearranged or substituted without changing their purpose.</p></div><div class="example"><p class="prefix"><em>Example: </em>The cover page of a dictionary has random words in very light text in the background.</p></div></dd><dt class="label"><a name="real-time-eventsdef" id="real-time-eventsdef"> </a>real-time event</dt><dd><p>event that a) occurs at the same time as the viewing and b) is not completely generated by the content</p><div class="example"><p class="prefix"><em>Example 1:
</em>A Webcast of a live performance (occurs at the same time as the viewing and is not prerecorded).</p><p class="prefix"><em>Example 2:
</em>An on-line auction with people bidding (occurs at the same time as the viewing).
</p><p class="prefix"><em>Example 3:
</em>Live humans interacting in a virtual world using avatars (is not completely generated by the content and occurs at the same time as the viewing).
</p></div></dd><dt class="label"><a name="relationshipsdef" id="relationshipsdef"> </a>relationships</dt><dd><p>
meaningful associations between distinct pieces of content
</p></dd><dt class="label"><a name="relativeluminancedef" id="relativeluminancedef"> </a>relative luminance</dt><dd><p>the relative brightness of any point in a colorspace, normalized to 0 for darkest black and 1 for lightest white</p><div class="note"><p class="prefix"><em>Note 1:
</em>For the sRGB colorspace, the relative luminance of a color is defined as L = 0.2126 * <strong>R</strong> + 0.7152 * <strong>G</strong> + 0.0722 * <strong>B</strong> where <strong>R</strong>, <strong>G</strong> and <strong>B</strong> are defined as:</p><ul><li><p>if R<sub>sRGB</sub> <= 0.03928 then <strong>R</strong> = R<sub>sRGB</sub>/12.92 else <strong>R</strong> = ((R<sub>sRGB</sub>+0.055)/1.055) ^ 2.4</p></li><li><p>if G<sub>sRGB</sub> <= 0.03928 then <strong>G</strong> = G<sub>sRGB</sub>/12.92 else <strong>G</strong> = ((G<sub>sRGB</sub>+0.055)/1.055) ^ 2.4</p></li><li><p>if B<sub>sRGB</sub> <= 0.03928 then <strong>B</strong> = B<sub>sRGB</sub>/12.92 else <strong>B</strong> = ((B<sub>sRGB</sub>+0.055)/1.055) ^ 2.4</p></li></ul><div class="note"><p class="prefix">and R<sub>sRGB</sub>, G<sub>sRGB</sub>, and B<sub>sRGB</sub> are defined as:</p></div><ul><li><p>R<sub>sRGB</sub> = R<sub>8bit</sub>/255</p></li><li><p>G<sub>sRGB</sub> = G<sub>8bit</sub>/255</p></li><li><p>B<sub>sRGB</sub> = B<sub>8bit</sub>/255</p></li></ul><div class="note"><p class="prefix">The "^" character is the exponentiation operator. (Formula taken from <a href="#sRGB">[sRGB]</a> and <a href="#IEC-4WD">[IEC-4WD]</a>).</p></div><p class="prefix"><em>Note 2:
</em>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 <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html">Understanding Success Criterion 1.4.3</a>.</p><p class="prefix"><em>Note 3:
</em>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). </p><p class="prefix"><em>Note 4:
</em>Tools are available that automatically do the calculations when testing contrast and flash.</p><p class="prefix"><em>Note 5:
</em>
A <a href="relative-luminance.xml">MathML version of the relative luminance definition</a> is available.
</p></div></dd><dt class="label"><a name="reliedupondef" id="reliedupondef"> </a>relied upon (technologies that are)</dt><dd><p>the content would not <a title="definition: conformance" href="#conformancedef" class="termref">conform</a> if that <a title="definition: technology (Web content)" href="#technologydef" class="termref">technology</a> is turned off or is not supported</p></dd><dt class="label"><a name="roledef" id="roledef"> </a>role</dt><dd><p>text or number by which software can identify the function of a component within Web content</p><div class="example"><p class="prefix"><em>Example: </em>A number that indicates whether an image functions as a hyperlink, command button, or check box.</p></div></dd><dt class="label"><a name="samefunctionalitydef" id="samefunctionalitydef"> </a>same functionality </dt><dd><p>
same result when used
</p><div class="example"><p class="prefix"><em>Example: </em>A submit "search" button on one Web page and a "find" button on another Web page may both have a field to enter a term and list topics in the Web site related to the term submitted. In this case, they would have the same functionality but would not be labeled consistently.</p></div></dd><dt class="label"><a name="samerelorderdef" id="samerelorderdef"> </a>same relative order</dt><dd><p>same position relative to other items</p><div class="note"><p class="prefix"><em>Note: </em>Items are considered to be in the same relative order even if other items are inserted or removed from the original order. For example, expanding navigation menus may insert an additional level of detail or a secondary navigation section may be inserted into the reading order.</p></div></dd><dt class="label"><a name="satisfiesdef" id="satisfiesdef"> </a>satisfies a success criterion</dt><dd><p>the success criterion does not evaluate to 'false' when applied to the page</p></dd><dt class="label"><a name="sectiondef" id="sectiondef"> </a>section</dt><dd><p>A self-contained portion of written content that deals with one or more related topics or thoughts</p><div class="note"><p class="prefix"><em>Note: </em>A section may consist of one or more paragraphs and include graphics, tables, lists and sub-sections.</p></div></dd><dt class="label"><a name="set-of-web-pagesdef" id="set-of-web-pagesdef"> </a>set of Web pages</dt><dd><p>collection of <a title="definition: Web page" href="#webpagedef" class="termref">Web pages</a> that share a common purpose and that are created by the same
author, group or organization
</p><div class="note"><p class="prefix"><em>Note: </em>Different language versions would be considered different sets of Web pages. </p></div></dd><dt class="label"><a name="sign-languagedef" id="sign-languagedef"> </a>sign language</dt><dd><p>a language using combinations of movements of the hands and arms, facial expressions, or
body positions to convey meaning
</p></dd><dt class="label"><a name="sign-languageinterpdef" id="sign-languageinterpdef"> </a>sign language interpretation</dt><dd><p>translation of one language, generally a spoken language, into a <a title="definition: sign language" href="#sign-languagedef" class="termref">sign language</a>
</p><div class="note"><p class="prefix"><em>Note: </em>
True sign languages are independent languages that are unrelated to the spoken language(s) of the same country or region.
</p></div></dd><dt class="label"><a name="sensoryexpdef" id="sensoryexpdef"> </a>specific sensory experience</dt><dd><p>a sensory experience that is not purely decorative and does not primarily convey important information or perform a function</p><div class="example"><p class="prefix"><em>Example: </em>
Examples include a performance of a flute solo, works of visual art etc.
</p></div></dd><dt class="label"><a name="structuredef" id="structuredef"> </a>structure</dt><dd><ol class="enumar"><li><p>The way the parts of a <a title="definition: Web page" href="#webpagedef" class="termref">Web page</a>
are organized in relation to each other; and
</p></li><li><p>The way a collection of <a title="definition: Web page" href="#webpagedef" class="termref">Web pages</a> is organized</p></li></ol></dd><dt class="label"><a name="suppcontentdef" id="suppcontentdef"> </a>supplemental content</dt><dd><p>additional <a title="definition: content (Web content)" href="#contentdef" class="termref">content</a> that illustrates or clarifies the primary content
</p><div class="example"><p class="prefix"><em>Example 1:
</em>
An audio version of a <a title="definition: Web page" href="#webpagedef" class="termref">Web page</a>.
</p><p class="prefix"><em>Example 2:
</em>
An illustration of a complex <a title="definition: process" href="#processdef" class="termref">process</a>.
</p><p class="prefix"><em>Example 3:
</em>
A paragraph summarizing the major outcomes and recommendations made in a research study.
</p></div></dd><dt class="label"><a name="synchronizedmediadef" id="synchronizedmediadef"> </a>synchronized media</dt><dd><p><a title="definition: audio" href="#audiodef" class="termref">audio</a> or <a title="definition: video" href="#videodef" class="termref">video</a> synchronized with another
format for presenting information and/or with time-based interactive components, unless the media is a <a title="definition: media alternative for text" href="#multimedia-alt-textdef" class="termref">media alternative for text</a> that is clearly labeled as such
</p></dd><dt class="label"><a name="technologydef" id="technologydef"> </a>technology (Web content)</dt><dd><p>
<a title="definition: mechanism" href="#mechanismdef" class="termref">mechanism</a> for encoding instructions to be rendered, played or executed by <a title="definition: user agent" href="#useragentdef" class="termref">user agents</a>
</p><div class="note"><p class="prefix"><em>Note 1:
</em>As used in these guidelines "Web Technology" and the word "technology" (when used alone) both refer to Web Content Technologies.</p><p class="prefix"><em>Note 2:
</em>Web content technologies may include markup languages, data formats, or programming languages that authors may use alone or in combination to create end-user experiences that range from static Web pages to synchronized media presentations to dynamic Web applications.
</p></div><div class="example"><p class="prefix"><em>Example: </em>Some common examples of Web content technologies include <acronym title="Hypertext Markup Language">HTML</acronym>, <acronym title="Cascading Style Sheets">CSS</acronym>, <acronym title="Scalable Vector Graphics">SVG</acronym>, <acronym title="Portable Network Graphics">PNG</acronym>, <acronym title="Portable Document Format">PDF</acronym>, Flash, and JavaScript.
</p></div></dd><dt class="label"><a name="textdef" id="textdef"> </a>text</dt><dd><p>sequence of characters that can be <a title="definition: programmatically determined (programmatically determinable)" href="#programmaticallydetermineddef" class="termref">programmatically determined</a>, where the sequence is expressing something in <a title="definition: human language" href="#human-langdef" class="termref">human language</a>
</p></dd><dt class="label"><a name="text-altdef" id="text-altdef"> </a>text alternative</dt><dd><p><a title="definition: text" href="#textdef" class="termref">Text</a> that is programmatically associated with <a title="definition: non-text content" href="#non-text-contentdef" class="termref">non-text content</a> or referred to from text that is programmatically associated with non-text content. Programmatically associated text is text whose location can be programmatically determined from the non-text content.</p><div class="example"><p class="prefix"><em>Example: </em>An image of a chart is described in text in the paragraph after the chart. The short text alternative for the chart indicates that a description follows.
</p></div><div class="note"><p class="prefix"><em>Note: </em>Refer to <a href="http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-text-alternatives-head">Understanding Text Alternatives</a> for more information.</p></div></dd><dt class="label"><a name="unusual-restricteddef" id="unusual-restricteddef"> </a>used in an unusual or restricted way</dt><dd><p>words used in such a way that requires users to know exactly which definition to apply in order to understand the content correctly</p><div class="example"><p class="prefix"><em>Example: </em>The term "gig" means something different if it occurs in a discussion of music concerts than it does in article about computer hard drive space, but the appropriate definition can be determined from context. By contrast, the word "text" is used in a very specific way in WCAG 2.0, so a definition is supplied in the glossary.</p></div></dd><dt class="label"><a name="useragentdef" id="useragentdef"> </a>user agent</dt><dd><p>any software that retrieves and presents Web content for users</p><div class="example"><p class="prefix"><em>Example: </em>Web browsers, media players, plug-ins, and other programs — including <a title="definition: assistive technology (as used in this document)" href="#atdef" class="termref">assistive technologies</a> — that help in retrieving, rendering, and interacting with Web content.
</p></div></dd><dt class="label"><a name="user-controllabledef" id="user-controllabledef"> </a>user-controllable</dt><dd><p>data that is intended to be accessed by users</p><div class="note"><p class="prefix"><em>Note: </em>This does not refer to such things as Internet logs and search engine monitoring data.</p></div><div class="example"><p class="prefix"><em>Example: </em> Name and address fields for a user's account.</p></div></dd><dt class="label"><a name="user-interface-componentdef" id="user-interface-componentdef"> </a>user interface component</dt><dd><p>a part of the content that is perceived by users as a single control for a distinct function</p><div class="note"><p class="prefix"><em>Note 1:
</em>Multiple user interface components may be implemented as a single programmatic element. Components here is not tied to programming techniques, but rather to what the user perceives as separate controls. </p><p class="prefix"><em>Note 2:
</em>User interface components include form elements and links as well as components generated by scripts.</p></div><div class="example"><p class="prefix"><em>Example: </em>An applet has a "control" that can be used to move through content by line or page or random access. Since each of these would need to have a name and be settable independently, they would each be a "user interface component." </p></div></dd><dt class="label"><a name="videodef" id="videodef"> </a>video</dt><dd><p>the technology of moving or sequenced pictures or images</p><div class="note"><p class="prefix"><em>Note: </em>Video can be made up of animated or photographic images, or both.</p></div></dd><dt class="label"><a name="video-onlydef" id="video-onlydef"> </a>video-only</dt><dd><p>a time-based presentation that contains only <a title="definition: video" href="#videodef" class="termref">video</a> (no <a title="definition: video" href="#videodef" class="termref">audio</a> and no interaction)</p></dd><dt class="label"><a name="viewportdef" id="viewportdef"> </a>viewport</dt><dd><p>
object in which the user agent presents content
</p><div class="note"><p class="prefix"><em>Note 1:
</em>The <a title="definition: user agent" href="#useragentdef" class="termref">user agent</a>
presents content through one or more viewports. Viewports include windows, frames, loudspeakers, and virtual magnifying glasses. A viewport may contain another viewport (e.g., nested frames). Interface components created by the user agent such as prompts, menus, and alerts are not viewports. </p><p class="prefix"><em>Note 2:
</em>This definition is based on <a href="http://www.w3.org/TR/WAI-USERAGENT/glossary.html">User Agent Accessibility Guidelines 1.0 Glossary</a>.</p></div></dd><dt class="label"><a name="visually-customizeddef" id="visually-customizeddef"> </a>visually customized</dt><dd><p>the font, size, color, and background can be set </p></dd><dt class="label"><a name="webpagedef" id="webpagedef"> </a>Web page</dt><dd><p>
a non-embedded resource
obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a <a title="definition: user agent" href="#useragentdef" class="termref">user agent</a>
</p><div class="note"><p class="prefix"><em>Note 1:
</em>Although any "other resources" would be rendered together with the primary resource, they would not necessarily be rendered simultaneously with each other.</p><p class="prefix"><em>Note 2:
</em>For the purposes of conformance with these guidelines, a resource must be "non-embedded" within the scope of conformance to be considered a Web page.</p></div><div class="example"><p class="prefix"><em>Example 1:
</em>A Web resource including all embedded images and media.</p><p class="prefix"><em>Example 2:
</em>A Web mail program built using Asynchronous JavaScript and XML (AJAX). The program lives entirely at http://example.com/mail, but includes an inbox, a contacts area and a calendar. Links or buttons are provided that cause the inbox, contacts, or calendar to display, but do not change the URI of the page as a whole.</p><p class="prefix"><em>Example 3:
</em>A customizable portal site, where users can choose content to display from a set of different content modules.</p><p class="prefix"><em>Example 4:
</em>When you enter "http://shopping.example.com/" in your browser, you enter a movie-like interactive shopping environment where you visually move around in a store dragging products off of the shelves around you and into a visual shopping cart in front of you. Clicking on a product causes it to be demonstrated with a specification sheet floating alongside. This might be a single-page Web site or just one page within a Web site.</p></div></dd></dl></div><div class="div1">
<h2><a name="acknowledgments" id="acknowledgments"> </a>Appendix B: Acknowledgments</h2><p>This section is <a title="definition: informative" href="#informativedef" class="termref">informative</a>. </p><p>This publication has been funded in part with Federal funds from the U.S. Department of Education, National Institute on Disability and Rehabilitation Research (NIDRR) under contract number ED05CO0039. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.</p><p>Additional information about participation in the Web Content Accessibility Guidelines Working Group (WCAG WG) can be found on the <a href="http://www.w3.org/WAI/GL/">Working Group home page</a>.
</p><div class="div2"> <h3><a name="d0e3472" id="d0e3472"> </a>Participants active in the WCAG WG at the time of publication</h3><ul><li><p>Bruce Bailey (U.S. Access Board) </p></li><li><p>Frederick Boland (NIST)</p></li><li><p>Ben Caldwell (Trace R&D Center, University of Wisconsin)</p></li><li><p>Sofia Celic (W3C Invited Expert)</p></li><li><p>Michael Cooper (W3C)</p></li><li><p>Roberto Ellero (International Webmasters Association / HTML Writers
Guild)</p></li><li><p>Bengt Farre (Rigab)</p></li><li><p>Loretta Guarino Reid (Google)</p></li><li><p>Katie Haritos-Shea</p></li><li><p>Andrew Kirkpatrick (Adobe)</p></li><li><p>Drew LaHart (IBM) </p></li><li><p>Alex Li (SAP AG)</p></li><li><p>David MacDonald (E-Ramp Inc.)</p></li><li><p>Roberto Scano (International Webmasters Association / HTML Writers
Guild)</p></li><li><p>Cynthia Shelly (Microsoft)</p></li><li><p>Andi Snow-Weaver (IBM)</p></li><li><p>Christophe Strobbe (DocArch, K.U.Leuven)</p></li><li><p>Gregg Vanderheiden (Trace R&D Center, University of Wisconsin)</p></li></ul></div><div class="div2"> <h3><a name="d0e3530" id="d0e3530"> </a>Other previously active WCAG WG participants and other contributors to WCAG 2.0</h3><p>Shadi Abou-Zahra, Jim Allan, Jenae Andershonis, Avi Arditti, Aries Arditi, Mike Barta, Sandy Bartell, Kynn Bartlett, Marco Bertoni, Harvey Bingham, Chris Blouch, Paul Bohman, Patrice Bourlon, Judy Brewer, Andy Brown, Dick Brown, Doyle Burnett, Raven Calais, Tomas Caspers, Roberto Castaldo, Sambhavi Chandrashekar, Mike Cherim, Jonathan Chetwynd, Wendy Chisholm, Alan Chuter, David M Clark, Joe Clark, James Coltham, James Craig, Tom Croucher, Nir Dagan, Daniel Dardailler, Geoff Deering, Pete DeVasto, Don Evans, Neal Ewers, Steve Faulkner, Lainey Feingold, Alan J. Flavell, Nikolaos Floratos, Kentarou Fukuda, Miguel Garcia, P.J. Gardner, Greg Gay, Becky Gibson, Al Gilman, Kerstin Goldsmith, Michael Grade, Jon Gunderson, Emmanuelle Gutiérrez y Restrepo, Brian Hardy, Eric Hansen, Sean Hayes, Shawn Henry, Hans Hillen, Donovan Hipke, Bjoern Hoehrmann, Chris Hofstader, Yvette Hoitink, Carlos Iglesias, Ian Jacobs, Phill Jenkins, Jyotsna Kaki, Leonard R. Kasday, Kazuhito Kidachi, Ken Kipness, Marja-Riitta Koivunen, Preety Kumar, Gez Lemon, Chuck Letourneau, Scott Luebking, Tim Lacy, Jim Ley, William Loughborough, Greg Lowney, Luca Mascaro, Liam McGee, Jens Meiert, Niqui Merret, Alessandro Miele, Mathew J Mirabella, Charles McCathieNevile , Matt May, Marti McCuller, Sorcha Moore, Charles F. Munat, Robert Neff, Bruno von Niman, Tim Noonan, Sebastiano Nutarelli, Graham Oliver, Sean B. Palmer, Sailesh Panchang, Nigel Peck, Anne Pemberton, David Poehlman, Adam Victor Reed, Chris Ridpath, Lee Roberts, Gregory J. Rosmaita, Matthew Ross, Sharron Rush, Gian Sampson-Wild, Joel Sanda, Gordon Schantz, Lisa Seeman, John Slatin, Becky Smith, Jared Smith, Neil Soiffer, Jeanne Spellman, Mike Squillace, Michael Stenitzer, Jim Thatcher, Terry Thompson, Justin Thorp, Makoto Ueki, Eric Velleman, Dena Wainwright, Paul Walsch, Takayuki Watanabe, Jason White.</p></div></div><div class="div1">
<h2><a name="references" id="references"> </a>Appendix C: References</h2><p>This section is <a title="definition: informative" href="#informativedef" class="termref">informative</a>. </p><dl><dt class="label"><a name="CAPTCHA" id="CAPTCHA"/>CAPTCHA</dt><dd>The CAPTCHA Project, Carnegie Mellon University. The project is online at <a href="http://www.captcha.net">http://www.captcha.net</a>.</dd><dt class="label"><a name="HARDING-BINNIE" id="HARDING-BINNIE"/>HARDING-BINNIE</dt><dd>Harding G. F. A. and Binnie, C.D., Independent Analysis of the ITC Photosensitive Epilepsy Calibration Test Tape. 2002.</dd><dt class="label"><a name="IEC-4WD" id="IEC-4WD"/>IEC-4WD</dt><dd>IEC/4WD 61966-2-1: Colour Measurement and Management in Multimedia Systems and Equipment - Part 2.1: Default Colour Space - sRGB. May 5, 1998.</dd><dt class="label"><a name="sRGB" id="sRGB"/>sRGB</dt><dd>"A Standard Default Color Space for the Internet - sRGB," M. Stokes, M. Anderson, S. Chandrasekar, R. Motta, eds., Version 1.10, November 5, 1996. A copy of this paper is available at <a href="http://www.w3.org/Graphics/Color/sRGB.html">http://www.w3.org/Graphics/Color/sRGB.html</a>.</dd><dt class="label"><a name="UNESCO" id="UNESCO"/>UNESCO</dt><dd>International Standard Classification of Education, 1997. A copy of the standard is available at <a href="http://www.unesco.org/education/information/nfsunesco/doc/isced_1997.htm">http://www.unesco.org/education/information/nfsunesco/doc/isced_1997.htm</a>.</dd><dt class="label"><a name="WCAG10" id="WCAG10"/>WCAG10</dt><dd>Web Content Accessibility Guidelines 1.0, G. Vanderheiden, W. Chisholm, I. Jacobs, Editors, W3C Recommendation, 5 May 1999, http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/. The latest version of WCAG 1.0 is available at <a href="http://www.w3.org/TR/WAI-WEBCONTENT/">http://www.w3.org/TR/WAI-WEBCONTENT/</a>.</dd></dl></div></div></body></html>