The W3C's Web Accessibility Initiative
Note:
This page was created for use in my former classes. It is only occasionally
updated resulting in many links being more of historical rather than current usefulness. Over time many links will suffer link rot.
“Time spent with cats is never wasted.”
Sidonie-Gabrielle Colette
- WAI Accessibility Guidelines
- Checklist of Checkpoints
for Web Content Accessibility Guidelines 1.0
- List
of Checkpoints for Web Content Accessibility Guidelines 1.0
- Fact Sheet for Web Content
Accessibility Guidelines 1.0
- WAI
A Compliance [Web-Savvy]
- WAI
Double-A Compliance [Web-Savvy]
- WAI
AAA Compliance [Web-Savvy]
Techniques
- Techniques for Web
Content Accessibility Guidelines 1.0
- Techniques for Accessibility Evaluation
and Repair
- Accessibility improvements
in HTML 4.0
- Creating Pages that Conform to
WCAG 1.0
- Accessibility Features of CSS
- Accessibility Features of SVG
- Accessibility Features of SMIL
- XML Accessibility Guidelines
Evaluation and Repair Tools
- Evaluating Web Sites for Accessibility
- Evaluation and Repair Tools
WAI vs 508
- Section
508 Web Standards & WCAG Priority 1 Checkpoints: A Side-by-side Comparison
- Section 508 and WCAG
Sidebar
Web Content Accessibility Guidelines 2.0 W3C Working Draft
22 August 2002
- Web Content Accessibility Guidelines
2.0
- Checkpoint
Mapping Between WCAG 1.0 and the WCAG 2.0 Working Draft
The WAI page authoring recommendations are organized by priority as follows:
[Priority 1] - A Compliance
A Web content developer must satisfy this checkpoint. Otherwise,
one or more groups will find it impossible to access information in the document.
Satisfying this checkpoint is a basic requirement for some groups to be able
to use Web documents.
[Priority 2] - AA Compliance
A Web content developer should satisfy this checkpoint. Otherwise,
one or more groups will find it difficult to access information in the document.
Satisfying this checkpoint will remove significant barriers to accessing Web
documents.
[Priority 3] - AAA Compliance
A Web content developer may address this checkpoint. Otherwise,
one or more groups will find it somewhat difficult to access information in
the document. Satisfying this checkpoint will improve access to Web documents.
The 14 WAI Accessibility Guidelines
Guideline, Technique, Checkpoint, Example, Tutorial
- Provide equivalent alternatives to auditory and visual content. W3C
Tech
Ck Ex
WebAim
- Don't rely on color alone. W3C
Tech Ck Ex
WebAim
- Use markup and style sheets and do so properly. W3C
Tech
Ck Ex
WebAim
- Clarify natural language usage. W3C
Tech
Ck Ex
WebAim
- Create tables that transform gracefully. W3C
Tech
Ck Ex
WebAim
- Ensure that pages featuring new technologies transform gracefully. W3C
Tech
Ck Ex
WebAim
- Ensure user control of time-sensitive content changes. W3C
Tech
Ck Ex
WebAim
- Ensure direct accessibility of embedded user interfaces. W3C
Tech
Ck Ex
WebAim
- Design for device-independence. W3C
Tech
Ck Ex
WebAim
- Use interim solutions. W3C
Tech
Ck Ex
WebAim
- Use W3C technologies and guidelines. W3C
Tech Ck Ex
WebAim
- Provide context and orientation information. W3C
Tech
Ck Ex
WebAim
- Provide clear navigation mechanisms. W3C
Tech
Ck Ex
WebAim
- Ensure that documents are clear and simple. W3C
Tech
Ck Ex
WebAim
If a web site is WCAG A-Compliant and its author wants to be Section
508 compliant as well, these are the five standards
he must address additionally. These are paragraphs 1194.22 (l),
(m),
(n),
(o), and (p).
** Home ** Class
Pages ** Site Map **
David J. Hark
HARK/INTERNET-HELP,Inc.
P. O. Box 201 Shepherdstown, WV 25443-0201
304-876-2607
dhark@fred.net
dhark@intrepid.net
http://www.dhark.com
http://www.fred.net/dhark
Last updated: 13 November 2002
© 2002 David J. Hark