- From: Denis Boudreau <info@denisboudreau.org>
- Date: Wed, 4 Jun 2014 12:08:27 -0400
- To: akirkpat@adobe.com
- Cc: EOWG <w3c-wai-eo@w3.org>, public-comments-wcag20@w3.org
Dear WCAG-WG, While my comment only involves me as I do not speak on behalf of the EOWG, I agree with the resolution. Thank you for hearing us. /Denis On Jun 4, 2014, at 9:12 AM, akirkpat@adobe.com wrote: > Dear EOWG , > > The Web Content Accessibility Guidelines Working Group has reviewed the > comments you sent [1] on the Last Call Working Draft [2] of the > Understanding 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 June 10 > 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. http://www.w3.org/mid/E1WET31-0008QV-7A@stuart.w3.org > 2. http://www.w3.org/WAI/GL/2014/WD-UNDERSTANDING-WCAG20-20140107/ > > > ===== > > Your comment on the document as a whole: >> Summary of Issue: Add "Techniques for Specific Technologies" >> Comment (Including rationale for any proposed change): >> In WAI announcements and blogs (e.g., >> http://www.w3.org/blog/2012/01/wcag-techniques-learn-more/) over the >> last couple of years, we've been clarifying saying this (the proposed >> change), and it really belongs in the doc itself. >> >> Proposed Change: >> In Understanding Techniques for WCAG Success Criteria >> > <http://www.w3.org/WAI/GL/2014/WD-UNDERSTANDING-WCAG20-20140107/complete-diff.html#understanding-techniques> >> add a new section, right under the Techniques are Informative section >> > <http://www.w3.org/WAI/GL/2014/WD-UNDERSTANDING-WCAG20-20140107/complete-diff.html#ut-understanding-techniques-informative-head>: >> >> <h3>Techniques for Specific Technologies >> Publication of techniques for a specific technology does not imply that >> the technology can be used in all cases to create accessible content >> that meets WCAG 2.0. Developers need to be aware of the limitations of >> specific technologies and ensure that they provide content in a way that >> is accessible to all potential users. > > > Working Group Resolution (LC-2895): > Thank you for your comment. > > As a result of our joint EOWG and WCAG meeting, we agreed to replace the > text: > > "Publication of techniques for a specific technology does not imply that > all uses of that technology will meet WCAG 2.0. Developers need to be aware > of the limitations of specific technologies and provide content in ways > that meets WCAG 2.0 success criteria." (found at > http://www.w3.org/TR/UNDERSTANDING-WCAG20/understanding-techniques.html#ut-understanding-techniques-general-tech-specific-head) > > > with the text: > > Publication of techniques for a specific technology does not imply that the > technology can be used in all situations to create content that meets WCAG > 2.0 success criteria and conformance requirements. Developers need to be > aware of the limitations of specific technologies and provide content in a > way that is accessible to people with disabilities. > > > > > > ---- > > >
Received on Wednesday, 4 June 2014 16:08:57 UTC