- From: Loretta Guarino Reid <lorettaguarino@google.com>
- Date: Wed, 10 Aug 2011 19:33:53 -0700
- To: Jeanne Spellman <jeanne@w3.org>, Jutta Treviranus <jtreviranus@faculty.ocad.ca>
- Cc: WCAG WG <w3c-wai-gl@w3.org>
- Message-ID: <CAHu5OWbhwWoqJAgf1OmDFYtfmwhLFMGOoLcNU---t_c8v+TrOg@mail.gmail.com>
The WCAG Working Group has reviewed your responses, and we accept all of them except WCAGWG17. We have run into issues in the past with calling content accessible, since no content is completely accessible to all people. We strongly encourage you to find a different term. We can say that it is WCAG 2.0 conforming. or perhaps even "WCAG2.0 accessible". But we certainly do not say or imply that WCAG makes pages accessible as an absolute and in fact go to great pains to say that meeting ALL WCAG, even at AAA and even if you do all the advisory techniques, will not make pages accessible to all. We feel that the use of the term "accessible content" raises unrealistic expectations. 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 On Wed, Jul 27, 2011 at 9:26 AM, Jeanne Spellman <jeanne@w3.org> wrote: > WCAG Working Group: > > Thank you for your comments on the 8 July 2010 Last Call Working Draft of > Authoring Tool Accessibility Guidelines (ATAG) 2.0 ( > http://www.w3.org/TR/2010/WD-**ATAG20-20100708/<http://www.w3.org/TR/2010/WD-ATAG20-20100708/>). > The Authoring Tool Accessibility Guidelines Working Group has reviewed all > comments received on the draft. We would like to know whether we have > understood your comments correctly and whether you are satisfied with our > resolutions. > > Please review our resolutions for the following comments, and reply to us > by 26 August 2011 to say whether you accept them or to discuss additional > concerns you have with our response. If we do not hear from you by that > date, we will mark your comment as "no response" and close it. If you need > more time to consider your acknowledgement, please let us know. You can > respond by email to public-atag2-comments@w3.org. Note that this list is > publicly archived. > > Since many of the comments were related, we have kept all the comments on a > topic together in a spreadsheet format, so you can see your comments in the > context of the others. You can search for your specific comments by > searching for your code "WCAGWG". The spreadsheet of comments is located at > http://www.w3.org/WAI/AU/2011/**atag20-8Jul10LC-comments-** > updated14july2011.html<http://www.w3.org/WAI/AU/2011/atag20-8Jul10LC-comments-updated14july2011.html> > > The AUWG has published a new working draft of ATAG 2.0 and Implementing > ATAG 2.0, so you can see the results of your comments in the document. > http://www.w3.org/TR/2011/WD-**ATAG20-20110721/<http://www.w3.org/TR/2011/WD-ATAG20-20110721/> > > Note that if you still strongly disagree with our resolution on an issue, > you have the opportunity to file a formal objection (according to 3.3.2 of > the W3C Process, at > http://www.w3.org/2005/10/**Process-20051014/policies.** > html#WGArchiveMinorityViews<http://www.w3.org/2005/10/Process-20051014/policies.html#WGArchiveMinorityViews>) > to public-atag2-comments@w3.org. Formal objections will be reviewed during > the candidate recommendation transition meeting with the W3C Director, > unless we can come to agreement with you on a resolution in > advance of the meeting. > > 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 ATAG 2.0. > > Regards, > > > Jutta Treviranus, AUWG Chair > Jeanne Spellman, AUWG Staff Contact > >
Received on Thursday, 11 August 2011 02:34:18 UTC