- From: <akirkpat@adobe.com>
- Date: Sun, 03 Aug 2014 23:38:50 +0000
- To: Webcc@jessica.w3.org
- Cc: public-comments-wcag20@w3.org
Dear Webcc, 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 16 Jan 2014. 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 10 August 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/WAI/GL/2014/WD-WCAG20-TECHS-20140107/ ===== Your comment on F17: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient info...: > In the file: > > https://github.com/w3c/wcag/blob/master/wcag20/sources/failure-tech-src.xml > > i.e.: > > http://www.w3.org/TR/WCAG-TECHS/F17.html > > "For client-side image maps, check that the value of the usemap > attribute has a corresponding id value if the usemap attribute is not a > URI." > > According to the HTML 4.0.1 specification the usemap attribute must be > an URI and must match the value of the name attribute of another map > element. Working Group Resolution (LC-2904): Thanks for your comment. We have updated the test procedure to reflect the HTML spec correctly: For client-side image maps, check that the value of the usemap attribute is a URI that references a valid name or id. ----
Received on Sunday, 3 August 2014 23:38:51 UTC