index.html
39 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
<?xml version="1.0"?>
<!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">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Accessibility - W3C Blog - Category Archives</title>
<style type="text/css" media="all">
@import "/QA/2006/01/blogstyle.css";
</style>
<meta name="keywords" content="W3C, QA, weblog, blog" />
<meta name="description" content="Archives for the W3C Questions and Answers Weblog - Category Accessibility" />
<meta name="revision" content="$Id: index.html,v 1.269 2012/01/13 07:42:06 mirror Exp $" />
<link rel="alternate" type="application/atom+xml" title="Atom" href="http://www.w3.org/QA/atom.xml" />
<link rel="alternate" type="application/rss+xml" title="RSS 1.0" href="http://www.w3.org/QA/news.rss" />
<link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://www.w3.org/QA/rsd.xml" />
</head>
<body>
<div id="banner">
<h1 id="title">
<a href="http://www.w3.org/"><img height="48" alt="W3C" id="logo" src="http://www.w3.org/Icons/WWW/w3c_home_nb" /></a>
W3C Blog - Archives
</h1>
</div>
<ul class="navbar" id="menu">
<li><strong><a href="/QA/" title="W3C Blog Home">[ W3C Blog ]</a></strong></li>
<li><a href="/QA/Library/" title="Documents and Publications on Web and Quality">Documents</a></li>
<li><a href="/QA/Tools/" accesskey="3" title="Validators and other Tools">Tools</a></li>
<li><a href="/2007/12/qa-blog-help/index#feedback">Feedback</a></li>
</ul>
<div id="searchbox">
<form method="get" action="http://www.google.com/custom" enctype="application/x-www-form-urlencoded">
<p id="formbox"><input type="text" size="15" class="textfield" name="q" accesskey="E" maxlength="255" /> <input type="submit" class="submitfield" value="Search" id="goButton" name="sa" accesskey="G" /> <input type="hidden" name="cof" value="T:black;LW:72;ALC:#ff3300;L:http://www.w3.org/Icons/w3c_home;LC:#000099;LH:48;BGC:white;AH:left;VLC:#660066;GL:0;AWFID:0b9847e42caf283e;" /><input type="hidden" id="searchW3C" name="sitesearch" checked="checked" value="www.w3.org/QA" /><input type="hidden" name="domains" value="www.w3.org/QA" /></p>
</form>
</div>
<div id="main"><!-- This DIV encapsulates everything in this page - necessary for the positioning -->
<h2>Archives for Category: Accessibility</h2>
<h3><a href="http://www.w3.org/QA/2011/05/html5-lastcall-accessibility.html">Ensuring Accessibility Support in HTML5</a></h3>
<p><p>HTML5 was <a href="http://www.w3.org/News/2011#entry-9105">announced as a W3C Last Call Working Draft</a> on 25 May 2011. The <a href="http://www.w3.org/2011/05/html5lc-pr.html">W3C press release </a> invites broad review to determine to what extent HTML5 has met its technical requirements and dependencies. The <a href="http://www.w3.org/WAI/"> Web Accessibility Initiative (WAI)</a> encourages your comments and participation.</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2011/05/html5-lastcall-accessibility.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Brewer/">Judy Brewer</a> on May 31, 2011 5:35 AM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/egov/">eGov</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2011/05/html5-lastcall-accessibility.html">Permalink</a>
| <a href="http://www.w3.org/QA/2011/05/html5-lastcall-accessibility.html#comments">Comments (2)</a>
| <a href="http://www.w3.org/QA/2011/05/html5-lastcall-accessibility.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2011/01/wai-aria-cr.html">Accessible Rich Internet Applications (WAI-ARIA) moves to Candidate Recommendation (CR)</a></h3>
<p><p>Today the <a href="http://www.w3.org/WAI/PF/">Protocols and Formats Working<br />
Group (PFWG)</a> published <a href="http://www.w3.org/TR/2011/CR-wai-aria-20110118/">WAI-ARIA<br />
1.0 as a Candidate Recommendation</a>. This is a major milestone in development of<br />
this technology, indicating that it is considered feature complete after<br />
years of development and multiple public consultations. As ARIA enters the Candidate Recommendation phase, the focus shifts from specification<br />
development to <a href="http://www.w3.org/WAI/ARIA/1.0/CR/">implementation testing</a>. </p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2011/01/wai-aria-cr.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/cooper/">Michael Cooper</a> on January 18, 2011 5:12 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/publications/">Publications</a>, <a href="http://www.w3.org/QA/archive/technology/">Technology</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/">W3C・QA News</a>, <a href="http://www.w3.org/QA/archive/technology/web_applications_1/">Web Applications</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2011/01/wai-aria-cr.html">Permalink</a>
| <a href="http://www.w3.org/QA/2011/01/wai-aria-cr.html#comments">Comments (3)</a>
| <a href="http://www.w3.org/QA/2011/01/wai-aria-cr.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2010/10/new_and_improved_wcag_20_techn.html">New and Improved WCAG 2.0 Techniques</a></h3>
<p><p>Today W3C WAI published updated Techniques for WCAG 2.0 and Understanding WCAG 2.0, following a public review and comment period. The WCAG Working Group is developing more techniques and would like your help...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2010/10/new_and_improved_wcag_20_techn.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Shawn/">Shawn Henry</a> on October 14, 2010 1:14 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/publications/">Publications</a>, <a href="http://www.w3.org/QA/archive/technology/web_design/">Web Design</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2010/10/new_and_improved_wcag_20_techn.html">Permalink</a>
| <a href="http://www.w3.org/QA/2010/10/new_and_improved_wcag_20_techn.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2010/10/new_and_improved_wcag_20_techn.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2010/06/make_your_presentations_access.html">Make Your Presentations Accessible to All</a></h3>
<p><em>Do you remember a time when people around you broke out in laughter,
but you didn't hear the joke? You could be doing a similar thing to your audience — leaving some
people out....</em> Read on to learn how to make presentations, talks, meetings, and training accessible to all
of your potential audience, including people with disabilities and others...</p>
<p class="readmore"><a href="http://www.w3.org/QA/2010/06/make_your_presentations_access.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Shawn/">Shawn Henry</a> on June 15, 2010 3:45 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/publications/">Publications</a>, <a href="http://www.w3.org/QA/archive/web_spotting/reference/">Reference</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/technology_101/">Technology 101</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/tools/">Tools</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/w3c_life/">W3C Life</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2010/06/make_your_presentations_access.html">Permalink</a>
| <a href="http://www.w3.org/QA/2010/06/make_your_presentations_access.html#comments">Comments (1)</a>
| <a href="http://www.w3.org/QA/2010/06/make_your_presentations_access.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2010/06/the_mission_of_w3c.html">The Mission of W3C</a></h3>
<p><p>I've now been with W3C for almost three months. My first priority was to meet with the global stakeholders of the organization. I began with W3C membership. Through meetings, phone calls, technical conferences, and informal sessions I've met upwards of...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2010/06/the_mission_of_w3c.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Jeff/">Jeff Jaffe</a> on June 1, 2010 2:20 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/ceo/">CEO</a>, <a href="http://www.w3.org/QA/archive/technology/">Technology</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/">W3C・QA News</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2010/06/the_mission_of_w3c.html">Permalink</a>
| <a href="http://www.w3.org/QA/2010/06/the_mission_of_w3c.html#comments">Comments (3)</a>
| <a href="http://www.w3.org/QA/2010/06/the_mission_of_w3c.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2010/01/encourage_accessibility_make_a_difference.html">Take a few minutes to encourage web accessibility. You can make a difference.</a></h3>
<p><p>What do you do when you come across an inaccessible website?. . .<br /><br />
...WAI just published: <a href="http://www.w3.org/WAI/users/inaccessible">Contacting Organizations about Inaccessible Websites</a>. It walks through steps, provides lots of tips, and includes sample e-mails...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2010/01/encourage_accessibility_make_a_difference.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Shawn/">Shawn Henry</a> on January 6, 2010 12:00 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions & Editorial</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/publications/">Publications</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2010/01/encourage_accessibility_make_a_difference.html">Permalink</a>
| <a href="http://www.w3.org/QA/2010/01/encourage_accessibility_make_a_difference.html#comments">Comments (19)</a>
| <a href="http://www.w3.org/QA/2010/01/encourage_accessibility_make_a_difference.html#trackback">TrackBacks (2)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/12/share_resources_supporting_the.html">Share Resources Supporting the Web Accessibility Business Case</a></h3>
<p><p>W3C WAI today published a collection of statistics, case studies, and articles supporting the business case for web accessibility in <a href="/WAI/bcase/resources.html"><strong>Resources for Developing a Web Accessibility Business Case for Your Organization</strong></a>.... Would your organization be willing to share your case study to support the business case for web accessibility?...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/12/share_resources_supporting_the.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Shawn/">Shawn Henry</a> on December 14, 2009 3:21 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/publications/">Publications</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/12/share_resources_supporting_the.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/12/share_resources_supporting_the.html#comments">Comments (2)</a>
| <a href="http://www.w3.org/QA/2009/12/share_resources_supporting_the.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/12/discover_new_ways_of_thinking.html">Discover new ways of thinking about accessibility</a></h3>
<p><p>As an employee of the W3C Web standards organization, you might think that I would say the most important thing to start with when addressing web accessibility is standards. I don't. I say the first step is learning how people with disabilities use the web. You might be surprised to learn that is the W3C's advice. We've now got it more clearly in writing, in the new document published today by the W3C Web Accessibility Initiative (WAI): Involving Users in Web Projects for Better, Easier Accessibility<br />
and...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/12/discover_new_ways_of_thinking.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Shawn/">Shawn Henry</a> on December 9, 2009 1:02 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions & Editorial</a>, <a href="http://www.w3.org/QA/archive/web_spotting/reference/">Reference</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/12/discover_new_ways_of_thinking.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/12/discover_new_ways_of_thinking.html#comments">Comments (5)</a>
| <a href="http://www.w3.org/QA/2009/12/discover_new_ways_of_thinking.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/11/w3c_cheatsheet_for_developers.html">W3C Cheatsheet for developers</a></h3>
<p><p>Yesterday, as part of the W3C Technical Plenary day, I got the opportunity to introduce a new tool that I had been working on over the past few weeks, the W3C Cheatsheet for Web developers. This cheatsheet aims at providing...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/11/w3c_cheatsheet_for_developers.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Dom/">Dominique Hazaël-Massieux</a> on November 5, 2009 9:47 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/css/">CSS</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/internationalization/">Internationalization</a>, <a href="http://www.w3.org/QA/archive/technology/mobile/">Mobile</a>, <a href="http://www.w3.org/QA/archive/technology/svg/">SVG</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/tools/">Tools</a>, <a href="http://www.w3.org/QA/archive/web_spotting/tutorials/">Tutorials</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/11/w3c_cheatsheet_for_developers.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/11/w3c_cheatsheet_for_developers.html#comments">Comments (22)</a>
| <a href="http://www.w3.org/QA/2009/11/w3c_cheatsheet_for_developers.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/06/wcag_20_in_your_mother_tongue.html">WCAG 2.0 in your mother tongue</a></h3>
<p><p>I come from Egypt, live in Austria, work in France, and when I start speaking, some people think I'm American. I speak fluent German and English, but no matter what I do, some expressions and thoughts will always be easier...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/06/wcag_20_in_your_mother_tongue.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/shadi/">Shadi Abou-Zahra</a> on June 26, 2009 5:04 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/internationalization/">Internationalization</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions & Editorial</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/publications/">Publications</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/06/wcag_20_in_your_mother_tongue.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/06/wcag_20_in_your_mother_tongue.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2009/06/wcag_20_in_your_mother_tongue.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/01/javascript_required_for_basic.html">JavaScript required for basic textual info? TRY AGAIN</a></h3>
<p><p>Sam says he's Online and Airborne. "Needless to say, this is seriously cool." I'll say! But when I follow the link to details from the service provider, I get:Sorry. You must have JavaScript enabled to view this page. Click the...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/01/javascript_required_for_basic.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on January 27, 2009 10:01 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/security/">Security</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/01/javascript_required_for_basic.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/01/javascript_required_for_basic.html#comments">Comments (8)</a>
| <a href="http://www.w3.org/QA/2009/01/javascript_required_for_basic.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/12/social_networks_at_w3c_foresee.html">Social networks at W3C: foreseeing a 2009 success story!</a></h3>
<p><p>The W3C social networks workshop is already a blast and it hasn't happened yet! We received a record number (72) of interesting position papers from a wide range of key players. Have a look at the impressive list (papers and...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/12/social_networks_at_w3c_foresee.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/mcf/">Marie-Claire Forgue</a> on December 23, 2008 4:10 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/mobile/">Mobile</a>, <a href="http://www.w3.org/QA/archive/workshops/">Workshops</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/12/social_networks_at_w3c_foresee.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/12/social_networks_at_w3c_foresee.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2008/12/social_networks_at_w3c_foresee.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/12/a_personal_reflection_on_wcag20.html">A personal reflection on the WCAG 2.0 publication</a></h3>
<p>Today W3C WAI published Web Content Accessibility Guidelines (<a href="http://www.w3.org/TR/WCAG20/">WCAG</a>) 2.0. This is a momentous occasion. <a href="http://www.w3.org/QA/2008/12/wcag_20_is_finalized.html">Another post</a> links to the official announcements. Here is another perspective, my personal perspective...</p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/12/a_personal_reflection_on_wcag20.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Shawn/">Shawn Henry</a> on December 11, 2008 3:11 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/publications/">Publications</a>, <a href="http://www.w3.org/QA/archive/technology/">Technology</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/w3c_life/">W3C Life</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/">W3C・QA News</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/12/a_personal_reflection_on_wcag20.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/12/a_personal_reflection_on_wcag20.html#comments">Comments (1)</a>
| <a href="http://www.w3.org/QA/2008/12/a_personal_reflection_on_wcag20.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/12/wcag_20_is_finalized.html">A New Era for Web Accessibility: WCAG 2.0 is Finalized</a></h3>
<p><a href="http://www.w3.org/TR/WCAG20/">WCAG 2.0</a> was published today as a final Web Standard "W3C Recommendation". Check out the official <a href="http://www.w3.org/News/2008#item210">announcement</a>, <a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2008OctDec/0152.html">e-mail</a>, <a href="http://www.w3.org/2008/12/wcag20-pressrelease.html">press release</a>, <a href="http://www.w3.org/2008/12/wcag20-testimonial">testimonials</a>, and <a href="http://www.w3.org/QA/2008/12/a_personal_reflection_on_wcag20.html">a personal reflection on WCAG</a>. Here are some additional perspectives on a few points...</p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/12/wcag_20_is_finalized.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Shawn/">Shawn Henry</a> on December 11, 2008 2:49 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/mobile/">Mobile</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/publications/">Publications</a>, <a href="http://www.w3.org/QA/archive/technology/">Technology</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/">W3C・QA News</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/12/wcag_20_is_finalized.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/12/wcag_20_is_finalized.html#comments">Comments (11)</a>
| <a href="http://www.w3.org/QA/2008/12/wcag_20_is_finalized.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/11/with_real_world_implementation.html">With real world implementations WCAG 2.0 steps closer to expected December 2008 publication</a></h3>
<p><p>Today W3C WAI <a href="http://lists.w3.org/Archives/Public/w3c-wai-ig/2008OctDec/0091.html">published WCAG 2.0 as a "W3C Proposed Recommendation"</a>. This means that the technical material of WCAG 2.0 is complete and it has been used successfully in real websites. <strong>Up next: final publication as a Web standard, which we expect in December!</strong></p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/11/with_real_world_implementation.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Shawn/">Shawn Henry</a> on November 3, 2008 6:34 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/publications/">Publications</a>, <a href="http://www.w3.org/QA/archive/technology/">Technology</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/technology_101/">Technology 101</a>, <a href="http://www.w3.org/QA/archive/technology/video/">Video</a>, <a href="http://www.w3.org/QA/archive/technology/egov/">eGov</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/11/with_real_world_implementation.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/11/with_real_world_implementation.html#comments">Comments (6)</a>
| <a href="http://www.w3.org/QA/2008/11/with_real_world_implementation.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/08/css-wg-give-me-a-break.html">Give me a break! CSS WG meeting</a></h3>
<p><p>CSS WG is meeting in Cambridge, UK and had an interesting discussion about br element and possible associated CSS properties.</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/08/css-wg-give-me-a-break.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/karl/">Karl Dubost</a> on August 22, 2008 5:59 AM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/css/">CSS</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions & Editorial</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/08/css-wg-give-me-a-break.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/08/css-wg-give-me-a-break.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2008/08/css-wg-give-me-a-break.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/08/the-digital-stakhanovite.html">The Digital Stakhanovite</a></h3>
<p><p>Designing a technology that will accomodate our social contexts of the digital Stakhanovite is a big challenge, far to be simple to solve.</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/08/the-digital-stakhanovite.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/karl/">Karl Dubost</a> on August 18, 2008 2:18 AM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions & Editorial</a>, <a href="http://www.w3.org/QA/archive/technology/semantic_web/">Semantic Web</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/08/the-digital-stakhanovite.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/08/the-digital-stakhanovite.html#comments">Comments (1)</a>
| <a href="http://www.w3.org/QA/2008/08/the-digital-stakhanovite.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/07/web-standards-curriculum.html">Once Upon A Time, Web Standards Curriculum </a></h3>
<p><p>Once upon a time, we started the Quality Assurance activity at W3C in 2001, one of the objectives was to find a way to improve the materials for communicating with Web developers. In the QA group, Snorre M. Grimsby (Opera) told me that we might find resources for producing educational materials. The discussion became quiet for a while and restarted in June 2006 with <a href="http://my.opera.com/dstorey/blog/">David Storey</a> (Opera). As the same time, some people at <a href="http://webstandards.org/">WASP</a> started a survey for defining requirements for a Web Standards Curriculum. </p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/07/web-standards-curriculum.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/karl/">Karl Dubost</a> on July 10, 2008 5:40 AM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/css/">CSS</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions & Editorial</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/technology_101/">Technology 101</a>, <a href="http://www.w3.org/QA/archive/web_spotting/tutorials/">Tutorials</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/07/web-standards-curriculum.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/07/web-standards-curriculum.html#comments">Comments (3)</a>
| <a href="http://www.w3.org/QA/2008/07/web-standards-curriculum.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/05/web-accessibility-older-users.html">My Arms Are WAI Too Short</a></h3>
<p><p>Web Accessibility for Older Users is a report on the needs and the issues that older adults face when using the Web.</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/05/web-accessibility-older-users.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/karl/">Karl Dubost</a> on May 15, 2008 2:50 AM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions & Editorial</a>, <a href="http://www.w3.org/QA/archive/web_spotting/reference/">Reference</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/05/web-accessibility-older-users.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/05/web-accessibility-older-users.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2008/05/web-accessibility-older-users.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/04/wcag20_cr_april2008.html">WCAG 2.0 takes a giant leap forward — Now it's your turn</a></h3>
<p>WCAG 2.0 is going, boldly, where it's never gone before: Today WCAG 2.0 is at "W3C Candidate Recommendation"! Can you feel the Web accessibility world shake? Candidate Recommendation means that we think the technical content is stable and we want developers and designers to start using WCAG 2.0, to test it out in every-day situations....</p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/04/wcag20_cr_april2008.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Shawn/">Shawn Henry</a> on April 30, 2008 5:35 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions & Editorial</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/publications/">Publications</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/04/wcag20_cr_april2008.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/04/wcag20_cr_april2008.html#comments">Comments (3)</a>
| <a href="http://www.w3.org/QA/2008/04/wcag20_cr_april2008.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/04/alt-authoring-practices.html">alt attributes authoring practices</a></h3>
<p><p>There has been a lot of discussions around <code>alt</code> attributes on HTML WG mailing list. It's always difficult to move forward in such discussions because it seems to be easy when in fact it is rather complicated.</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/04/alt-authoring-practices.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/karl/">Karl Dubost</a> on April 30, 2008 2:47 AM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/tools/">Tools</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/04/alt-authoring-practices.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/04/alt-authoring-practices.html#comments">Comments (3)</a>
| <a href="http://www.w3.org/QA/2008/04/alt-authoring-practices.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/04/proposed_activity_for_video_on.html">Proposed Activity for Video on the Web</a></h3>
<p><p>W3C organized a workshop on Video on the Web in December 2007 in order<br />
to share current experiences and examine the technologies (see <a href='http://www.w3.org/2007/08/video/report.html'>report</a>) and is now following up with a proposal for a Video on the Web activity.</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/04/proposed_activity_for_video_on.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/LeHegaret/">Philippe Le Hégaret</a> on April 15, 2008 3:29 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/http/">HTTP</a>, <a href="http://www.w3.org/QA/archive/technology/semantic_web/">Semantic Web</a>, <a href="http://www.w3.org/QA/archive/technology/">Technology</a>, <a href="http://www.w3.org/QA/archive/technology/video/">Video</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/">W3C・QA News</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/04/proposed_activity_for_video_on.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/04/proposed_activity_for_video_on.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2008/04/proposed_activity_for_video_on.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/02/new_resources_on_making_ajax_a.html">New resources on making Ajax and related technologies accessible</a></h3>
<p><p>Today WAI published documents that help Web content developers know how to use WAI-ARIA to develop accessible rich Web applications, including WAI-ARIA Primer and WAI-ARIA Best Practices. We also posted a WAI-ARIA FAQ that answers questions such as "As a Web developer, what should I do with WAI-ARIA now?"</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/02/new_resources_on_making_ajax_a.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Shawn/">Shawn Henry</a> on February 4, 2008 3:05 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/02/new_resources_on_making_ajax_a.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/02/new_resources_on_making_ajax_a.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2008/02/new_resources_on_making_ajax_a.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2007/12/is_wcag_20_almost_done.html">Is WCAG 2.0 almost done?!</a></h3>
<p><p>A Last Call Working Draft of WCAG 2.0 was just published. This means that the WCAG Working Group has integrated all resolutions from previous comments. Yeah! Now the question is whether this draft of WCAG 2.0 is ready for the community to support moving it on towards becoming a Web standard (W3C Recommendation)...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2007/12/is_wcag_20_almost_done.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Shawn/">Shawn Henry</a> on December 12, 2007 2:52 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions & Editorial</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/publications/">Publications</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2007/12/is_wcag_20_almost_done.html">Permalink</a>
| <a href="http://www.w3.org/QA/2007/12/is_wcag_20_almost_done.html#comments">Comments (4)</a>
| <a href="http://www.w3.org/QA/2007/12/is_wcag_20_almost_done.html#trackback">TrackBacks (0)</a>
</p>
<p id="gentime">This page was last generated on $Date: 2012/01/13 07:42:06 $</p>
</div><!-- End of "main" DIV. -->
<address>
This blog is written by W3C staff and working group participants,<br />
and maintained by <a href="/People/CMercier/">Coralie Mercier</a>.<br />
Authorized parties may <a href="/QA/new">log in</a> to create a new entry.<br/>
<span id="poweredby">Powered by Movable Type, magpierss and a lot of Web Technology</span>
</address>
<p class="copyright">
<a rel="Copyright" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 1994-2012
<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a>®
(<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>),
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>,
<a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
and <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-software">software licensing</a>
rules apply. Your interactions with this site are in accordance
with our <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Public">public</a> and
<a href="http://www.w3.org/Consortium/Legal/privacy-statement#Members">Member</a> privacy
statements.
</p>
</body>
</html>