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

Dear Jimmy Kromann,

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: teastability
Source: http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Jun/0231.html
(Issue ID: 2066)
----------------------------
Original Comment:
----------------------------

Hard to test accessbility? :D

Forget about the testing of accessbility through a program. It will
never happen.

Proposed Change:

I propose a "check box".

Then it will give the webdesigners possbility to "check" their way
into accessbility. Of course we will have to "trust" designers not to
"cheat". But i guess if the webdesigners want a "accessbility tag",
they wouldnt cheat.

i myself would have loved a interactiv checklist for when i started to
look into accessbility.

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

The current language allows for testing, some may be done by machine
and some may need human testing, and some need a combination of both.
We have also provided a Quick Reference which can be used in checklist
fashion.  Future tools may be built from the Quick Reference that
include checklist features, but this is not something the working
group can devote resources to until the guidelines and techniques are
more complete.

Received on Sunday, 4 November 2007 04:47:22 UTC