Please review ATAG2.0

I'm part of the W3C's Web Accessibility Initiative (WAI) Authoring Tools Accessibility Guidelines (ATAG) working group (phew, that's a mouthful) and during the week, we published a new working draft of the new guidlines (ATAG2.0) along with a new "Implementing ATAG 2.0" guide. The official call for comments sent to the WAI Interest Group (IG) went like so:

Dear WAI Interest Group Participants,

The Authoring Tool Accessibility Guidelines Working Group invites you to comment on the updated Authoring Tool Accessibility Guidelines (ATAG) 2.0 Working Draft published 29 October 2009 at:

The draft integrates revisions in response to the comments of the 21 May draft as well as a substantially revised document, Implementing ATAG 2.0 that replaces Techniques for ATAG 2.0. In this draft, the Working Group made the following substantial changes: * Revised how authoring tools should support authors in making choices that improve accessibility. * Revised the former Techniques document to better serve developers, and changed the title to: Implementing ATAG 2.0.

Specific changes and questions for feedback are listed in the Status section:

ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to Web Content Accessibility Guidelines (WCAG) 2.0. It also defines how to make authoring tools accessible so that people with disabilities can use the tools. ATAG is introduced in the ATAG Overview at: ATAG is part of a series of accessibility guidelines/standards developed by WAI, which are listed in WAI Guidelines and Techniques at:

WAI encourages you to review the update ATAG 2.0 documents and submit comments on any issues that you think could present a barrier to future adoption and implementation of ATAG 2.0. Please send comments to the publicly-archived list: by 30 November 2009

For more information, see: * How WAI Develops Accessibility Guidelines through the W3C Process * Authoring Tool Accessibility Guidelines Working Group (AUWG)

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 and Judy Brewer, W3C WAI On behalf of: Jutta Treviranus, Chair of AUWG, and Director of the Assistive Technology Research Center, University of Toronto Jeanne Spellman, W3C Staff Contact for AUWG

If you're at all interested in accessibility (or even if you're not) and you build any kind of tool or application that can be used to create content, you really need to be having a read of these and making comments if there's anything you have an issue with. These guidelines are an important part of the process of ensuring that web content, applications and software are accessible, and present an incredible opportunity to really lead the field in best practice, especially for CMS vendors.