2. Don??™t rely on color alone.
3. Use markup and style sheets and do so properly.
4. Clarify natural language usage.
5. Create tables that transform gracefully.
6. Ensure that pages featuring new technologies transform gracefully.
7. Ensure user control of time-sensitive content changes.
8. Ensure direct accessibility of embedded user interfaces.
9. Design for device-independence.
10. Use interim solutions.
11. Use W3C technologies and guidelines.
12. Provide context and orientation information.
13. Provide clear navigation mechanisms.
14. Ensure that documents are clear and simple.
WCAG 2.0
WCAG 2.0 arrived in 2006 and saw both criticism and praise from developers all over the
Web. Many considered it a major step forward, while others, like accessibility consultant
Joe Clark, blasted it as a major step backward.8 In essence, the WAI shifted away from the
ACCESSIBILITY
43
3
7. W3C, ???Web Content Accessibility Guidelines 1.0??? (www.w3.org/TR/WAI-WEBCONTENT/
#Guidelines).
8. Joe Clark, ???To Hell with WCAG 2,??? A List Apart, May 2006 (www.alistapart.com/articles/
tohellwithwcag2).
technique-centric approach and rewrote the guidelines by principle.
Pages:
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