accessibility
52.8 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
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<!-- Generated from data/head.php, ../../smarty/{head.tpl} -->
<head>
<title>Accessibility (All) - W3C</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="Help" href="/Help/" />
<link rel="stylesheet" href="/2008/site/css/minimum" type="text/css" media="handheld, all" />
<style type="text/css" media="print, screen and (min-width: 481px)">
/*<![CDATA[*/
@import url("/2008/site/css/advanced");
/*]]>*/
</style>
<link href="/2008/site/css/minimum" rel="stylesheet" type="text/css" media="handheld, only screen and (max-device-width: 480px)" />
<meta name="viewport" content="width=device-width" />
<link rel="stylesheet" href="/2008/site/css/print" type="text/css" media="print" />
<link rel="shortcut icon" href="/2008/site/images/favicon.ico" type="image/x-icon" />
</head>
<body id="www-w3-org" class="w3c_public">
<div id="w3c_container">
<!-- Generated from data/mast.php, ../../smarty/{mast.tpl} -->
<div id="w3c_mast"><!-- #w3c_mast / Page top header -->
<h1 class="logo"><a tabindex="2" accesskey="1" href="/"><img src="/2008/site/images/logo-w3c-mobile-lg" width="90" height="53" alt="W3C" /></a> <span class="alt-logo">W3C</span></h1>
<div id="w3c_nav">
<form action="http://www.w3.org/Help/search" method="get" enctype="application/x-www-form-urlencoded">
<!-- w3c_sec_nav is populated through js -->
<div class="w3c_sec_nav"><!-- --></div>
<ul class="main_nav"><!-- Main navigation menu -->
<li class="first-item"><a href="/standards/">Standards</a></li>
<li><a href="/participate/">Participate</a></li>
<li><a href="/Consortium/membership">Membership</a></li>
<li class="last-item"><a href="/Consortium/">About W3C</a></li>
<li class="search-item">
<div id="search-form"><input tabindex="3" class="text" name="q" value="" title="Search" /> <button id="search-submit" name="search-submit" type="submit"><img class="submit" src="/2008/site/images/search-button" alt="Search" width="21" height="17" /></button></div>
</li>
</ul>
</form>
</div>
</div>
<!-- /end #w3c_mast -->
<div id="w3c_main">
<div id="w3c_logo_shadow" class="w3c_leftCol"><img width="100%" height="32" alt="" src="/2008/site/images/logo-shadow" /></div>
<div class="w3c_leftCol"><h2 class="offscreen">Site Navigation</h2>
<br /></div>
<div class="w3c_mainCol">
<!-- Generated from data/crumbs.php, ../../smarty/{crumbs.tpl} -->
<div id="w3c_crumbs">
<div id="w3c_crumbs_frame">
<ul class="bct"> <!-- .bct / Breadcrumbs -->
<li class="skip"><a tabindex="1" accesskey="2" title="Skip to content (e.g., when browsing via audio)" href="#w3c_content_body">Skip</a></li>
<li><a href="/">W3C</a> <span class="cr">»</span> </li>
<li><a href="/standards/">Standards</a> <span class="cr">»</span> </li>
<li><a href="/TR/">All Standards and Drafts</a> <span class="cr">»</span> </li>
<li class="current">Accessibility (All)</li>
</ul>
</div>
</div>
<h1 class="title">Accessibility (All)</h1>
<div class="w3c_toc"><!-- --></div>
<div id="w3c_content_body"><div id="w3c_generated_status">
<p id="w3c_toggle_include" class="default_open intro tPadding">This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
For related introductory information, see: <a href="http://www.w3.org/standards/webdesign/accessibility">Accessibility</a>.</p>
<h2 id="completed">Completed Work</h2>
<p>
<a href="/TR/tr-technology-stds">W3C Recommendations</a> have
been reviewed by W3C Members, by software developers, and by other
W3C groups and interested parties, and are endorsed by the
Director as Web Standards. Learn more about the <a href="/Consortium/Process/tr#rec-advance">W3C Recommendation
Track</a>.</p>
<p>
<a href="/2005/10/Process-20051014/tr.html#q75">Group Notes</a> are <em>not</em> standards and do not
have the same level of W3C endorsement.</p>
<h3 id="stds">Standards</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/WCAG20" title="Web Content Accessibility Guidelines (WCAG) 2.0 publication history">2008-12-11</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/">Web Content Accessibility Guidelines (WCAG) 2.0</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=WCAG20">translations</a>
·
<a href="http://www.w3.org/WAI/WCAG20/errata/">errata</a>
</p>
<div class="expand_description">
<p>Guidelines for making Web content more accessible to 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.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/UAAG10" title="User Agent Accessibility Guidelines 1.0 publication history">2002-12-17</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/2002/REC-UAAG10-20021217/">User Agent Accessibility Guidelines 1.0</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/WAI/UA/UAAG-translations">translations</a>
·
<a href="http://www.w3.org/WAI/UA/UAAG-errata">errata</a>
</p>
<div class="expand_description">
<p>This document provides guidelines for designing user agents that lower barriers to Web
accessibility for people with disabilities (visual, hearing, physical,
cognitive, and neurological). User agents include HTML browsers and other types
of software that retrieve and render Web content. A user agent that
conforms to these guidelines will
promote accessibility through its own user interface and through other internal
facilities, including its ability to communicate with other technologies
(especially assistive technologies).
Furthermore, all users, not just users with disabilities, should find
conforming user agents to be more usable.</p>
<p>In addition to helping developers of HTML browsers and media players, this
document will also benefit developers of assistive technologies because it
explains what types of information and control an assistive technology may
expect from a conforming user agent. Technologies not addressed directly by
this document (e.g., technologies for braille rendering) will be essential to
ensuring Web access for some users with disabilities.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/ATAG10" title="Authoring Tool Accessibility Guidelines 1.0 publication history">2000-02-03</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/2000/REC-ATAG10-20000203">Authoring Tool Accessibility Guidelines 1.0</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/WAI/AU/ATAG-ERRATA">errata</a>
</p>
<div class="expand_description">
<p>This specification provides guidelines for Web authoring tool
developers. Its purpose is two-fold: to assist developers in
designing authoring tools that produce accessible Web content and
to assist developers in creating an accessible authoring
interface.</p>
<p>Authoring tools can enable, encourage, and assist users
("authors") in the creation of accessible Web content through
prompts, alerts, checking and repair functions, help files and
automated tools. It is just as important that all people be able to
author content as it is for all people to have access to it. The
tools used to create this information must therefore be accessible
themselves. Adoption of these guidelines will contribute to the
proliferation of Web content that can be read by a broader range of
readers and authoring tools that can be used by a broader range of
authors.</p>
<p>This document is part of a series of accessibility documents
published by the <abbr>W3C</abbr> Web Accessibility Initiative
(<abbr>WAI</abbr>).</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/WAI-WEBCONTENT" title="Web Content Accessibility Guidelines 1.0 publication history">1999-05-05</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/">Web Content Accessibility Guidelines 1.0</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/WAI/GL/WAI-WEBCONTENT-ERRATA">errata</a>
</p>
<div class="expand_description">
<p>These guidelines explain how to make Web content accessible to people with disabilities; superceded by WCAG 2.0.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h3 id="notes">Group Notes</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/WCAG20-TECHS" title="Techniques for WCAG 2.0 publication history">2012-01-03</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/">Techniques for WCAG 2.0</a>
</h4>
<div class="expand_description">
<p>Specific authoring practices that may be used in support of WCAG 2.0. Includes general techniques, techniques for HTML, CSS, etc., and common failures.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/UNDERSTANDING-WCAG20" title="Understanding WCAG 2.0 publication history">2012-01-03</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/">Understanding WCAG 2.0</a>
</h4>
<div class="expand_description">
<p>Guide to understanding and implementing WCAG 2.0.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/xhtml-access" title="XHTML Access Module publication history">2010-12-16</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2010/NOTE-xhtml-access-20101216">XHTML Access Module</a>
</h4>
<div class="expand_description">
<p>The XHTML Access module defines an element that, when used in conjunction with other XHTML modules in XHTML Family Markup Languages, enables a more robust accessibility model than is presently
possible.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/mwbp-wcag" title="Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG) publication history">2009-07-09</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2009/NOTE-mwbp-wcag-20090709/">Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG)</a>
</h4>
<div class="expand_description">
<p>This technical report describes the similarities and differences between the <a href="http://www.w3.org/WAI/intro/wcag" shape="rect">Web Content Accessibility Guidelines (WCAG)</a> and the <a href="http://www.w3.org/TR/mobile-bp/" shape="rect">Mobile Web Best Practices 1.0</a>.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/wcag2-req" title="Requirements for WCAG 2.0 publication history">2006-04-25</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2006/NOTE-wcag2-req-20060425/">Requirements for WCAG 2.0</a>
</h4>
<div class="expand_description">
<p>Requirements used for development of WCAG 2.0.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/turingtest" title="Inaccessibility of CAPTCHA publication history">2005-11-23</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2005/NOTE-turingtest-20051123/">Inaccessibility of CAPTCHA</a>
</h4>
<div class="expand_description">
<p>
A common method of limiting access to services made available over the Web is visual verification of a bitmapped image. This presents a major problem to users who are blind, have low vision, or have a learning disability such as dyslexia. This document examines a number of potential solutions that allow systems to test for human users while preserving access by users with disabilities.
</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/UAAG10-TECHS" title="Techniques for User Agent Accessibility Guidelines 1.0 publication history">2002-12-17</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2002/NOTE-UAAG10-TECHS-20021217/">Techniques for User Agent Accessibility Guidelines
1.0</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/WAI/UA/UAAG-translations">translations</a>
</p>
<div class="expand_description">
<p>This document provides techniques for satisfying the checkpoints defined in
"User Agent Accessibility Guidelines 1.0"
<cite>[UAAG10]</cite>. These techniques address
key aspects of the accessibility of user interfaces, content rendering,
application programming interfaces (<acronym>APIs</acronym>), and languages
such as the Hypertext Markup Language
(<acronym>HTML</acronym>), Cascading Style
Sheets (<acronym>CSS</acronym>) and the
Synchronized Multimedia Integration Language
(<acronym>SMIL</acronym>).</p>
<p>The techniques listed in this document are not required for conformance to
the Guidelines. These techniques are not necessarily the only way of satisfying
the checkpoint, nor are they a definitive set of requirements for satisfying a
checkpoint.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/ATAG10-TECHS" title="Techniques for Authoring Tool Accessibility Guidelines 1.0 publication history">2002-10-29</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2002/NOTE-ATAG10-TECHS-20021029/">Techniques for Authoring Tool Accessibility Guidelines
1.0</a>
</h4>
<div class="expand_description">
<p>This document provides information to authoring tool developers who wish to satisfy the checkpoints of "Authoring Tool Accessibility Guidelines 1.0" [ATAG10]. It includes suggested techniques, sample strategies in deployed tools, and references to other accessibility resources (such as platform-specific software accessibility guidelines) that provide additional information on how a tool may satisfy each checkpoint.</p>
<p>This document is part of a series of accessibility documents published by
the <abbr>W3C</abbr> Web Accessibility Initiative
(<abbr>WAI</abbr>).</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/WCAG10-CSS-TECHS" title="CSS Techniques for Web Content Accessibility Guidelines 1.0 publication history">2000-11-06</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2000/NOTE-WCAG10-CSS-TECHS-20001106">CSS Techniques for Web Content Accessibility Guidelines 1.0</a>
</h4>
<div class="expand_description">
<p>This document describes techniques for authoring accessible Cascading Style
Sheets (<acronym>CSS</acronym>). Cascading Style
Sheets are defined by the W3C Recommendations "CSS Level 1" <cite>[CSS1]</cite> and "CSS
Level 2" <cite>
[CSS2]</cite>. This document is intended to help authors of Web content who
wish to claim conformance to "Web Content Accessibility Guidelines 1.0"
(<cite>[WCAG10]</cite>). While the techniques in
this document should help people author <acronym>CSS</acronym> that conforms to "Web Content
Accessibility Guidelines 1.0", these techniques are neither guarantees of
conformance nor the only way an author might produce conforming content.</p>
<p>This document is part of a series of documents about techniques for
authoring accessible Web content. For information about the other documents in
the series, please refer to "Techniques for Web Content Accessibility
Guidelines 1.0" <cite>[WCAG10-TECHS]</cite>.</p>
<p>
<strong>Note:</strong> This document contains a number of examples that
illustrate accessible solutions in CSS but also deprecated examples that
illustrate what content developers should not do. The deprecated examples are
highlighted and readers should approach them with caution -- they are meant for
illustrative purposes only.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/WCAG10-CORE-TECHS" title="Core Techniques for Web Content Accessibility Guidelines 1.0 publication history">2000-11-06</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2000/NOTE-WCAG10-CORE-TECHS-20001106">Core Techniques for Web Content Accessibility Guidelines 1.0</a>
</h4>
<div class="expand_description">
<p>Techniques that apply across technologies for authors of Web content who wish to claim conformance to WCAG 1.0</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/WCAG10-HTML-TECHS" title="HTML Techniques for Web Content Accessibility Guidelines 1.0 publication history">2000-11-06</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2000/NOTE-WCAG10-HTML-TECHS-20001106">HTML Techniques for Web Content Accessibility Guidelines 1.0</a>
</h4>
<div class="expand_description">
<p>This document describes techniques for authoring accessible Hypertext Markup
Language (<acronym>HTML</acronym>) content
(refer to HTML 4.01 <cite>
[HTML4]</cite>). This document is intended to help authors of Web content
who wish to claim conformance to "Web Content Accessibility Guidelines 1.0"
(<cite>[WCAG10]</cite>). While the techniques in
this document should help people author HTML that conforms to "Web Content
Accessibility Guidelines 1.0", these techniques are neither guarantees of
conformance nor the only way an author might produce conforming content.</p>
<p>This document is part of a series of documents about techniques for
authoring accessible Web content. For information about the other documents in
the series, please refer to "Techniques for Web Content Accessibility
Guidelines 1.0" <cite>[WCAG10-TECHS]</cite>.</p>
<p>
<strong>Note:</strong> This document contains a number of examples that
illustrate accessible solutions in CSS but also deprecated examples that
illustrate what content developers should not do. The deprecated examples are
highlighted and readers should approach them with caution -- they are meant for
illustrative purposes only.</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/WCAG10-TECHS" title="Techniques for Web Content Accessibility Guidelines 1.0 publication history">2000-11-06</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2000/NOTE-WCAG10-TECHS-20001106/">Techniques for Web Content Accessibility Guidelines 1.0</a>
</h4>
<div class="expand_description">
<p>Gateway to a series of related documents that provide techniques for satisfying the requirements defined in WCAG 1.0.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h2 id="drafts">Drafts</h2>
<p>Below are draft documents:
<a href="/2005/10/Process-20051014/tr.html#RecsCR">Candidate Recommendations</a>, <a href="/2005/10/Process-20051014/tr.html#last-call">Last Call Drafts</a>, <a href="/2005/10/Process-20051014/tr.html#RecsWD">other Working Drafts</a>.
Some of these may become Web Standards through the <a href="/Consortium/Process/tr#rec-advance">W3C Recommendation Track
process</a>. Others may be published as Group Notes or
become obsolete specifications.</p>
<h3 id="cr">Candidate Recommendations</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr class="lastRow">
<td class="table_datecol">
<a href="../history/wai-aria" title="Accessible Rich Internet Applications (WAI-ARIA) 1.0 publication history">2011-01-18</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is CR" href="http://www.w3.org/TR/2011/CR-wai-aria-20110118/">Accessible Rich Internet Applications (WAI-ARIA) 1.0</a>
</h4>
<div class="expand_description">
<p>Accessibility of Web content to people with disabilities requires semantic information about widgets, structures, and behaviors, in order to allow Assistive Technologies to make appropriate transformations. This specification
provides an ontology of roles, states, and properties that set out an abstract model for accessible interfaces and can be used to improve the accessibility
and interoperability of Web Content and Applications. This information can be mapped to accessibility frameworks
that use this information to provide alternative access solutions. Similarly,
this information can be used to change the rendering of content
dynamically using different style sheet properties. The result is an
interoperable method for associating behaviors with document-level markup. This document is part of the WAI-ARIA suite described in the ARIA Overview.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h3 id="lcwd">Last Call Drafts</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/wai-aria-implementation" title="WAI-ARIA 1.0 User Agent Implementation Guide publication history">2012-01-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is LCWD" href="http://www.w3.org/TR/2012/WD-wai-aria-implementation-20120110/">WAI-ARIA 1.0 User Agent Implementation Guide</a>
</h4>
<div class="expand_description">
<p>Describes how user agents should support keyboard
navigation, respond to roles, states, and properties provided in Web
content via WAI-ARIA, and expose this to accessibility APIs.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/EARL10-Schema" title="Evaluation and Report Language (EARL) 1.0 Schema publication history">2011-05-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is LCWD" href="http://www.w3.org/TR/2011/WD-EARL10-Schema-20110510/">Evaluation and Report Language (EARL) 1.0 Schema</a>
</h4>
<div class="expand_description">
<p>This document describes the formal schema of the Evaluation and Report Language (<acronym>EARL</acronym>) 1.0. The Evaluation and Report Language is a standardized vocabulary to express test results. The primary motivation for developing this language is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor neutral and platform independent format. It also provides reusable vocabulary for generic quality assurance and validation purposes. While this document focuses on the technical details of the specification, a companion document [Guide] describes the motivations for <acronym>EARL</acronym> and provides a tutorial introduction to its use.</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/role-attribute" title="Role Attribute 1.0 publication history">2011-01-13</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is LCWD" href="http://www.w3.org/TR/2011/WD-role-attribute-20110113/">Role Attribute 1.0</a>
</h4>
<div class="expand_description">
<p>This is a sample short description for this specification;
over time we will replace this description with a real one.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h3 id="wd">Other Working Drafts</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/media-accessibility-reqs" title="Media Accessibility User Requirements publication history">2012-01-03</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2012/WD-media-accessibility-reqs-20120103/">Media Accessibility User Requirements</a>
</h4>
<div class="expand_description">
<p>Aggregates requirements of a user with disabilities with respect to audio and video on the Web, providing background on user needs, alternative content technologies, and their application on the Web.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/ATAG20" title="Authoring Tool Accessibility Guidelines (ATAG) 2.0 publication history">2011-07-21</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-ATAG20-20110721/">Authoring Tool Accessibility Guidelines (ATAG) 2.0</a>
</h4>
<div class="expand_description">
<div>
<p>This specification provides guidelines for designing Web content authoring
tools that are more accessible for people with disabilities. An authoring
tool that conforms to these guidelines will promote accessibility by providing
an accessible user interface to authors with disabilities as well as enabling,
supporting, and promoting the production of accessible Web content by all
authors.</p>
</div>
<p>The "Authoring Tool Accessibility Guidelines 2.0" (<acronym>ATAG</acronym> 2.0)
is part of a series of accessibility guidelines published by the
<acronym>W3C</acronym> Web
Accessibility Initiative (<acronym>WAI</acronym>).</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/IMPLEMENTING-ATAG20" title="Implementing ATAG 2.0 publication history">2011-07-21</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-ATAG20-20110721/">Implementing ATAG 2.0</a>
</h4>
<div class="expand_description">
<p>Implementing ATAG 2.0 is an essential guide to understanding and using "Authoring Tool Accessibility Guidelines 2.0" [ATAG20]. Although the normative definitions and requirements for ATAG 2.0 can all be found in the ATAG 2.0 document itself, the concepts and provisions may be new to some people. Implementing ATAG 2.0 provides a non-normative extended commentary on each guideline and each success criterion to help readers better understand the intent and how the guidelines and success criteria work together. It also provides examples that the Working Group has identified for each success criterion.
</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/UAAG20" title="User Agent Accessibility Guidelines (UAAG) 2.0 publication history">2011-07-19</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-UAAG20-20110719/">User Agent Accessibility Guidelines (UAAG) 2.0</a>
</h4>
<div class="expand_description">
<p>This document provides guidelines for designing user agents that lower barriers to Web
accessibility for people with disabilities. User agents include browsers and other types
of software that retrieve and render Web content. A user agent that
conforms to these guidelines will
promote accessibility through its own user interface and through other internal
facilities, including its ability to communicate with other technologies
(especially assistive technologies).
Furthermore, all users, not just users with disabilities, should find
conforming user agents to be more usable.</p>
<p>In addition to helping developers of browsers and media players, this
document will also benefit developers of assistive technologies because it
explains what types of information and control an assistive technology may
expect from a conforming user agent. Technologies not addressed directly by
this document (e.g., technologies for braille rendering) will be essential to
ensuring Web access for some users with disabilities.</p>
<p>The "User Agent Accessibility Guidelines 2.0" (<acronym>UAAG</acronym> 2.0)
is part of a series of accessibility guidelines published by the <acronym>W3C</acronym> Web
Accessibility Initiative (<acronym>WAI</acronym>).</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/IMPLEMENTING-UAAG20" title="Implementing UAAG 2.0 publication history">2011-07-19</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-IMPLEMENTING-UAAG20-20110719/">Implementing UAAG 2.0</a>
</h4>
<div class="expand_description">
<p>This document provides explanation of the intent of UAAG 2.0 success criteria, examples of implementation of the UAAG 2.0 guidelines, best practice recommendations and additional resources for the guidelines.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/HTTP-in-RDF10" title="HTTP Vocabulary in RDF 1.0 publication history">2011-05-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-HTTP-in-RDF10-20110510/">HTTP Vocabulary in RDF 1.0</a>
</h4>
<div class="expand_description">
<p>The identification of resources on the Web by <acronym>URI</acronym> alone may not be sufficient, as other factors such as <acronym>HTTP</acronym> content negotiation might come into play. This issue is particularly significant for quality assurance testing, conformance claims, and reporting languages like the W3C Evaluation And Report Language (EARL). This document provides a representation of the HTTP vocabulary in <acronym>RDF</acronym>, to allow quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. The RDF terms defined by this document represent the core HTTP specification defined by <acronym>RFC</acronym> 2616, as well as additional HTTP headers registered by <acronym>IANA</acronym>. These terms can also be used to record <acronym>HTTPS</acronym> exchanges.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/Content-in-RDF10" title="Representing Content in RDF 1.0 publication history">2011-05-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-Content-in-RDF10-20110510/">Representing Content in RDF 1.0</a>
</h4>
<div class="expand_description">
<p>This document is a specification for a vocabulary to represent Content in <acronym>RDF</acronym>. This vocabulary is intended to provide a flexible framework within different usage scenarios to semantically represent any type of content, be it on the Web or in local storage media. For example, it can be used by Web accessibility evaluation tools to record a representation of the assessed Web content in an Evaluation And Report Language (EARL) 1.0 Schema evaluation report. The document contains introductory information on its usage and some examples.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/Pointers-in-RDF10" title="Pointer Methods in RDF 1.0 publication history">2011-05-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-Pointers-in-RDF10-20110510/">Pointer Methods in RDF 1.0</a>
</h4>
<div class="expand_description">
<p>Add content here.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/EARL10-Guide" title="Developer Guide for Evaluation and Report Language (EARL) 1.0 publication history">2011-05-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-EARL10-Guide-20110510/">Developer Guide for Evaluation and Report Language (EARL) 1.0</a>
</h4>
<div class="expand_description">
<p>This document is an introductory guide to the Evaluation and Report Language (EARL) 1.0. EARL is a vocabulary, the terms of which are defined across a set of specifications and technical notes, that is used to describe test results. The primary motivation for developing this vocabulary is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor-neutral and platform-independent format. </p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/wai-aria-practices" title="WAI-ARIA 1.0 Authoring Practices publication history">2010-09-16</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2010/WD-wai-aria-practices-20100916/">WAI-ARIA 1.0 Authoring Practices</a>
</h4>
<div class="expand_description">
<p>This document specifies Best Practices for delivering accessible rich internet applications using <cite>WAI-ARIA</cite> [<cite>ARIA</cite>]. The principle objective is to produce a usable, accessible experience over the Web. It provides recommended approaches to create accessible Web content using WAI-ARIA roles, states, and properties to make widgets, navigation, and behaviors accessible. The document also describes considerations that might not be evident to most implementers from the WAI-ARIA specification alone. This document is directed primarily to Web application developers, but the guidance is also useful to user agent and assistive technology developers. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/wai-aria-primer" title="WAI-ARIA 1.0 Primer publication history">2010-09-16</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2010/WD-wai-aria-primer-20100916/">WAI-ARIA 1.0 Primer</a>
</h4>
<div class="expand_description">
<p>The <acronym>WAI</acronym>-<acronym>ARIA</acronym> Primer introduces developers to the use of WAI-ARIA [ARIA] for addressing the
accessibility of dynamic Web content for people with disabilities.
This primer explains the accessibility problems posed by hybrid technologies
such as DHTML and Ajax. It introduces the technologies to map controls, Ajax live regions, and
events to accessibility APIs, including custom controls used for Rich Internet Applications. The
primer also describes new navigation techniques to mark common Web
elements such as menus, primary content, secondary content, banner
information and other types of Web structures. These new
technologies can be used to improve the accessibility and usability
of Web resources by people with disabilities, without extensive
modification to existing libraries of Web resources. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/wai-age-literature" title="Web Accessibility for Older Users: A Literature Review publication history">2008-05-14</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/">Web Accessibility for Older Users: A Literature Review</a>
</h4>
<div class="expand_description">
<p>This document provides a review and analysis of guidelines and articles relating to the needs of older people with Web accessibility needs due to ageing, and compares these with the needs of people with disabilities as already addressed in WAI guidelines. The focus is particularly on Europe but applies internationally as well. This review is being undertaken in order to inform the development of educational materials which can better promote the needs of people who have accessibility needs due to ageing, and potential development of profiles and/or extensions on WAI guidelines.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/wai-aria-roadmap" title="Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap) publication history">2008-02-04</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2008/WD-wai-aria-roadmap-20080204/">Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap)</a>
</h4>
<div class="expand_description">
<p>The Roadmap for Accessible Rich Internet Applications addresses the
accessibility of dynamic Web content for people with disabilities.
The roadmap introduces the technologies to map controls, Ajax live regions, and
events to accessibility APIs, including custom controls used for Rich Internet Applications. The
roadmap also describes new navigation techniques to mark common Web
structures as menus, primary content, secondary content, banner
information and other types of Web structures. These new
technologies can be used to improve the accessibility and usability
of Web resources by people with disabilities, without extensive
modification to existing libraries of Web resources. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/UAAG20-requirements" title="User Agent Accessibility Guidelines 2.0 Requirements publication history">2007-10-31</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2007/WD-UAAG20-requirements-20071031/">User Agent Accessibility Guidelines 2.0 Requirements</a>
</h4>
<div class="expand_description">
<p>This First Public Working Draft outlines the requirements that the User Agent Accessibility
Guidelines Working Group (UAWG) has set for development of User Agent
Accessibility Guidelines 2.0 (UAAG 2.0). These requirements are based on feedback from
the use of UAAG 1.0 and will be used to determine if the UAWG has met
its goals as UAAG 2.0 advances through the W3C
Recommendation Track Process.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/xag" title="XML Accessibility Guidelines publication history">2002-10-03</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2002/WD-xag-20021003">XML Accessibility Guidelines</a>
</h4>
<div class="expand_description">
<p>Requirements intended to be used for development of WCAG 2.0 Techniques, superceded by later plans.</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/ATAG-wombat" title="Authoring Tool Accessibility Guidelines "Wombat" publication history">2001-12-21</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2001/WD-ATAG-wombat-20011221/">Authoring Tool Accessibility Guidelines "Wombat"</a>
</h4>
<div class="expand_description">
<p>This specification provides guidelines for Web authoring tool developers.
Its purpose is two-fold: to assist developers in designing authoring tools
that produce accessible Web content and to assist developers in creating an
accessible authoring interface.</p>
<p>Authoring tools can enable, encourage, and assist users ("authors") in the
creation of accessible Web content through prompts, alerts, checking and
repair functions, help files and automated tools. It is just as important
that all people be able to author content as it is for all people to have
access to it. The tools used to create this information must therefore be
accessible themselves. Adoption of these guidelines will contribute to the
proliferation of Web content that can be read by a broader range of readers
and authoring tools that can be used by a broader range of authors.</p>
<p>This document is part of a series of accessibility documents published by
the <abbr>W3C</abbr> Web Accessibility Initiative (<abbr>WAI</abbr>).</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h2 id="obsolete">Obsolete Specifications</h2>
<p>These specifications have either been superseded by others,
or have been abandoned. They remain available for archival
purposes, but are not intended to be used.</p>
<h3 id="retired">
Retired
</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/wcag2-tech-req" title="Requirements for WCAG 2.0 Checklists and Techniques publication history">2003-02-07</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/2003/WD-wcag2-tech-req-20030207/">Requirements for WCAG 2.0 Checklists and Techniques</a>
</h4>
<div class="expand_description">
<p>This is a W3C Working Draft produced by the Web Content Accessibility Guidelines Working
Group (WCAG WG). It describes requirements for Checklists and Techniques described by the Web Content Accessibility Guidelines 2.0 (WCAG 2.0). These requirements are related to but different from Requirements for
WCAG 2.0 in that "Requirements for WCAG 2.0 Checklists and Techniques"
specifies requirements for the technology-specific documents produced by
the WCAG WG while "Requirements for WCAG 2.0" specifies general
requirements for the general usability of documents produced by the WCAG
WG. The Working Group encourages feedback about these requirements as well
as participation in the development of WCAG 2.0 by people who have
experience creating Web content that conforms to Web Content Accessibility Guidelines 1.0. </p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/AERT" title="Techniques For Accessibility Evaluation And Repair Tools publication history">2000-04-26</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/2000/WD-AERT-20000426">Techniques For Accessibility Evaluation And Repair Tools</a>
</h4>
<div class="expand_description">
<p>This document describes techniques that Web accessibility
validation tools may use to evaluate the conformance of HTML
documents to the Web
Content Accessibility Guidelines 1.0 (WCAG 1.0). This document
also describes techniques that Web authoring tools may use to help
authors modify HTML documents to conform to WCAG 1.0. We anticipate
that tool developers may develop accessibility validation and/or
repair modules to be incorporated into commercial authoring tools,
validation tools, and perhaps user agents.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div></div>
</div>
</div>
</div>
<!-- Generated from data/footer.php, ../../smarty/{footer-block.tpl} -->
<div id="w3c_footer">
<div id="w3c_footer-inner">
<h2 class="offscreen">Footer Navigation</h2>
<div class="w3c_footer-nav">
<h3>Navigation</h3>
<ul class="footer_top_nav">
<li><a href="/">Home</a></li>
<li><a href="/standards/">Standards</a></li>
<li><a href="/participate/">Participate</a></li>
<li><a href="/Consortium/membership">Membership</a></li>
<li class="last-item"><a href="/Consortium/">About W3C</a></li>
</ul>
</div>
<div class="w3c_footer-nav">
<h3>Contact W3C</h3>
<ul class="footer_bottom_nav">
<li><a href="/Consortium/contact">Contact</a></li>
<li><a accesskey="0" href="/Help/">Help and FAQ</a></li>
<li><a href="/Consortium/sponsor/">Sponsor / Donate</a></li>
<li><a href="/Consortium/siteindex">Site Map</a></li>
<li>
<address id="w3c_signature"><a href="mailto:site-comments@w3.org">Feedback</a> (<a href="http://lists.w3.org/Archives/Public/site-comments/">archive</a>)</address>
</li>
</ul>
</div>
<div class="w3c_footer-nav">
<h3>W3C Updates</h3>
<ul class="footer_follow_nav">
<li><a href="http://twitter.com/W3C" title="Follow W3C on Twitter"><img src="/2008/site/images/twitter-bird" alt="Twitter" class="social-icon" width="78" height="83" /></a>
<a href="http://identi.ca/w3c" title="See W3C on Identica"><img src="/2008/site/images/identica-logo" alt="Identica" class="social-icon" width="91" height="83" /></a></li>
</ul>
</div>
<!-- #footer address / page signature -->
<p class="copyright">Copyright © 2012 W3C <sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
<a href="http://www.keio.ac.jp/">Keio</a>) <a href="/Consortium/Legal/ipr-notice">Usage policies
apply</a>.</p>
</div>
</div>
<!-- /end #footer -->
<!-- Generated from data/scripts.php, ../../smarty/{scripts.tpl} -->
<div id="w3c_scripts"><script type="text/javascript" src="/2008/site/js/main">
//<![CDATA[
<!-- -->
//]]>
</script></div>
</body>
</html>