Fw: WCAG 2.0 CR - W3C blog post and press release

The below was sent to the WAI Interest Group list today:


WCAG 2.0 includes advice for how authors should author their content. That 
includes HTML, so it seems relevant for this Group to review it.

For example, it mentions "standard HTML controls" are natively accessible:

4.1.2 Name, Role, Value: For all user user interface components (including 
but not limited to: form elements, links and components generated by 
scripts), the name and role can be programmatically determined; states, 
properties, and values that can be set by the user can be programmatically 
set; and notification of changes to these items is available to user agents, 
including assistive technologies. (Level A) How to Meet 4.1.2 Understanding 

Note: 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 

-- <http://www.w3.org/TR/2008/CR-WCAG20-20080430/#ensure-compat-rsv>

I haven't read the whole thing but this part seems eminently sensible, to 

Ben 'Cerbera' Millard
Collections of Interesting Data Tables

----- Original Message ----- 
From: "Shawn Henry" <shawn@w3.org>
To: "WAI Interest Group" <w3c-wai-ig@w3.org>
Sent: Wednesday, April 30, 2008 7:10 PM
Subject: WCAG 2.0 CR - W3C blog post and press release

Hi WAI Interest Group folks,

Additional perspectives on the WCAG 2.0 Candidate Recommendation (CR) are 
available in:
* "WCAG 2.0 takes a giant leap forward — Now it's your turn" blog post at
* "W3C Invites Developers to Implement WCAG 2.0: WAI's Web Content 
Accessibility Guidelines 2.0 Advances to Candidate Recommendation" press 
release at


-------- Original Message --------
Subject: WCAG 2.0 Candidate Recommendation Ready to Test Drive
Date: Wed, 30 Apr 2008 10:49:28 -0500
From: Shawn Henry <shawn@w3.org>
To: WAI Interest Group <w3c-wai-ig@w3.org>

Dear WAI Interest Group Participants,

The Web Content Accessibility Guidelines (WCAG) Working Group is excited to 
announce the publication of WCAG 2.0 as a W3C Candidate Recommendation on 30 
April. WCAG 2.0 explains how to make Web sites, applications, and other 
content accessible to people with disabilities, and many elderly users.

Candidate Recommendation (CR) is a major step in the W3C standards 
development process; it signals that there is broad consensus in the Working 
Group and among public reviewers on the technical content of WCAG 2.0. The 
W3C Process stages are described in:
How WAI Develops Accessibility Guidelines through the W3C Process

The primary purpose of this CR stage is for developers and designers to 
"test drive" WCAG 2.0 to demonstrate that WCAG 2.0 can be implemented in Web 
sites. WAI encourages a broad range of Web sites and Web applications to use 
WCAG 2.0 at this stage, and share implementation experience. For information 
on submitting your implementations, see:
WCAG 2.0 Candidate Recommendation Implementation Information
If you plan to provide implementations, please let us know your intentions 
by *23 May 2008*.
Actual implementations are due by *30 June 2008*.

It is important to note that some WCAG 2.0 requirements are at risk; that 
is, they may not be included if there are not sufficient implementations. 
Items at risk are listed under “Items at Risk” in:

While the focus of this stage is to collect implementations, the comment 
form and email address are still available from:
Instructions for Commenting on WCAG 2.0 Documents

The different WCAG 2.0 documents that the WCAG Working Group updated with 
this publication are introduced in:
Overview of Web Content Accessibility Guidelines (WCAG) 2.0 Documents

A key tool for using WCAG 2.0 documents, which was previously called the 
"Quick Reference", is:
How to Meet WCAG 2.0: A customizable quick reference to WCAG 2.0 

For more information about the Candidate Recommendation status of WCAG 2.0 
and the changes since the last publication, see:
"Status of this Document" section of WCAG 2.0

WCAG 2.0 is part of a series of accessibility guidelines/standards developed 
by WAI, which are listed in:
WAI Guidelines and Techniques

Feel free to circulate this message to other lists; please avoid 
cross-postings where possible.

Please let us know if you have any questions. Thank you in advance for your 
help implementing WCAG 2.0.

~Shawn Lawton Henry and Judy Brewer
On behalf of:
Loretta Guarino Reid, Co-chair of WCAG WG, and Computer Scientist, Google 
Gregg Vanderheiden, Co-chair of WCAG WG, and Director of Trace R&D Center, 
University of Wisconsin-Madison
Michael Cooper, W3C Team Contact for WCAG WG

Shawn Lawton Henry, W3C Web Accessibility Initiative (WAI)
about: http://www.w3.org/People/Shawn/
phone: +1-617-395-7664
e-mail: shawn@w3.org

No virus found in this incoming message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.23.6/1407 - Release Date: 30/04/2008 

Received on Wednesday, 30 April 2008 19:53:29 UTC