Re: Add "Techniques for Specific Technologies" ( LC-2895)

Dear WCAG WG,

Thank you for considering EOWG's comment.

We do not accept the modified wording because it does not cover the important points of the message -- including that content can meet WCAG success criteria but still not be accessible because the technology is not accessibility-supported for many users.

We were unable to propose an alternative rewording because we did not know your issues with our proposed wording. We tried suggesting changes to your modified wording, such as including "conformance requirements" but it became jargony and too complex.

After the EOWG telecon, I found your minutes saying, "Worry about the phrase "makes accessible to all people", since WCAG itself doesn't claim to meet that goal." Perhaps this modified wording will satisfy EOWG's messaging goals and your issues:
"Publication of techniques for a specific technology does not imply that the technology can be used in all situations 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 potential users."

EOWG is happy to continue working on wording that is acceptable to the WCAG WG.

Regards,
~Shawn for EOWG


On 2/18/2014 8:58 PM, 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
> 02/25/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.
> We agree that this text is useful, but that it should be added in this
> section instead:
> http://www.w3.org/WAI/GL/2014/WD-UNDERSTANDING-WCAG20-20140107/complete-diff.html#ut-understanding-techniques-general-tech-specific-head
>
> Also, the sentence should be modified to:
> 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.
>
> ----
>
>
>
>

Received on Friday, 21 February 2014 20:07:14 UTC