- From: <akirkpat@adobe.com>
- Date: Thu, 16 Jan 2014 20:57:36 +0000
- To: Andrew Kirkpatrick <akirkpat@adobe.com>
- Cc: public-comments-wcag20@w3.org
Dear Andrew Kirkpatrick , The Web Content Accessibility Guidelines Working Group has reviewed the comments you sent [1] on the Last Call Working Draft [2] of the Techniques for WCAG 2.0 published on 5 Sep 2013. Thank you for having taken the time to review the document and to send us comments! The Working Group's response to your comment is included below. Please review it carefully and let us know by email at public-comments-wcag20@w3.org if you agree with it or not before 21 January 2014. In case of disagreement, you are requested to provide a specific solution for or a path to a consensus with the Working Group. If such a consensus cannot be achieved, you will be given the opportunity to raise a formal objection which will then be reviewed by the Director during the transition of this document to the next stage in the W3C Recommendation Track. Thanks, For the Web Content Accessibility Guidelines Working Group, Michael Cooper W3C Staff Contact 1. (reference not available) 2. http://www.w3.org/TR/2013/NOTE-WCAG20-TECHS-20130905/ ===== Your comment on H42: Using h1-h6 to identify headings: > In H42 the resources section > (http://www.w3.org/TR/2013/NOTE-WCAG20-TECHS-20130905/H42) contains a > link to a non-existant RNIB blog post on headings "Quick tips for > accessible headings". This resource should be removed or replaced. > Also, the 2004 Eric Meyer resource seems dated and it is worth > identifying better resources. Working Group Resolution (LC-2865): Thank you for the comment. We are removing both links and replacing them with the following: WebAIM: Semantic Structure (Using Headings for Content Structure) http://webaim.org/techniques/semanticstructure/#contentstructure Heading Tags http://accessibility.psu.edu/headingshtml ---- Your comment on F42: Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting e...: > On http://www.w3.org/TR/WCAG-TECHS/failures.html#F42 example 2 there is > code for an image that lacks the <img> element. Working Group Resolution (LC-2870): Thanks for the comment, we've corrected the typo on F42. ----
Received on Thursday, 16 January 2014 20:57:39 UTC