[Athen] FW: Invitation for ATAG 2.0 Implementation Testing

Sam Joehl sam.joehl at ssbbartgroup.com
Fri Nov 8 07:53:36 PST 2013

W3C WAI is pleased to announce the publication of Authoring Tool
Accessibility Guidelines (ATAG) 2.0 as a W3C Candidate Recommendation. An
updated Working Draft of the supporting Note Implementing ATAG 2.0 is also
ATAG 2.0: http://www.w3.org/TR/ATAG20/
Implementing ATAG 2.0: http://www.w3.org/TR/IMPLEMENTING-ATAG20/

ATAG defines how authoring tools should help developers produce accessible
web content that conforms to Web Content Accessibility Guidelines (WCAG)
2.0. ATAG also defines how to make authoring tools accessible so that
people with disabilities can use them. Authoring tools include content
management systems (CMS), learning management systems (LMS), HTML editors,
blogs, wikis, social media, and development environments.
ATAG Overview: http://www.w3.org/WAI/intro/atag
ATAG at a Glance: http://www.w3.org/WAI/intro/atag-glance

Candidate Recommendation (CR) is a major step in the W3C standards
development process; it signals that there is broad consensus in the
Working Group and among public reviewers on the technical content of ATAG
2.0. The W3C Process stages are described in: How WAI Develops
Accessibility Guidelines through the W3C Process at <
http://www.w3.org/WAI/intro/w3c-process>. For more information about the CR
status of ATAG 2.0, including the "exit criteria" for completing CR and the
features at risk, see: "Status of this Document" section of ATAG 2.0 at <

The purpose of the Candidate Recommendation stage is to ensure that ATAG
2.0 can be implemented in the real world and to document that different
types of authoring tools meet ATAG success criteria. *WAI encourages a
broad range of authoring tools to use ATAG 2.0 at this stage*, and share
implementation experience. During this CR stage, we are developing an
implementation report listing tools that meet each ATAG success criteria.

*Would you like your tool listed in the ATAG 2.0 CR implementation report*?
If you might be interested in sharing how your tool implements ATAG, please
let us know by *7 December 2013* via e-mail to <public-atag2-comments at w3.org>
or Jeanne Spellman <jeanne at w3.org>.

*A unique opportunity to get experience working with ATAG*: We are looking
for accessibility specialists and specialists in specific authoring tools
to help the ATAG Working Group with testing. If you might be interested in
testing ATAG, please contact Jeanne Spellman <jeanne at w3.org>.

While the focus of this CR stage is to collect implementations, comments
are still welcome at: <public-atag2-comments at w3.org>

About the URIs:
The first links above go to the latest version of the documents. The
"dated" versions are:
* http://www.w3.org/TR/2013/CR-ATAG20-20131107/
* http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/
The difference between these links are explained in Referencing and Linking
to WAI Guidelines and Technical Documents at: <

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

~Shawn Henry, WAI Outreach
Jutta Treviranus, AUWG Chair
Jeanne Spellman, AUWG W3C Staff Contact

Shawn Lawton Henry
W3C Web Accessibility Initiative (WAI)
e-mail: shawn at w3.org
phone: +1.617.395.7664
about: http://www.w3.org/People/Shawn/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20131108/87de2af0/attachment.html>

More information about the athen-list mailing list