Your comments on WCAG 2.0 Public Working Draft of May, 2007

Dear Jeremy Andrews,

Thank you for your comments on the 17 May 2007 Public Working Draft of
the Web Content Accessibility Guidelines 2.0 (WCAG 2.0
http://www.w3.org/TR/2007/WD-WCAG20-20070517/). The WCAG Working Group
has reviewed all comments received on the May draft, and will be
publishing an updated Public Working Draft shortly. Before we do that,
we would like to know whether we have understood your comments
correctly, and also whether you are satisfied with our resolutions.

Please review our resolutions for the following comments, and reply to
us by 19 November 2007 at public-comments-wcag20@w3.org to say whether
you are satisfied. Note that this list is publicly archived. Note also
that we are not asking for new issues, nor for an updated review of
the entire document at this time.

Please see below for the text of comments that you submitted and our
resolutions to your comments. Each comment includes a link to the
archived copy of your original comment on
http://lists.w3.org/Archives/Public/public-comments-wcag20/, and may
also include links to the relevant changes in the WCAG 2.0 Editor's
Draft of May-October 2007 at
http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20071102/

Thank you for your time reviewing and sending comments. Though we
cannot always do exactly what each commenter requests, all of the
comments are valuable to the development of WCAG 2.0.

Regards,

Loretta Guarino Reid, WCAG WG Co-Chair
Gregg Vanderheiden, WCAG WG Co-Chair
Michael Cooper, WCAG WG Staff Contact

On behalf of the WCAG Working Group

----------------------------------------------------------
Comment 1: too vague
Source: http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Jun/0235.html
(Issue ID: 2068)
----------------------------
Original Comment:
----------------------------

I believe that in an attempt to improve accessibility to the web the
WCAG2.0 has simply managed to further muddy the water. The outline is
too vague in many areas and as a developer makes it nearly impossible
to know what is expected of my sites in relation to these guide lines.

Proposed Change:
Drop the use of WCAG2.0.

---------------------------------------------
Response from Working Group:
---------------------------------------------

To help with the issue you cite we have created the WCAG 2.0 Quick
Reference.  It provides a summary of all the success criteria along
with a listing of the techniques that are sufficient to meet them.
You can limit the list of techniques to just the technologies that you
use.  And there are links from the sufficient techniques to full
descriptions and examples.   Please look at the Quick Reference if you
are looking for concrete advice for meeting the guidelines.

Received on Sunday, 4 November 2007 04:46:18 UTC