Commenting on WCAG via GitHub

As Shawn noted we are currently in a review period for updates to the two supporting documents for WCAG 2.0 - Understanding WCAG 2.0 and Techniques for WCAG 2.0.  

With this update we have also transferred the XML sources to a GitHub repository and have added information to the web page with instructions on how to comment on WCAG 2.0 (http://www.w3.org/WAI/WCAG20/comments/).  The traditional method of using the online form is still active, and in some cases may be the more appropriate way to leave a general comment.  Using GitHub is ideal for comments where a specific change to the documents is part of the comment. 

We are very interested in comments and questions regarding the use of GitHub for WCAG 2.0 document commenting, but will not be able to provide general support around the use of GitHub.

Please take a look and send in comments on the current drafts by February 14!

Thanks,
Andrew Kirkpatrick
Joshue O'Connor
WCAG Working Group co-Chairs

-----Original Message-----
From: Shawn Henry [mailto:shawn@w3.org] 
Sent: Thursday, January 16, 2014 3:17 PM
To: WAI Interest Group
Cc: Andrew Kirkpatrick; Joshue O Connor; Michael Cooper
Subject: Call for Review: WCAG 2.0 Techniques Draft Updates

Dear WAI Interest Group Participants,

The W3C WAI announces a Call for Review of updates to two supporting documents for Web Content Accessibility Guideline (WCAG) 2.0. *This is not an update to WCAG 2.0, which is a stable document*.

The supporting documents (W3C Working Group Notes) are updated periodically to reflect current practices and technologies. Previously they were updated about once a year. The WCAG Working Group plans to update them more frequently.

The existing Techniques and Understanding documents remain in place as W3C Notes while these separate draft updates are under review and the WCAG Working Group addresses comments.

The following draft updates are available for review as Editors' Drafts:
- Techniques for WCAG 2.0 Editors' Draft http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/

- Understanding WCAG 2.0 Editors' Draft
http://www.w3.org/WAI/GL/2014/WD-UNDERSTANDING-WCAG20-20140107/


The changes are highlighted in diff-marked versions at:
- http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/complete-diff.html

- http://www.w3.org/WAI/GL/2014/WD-UNDERSTANDING-WCAG20-20140107/complete-diff.html


Changes that apply to "How to Meet WCAG 2.0: A customizable quick reference..." are available in a draft at: <http://www.w3.org/WAI/WCAG20/quickref/20140107/>

Updates for review:
Most of the updates in this draft are new WAI-ARIA Techniques. The WCAG Working Group is still discussing appropriate ways to provide text alternatives for images -- specifically, is it OK to not provide an alt attribute and instead use ARIA attributes? We particularly request feedback on this issue and related techniques such as F65[1]. See the examples and details at:
- ARIA10: Using aria-labelledby to provide a text alternative for non-text content <http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/ARIA10>

Please send any comments on these Editors' Drafts by *14 February 2014*. Comments and contributions for additional WCAG 2.0 techniques can be sent via web form or e-mail, per:
- Instructions for Commenting on WCAG 2.0 Documents http://www.w3.org/WAI/WCAG20/comments/


*Important notes about techniques*:
- The basis for determining conformance to WCAG 2.0 is the success criteria from the WCAG 2.0 standard -- not the techniques. W3C’s techniques are informative and are not intended to be required. Learn more from "Understanding Techniques for WCAG Success Criteria" at <http://www.w3.org/TR/UNDERSTANDING-WCAG20/understanding-techniques.html>
- 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 their potential users.

If you are interested in actively contributing to the development of additional WCAG 2.0 techniques and support material through the WCAG Working Group, please see:
- Participating in WAI< http://www.w3.org/WAI/participation> and contact Michael Cooper

For an introduction to the WCAG documents, see:
- WCAG Overview
http://www.w3.org/WAI/intro/wcag.php


Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.

Regards,
Shawn Henry, W3C, WAI Outreach
Andrew Kirkpatrick, Adobe Systems Inc., WCAG WG Co-Chair Joshue O Connor, WCAG WG Co-Chair Michael Cooper, W3C, WCAG WG Staff Contact

---
[1] F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type "image" <http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/F65>




-----
Shawn Lawton Henry
W3C Web Accessibility Initiative (WAI)
Massachusetts Institute of Technology (MIT)
e-mail: shawn@w3.org
phone: +1.617.395.7664
about: http://www.w3.org/People/Shawn/

Received on Monday, 20 January 2014 15:58:38 UTC