<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 14 (filtered medium)"><style><!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal" style="margin-bottom:12.0pt">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 published.<br>
ATAG 2.0: <a href="http://www.w3.org/TR/ATAG20/">http://www.w3.org/TR/ATAG20/</a><br> Implementing ATAG 2.0: <a href="http://www.w3.org/TR/IMPLEMENTING-ATAG20/">http://www.w3.org/TR/IMPLEMENTING-ATAG20/</a><br><br>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.<br>
ATAG Overview: <a href="http://www.w3.org/WAI/intro/atag">http://www.w3.org/WAI/intro/atag</a><br> ATAG at a Glance: <a href="http://www.w3.org/WAI/intro/atag-glance">http://www.w3.org/WAI/intro/atag-glance</a><br><br>
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 <<a href="http://www.w3.org/WAI/intro/w3c-process">http://www.w3.org/WAI/intro/w3c-process</a>>. 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 <<a href="http://www.w3.org/TR/2013/CR-ATAG20-20131107/#status">http://www.w3.org/TR/2013/CR-ATAG20-20131107/#status</a>><br>
<br>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.<br>
<br>*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 <<a href="mailto:public-atag2-comments@w3.org">public-atag2-comments@w3.org</a>> or Jeanne Spellman <<a href="mailto:jeanne@w3.org">jeanne@w3.org</a>>.<br>
<br>*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 <<a href="mailto:jeanne@w3.org">jeanne@w3.org</a>>.<br>
<br>While the focus of this CR stage is to collect implementations, comments are still welcome at: <<a href="mailto:public-atag2-comments@w3.org">public-atag2-comments@w3.org</a>><br><br>About the URIs:<br>The first links above go to the latest version of the documents. The "dated" versions are:<br>
* <a href="http://www.w3.org/TR/2013/CR-ATAG20-20131107/">http://www.w3.org/TR/2013/CR-ATAG20-20131107/</a><br>* <a href="http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/">http://www.w3.org/TR/2013/WD-IMPLEMENTING-ATAG20-20131107/</a><br>
The difference between these links are explained in Referencing and Linking to WAI Guidelines and Technical Documents at: <<a href="http://www.w3.org/WAI/intro/linking.html">http://www.w3.org/WAI/intro/linking.html</a>><br>
<br>Feel free to circulate this message to other lists; please avoid cross-postings where possible.<br>Please let us know if you have any questions. Thank you in advance for your help implementing ATAG 2.0.<br><br>Regards,<br>
~Shawn Henry, WAI Outreach<br>Jutta Treviranus, AUWG Chair<br>Jeanne Spellman, AUWG W3C Staff Contact<br><br><br><br><br>-----<br>Shawn Lawton Henry<br>W3C Web Accessibility Initiative (WAI)<br>e-mail: <a href="mailto:shawn@w3.org">shawn@w3.org</a><br>
phone: +1.617.395.7664<br>about: <a href="http://www.w3.org/People/Shawn/">http://www.w3.org/People/Shawn/</a></p></div></body></html>