Re: Fwd: Authoring Tool Accessibility Guidelines (ATAG) 2.0 is a W3C Recommendation
Joshue O Connor <[email protected]> Thu, 24 Sep 2015 16:18:44 +0100
| Newsgroups | gmane.org.w3c.accessibility.tools |
|---|---|
| Message-ID | <[email protected]> |
------4CARX6UY23A37Q6E27CQI3AQJY3K7T Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Congrats! =F0=9F=98=81=F0=9F=98=84 Sent from TypeMail On 24 Sep 2015 16:06, at 16:06, Jeanne Spellman <[email protected]> wrote: >Congratulations everyone!! ATAG 2.0 is officially complete. :)) > > >-------- Forwarded Message -------- >Subject: Authoring Tool Accessibility Guidelines (ATAG) 2.0 is a W3C=20 >Recommendation >Date: Thu, 24 Sep 2015 11:03:54 -0400 >From: Jeanne Spellman <[email protected]> >To: WAI Interest Group <[email protected]> >CC: [email protected], Jutta Treviranus <[email protected]> > > > >Dear WAI Interest Group Participants, > >WAI is pleased to announce the publication of Authoring Tool >Accessibility Guidelines (ATAG) 2.0 as a W3C Recommendation at: >http://www.w3.org/TR/ATAG20/ > >ATAG 2.0 has a companion document, Implementing ATAG 2.0, published as >a >W3C Working Group Note: >http://www.w3.org/TR/IMPLEMENTING-ATAG20/ > >ATAG 2.0 helps improve web accessibility by providing guidelines for >designing web content authoring tools that are both more accessible to >authors with disabilities (Part A) and designed to enable, support, and >promote the production of more accessible web content by all authors >(Part B). ATAG 2.0 helps authors meet WCAG 2.0. Selecting authoring >tools that conform to ATAG 2.0 can facilitate the process of creating >accessible Web content, and can also remove barriers to content >creation >by people with disabilities. ATAG 2.0 is complete, ready for use and is >already being implemented by native and web-based authoring tools >including: social media tools, content management systems, learning >management systems, WYSIWYG editors, and HTML editors. Please see >additional information in: > >* How WAI Develops Accessibility Guidelines through the W3C Process ><http://www.w3.org/WAI/intro/w3c-process> >* ATAG Overview <http://www.w3.org/WAI/intro/atag.php>, >* ATAG at a Glance <http://www.w3.org/WAI/intro/atag-glance.php>, >* blog article on ATAG 2.0 Recommendation ><https://www.w3.org/blog/2015/09/more-accessible-web-authoring-with-atag= -2-0/> > >ATAG 2.0 was developed by the Authoring Tool Accessibility Guidelines >Working Group (ATAG WG). > >URI: >The first URI above goes to the latest version of the document. The >"dated" version of this draft is: ><http://www.w3.org/WAI/AU/2015/REC-ATAG20-20150924/> ><http://www.w3.org/WAI/AU/2015/REC-ATAG20-20150924/> The difference >between these URIs are explained in Referencing and Linking to WAI >Guidelines and Technical Documents at: ><http://www.w3.org/WAI/intro/linking.html> ><http://www.w3.org/WAI/intro/linking.html> > >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, > >Jutta Treviranus ATAG WG Chair >Jeanne Spellman ATAG WG W3C Staff Contact >Judy Brewer, WAI Director ------4CARX6UY23A37Q6E27CQI3AQJY3K7T Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head></head><body><p dir=3D"ltr">Congrats! 😁😄</p> <p dir=3D"ltr"><!-- tmjah_g_1299s -->Sent from <a href=3D"http://www.type= app.com/r">TypeMail<!-- tmjah_g_1299e --></a></p> <div class=3D"gmail_quote" >On 24 Sep 2015, at 16:06, Jeanne Spellman <= ;<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>>= wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8= ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <pre class=3D"blue">Congratulations everyone!! ATAG 2.0 is officially com= plete. :))<br><br><br>-------- Forwarded Message --------<br>Subject: A= uthoring Tool Accessibility Guidelines (ATAG) 2.0 is a W3C <br>Recommenda= tion<br>Date: Thu, 24 Sep 2015 11:03:54 -0400<br>From: Jeanne Spellman = <[email protected]><br>To: WAI Interest Group <[email protected]>= ;<br>CC: [email protected], Jutta Treviranus <[email protected]= a><br><br><br><br>Dear WAI Interest Group Participants,<br><br>WAI is = pleased to announce the publication of Authoring Tool<br>Accessibility Gu= idelines (ATAG) 2.0 as a W3C Recommendation at:<br><a href=3D"http://www.= w3.org/TR/ATAG20">http://www.w3.org/TR/ATAG20</a>/<br><br>ATAG 2.0 has a = companion document, Implementing ATAG 2.0, published as a<br>W3C Working = Group Note:<br><a href=3D"http://www.w3.org/TR/IMPLEMENTING-ATAG20">http:= //www.w3.org/TR/IMPLEMENTING-ATAG20</a>/<br><br>ATAG 2.0 helps improve we= b accessibility by providing guidelines for<br>designing web content authoring tools that are both more accessibl= e to<br>authors with disabilities (Part A) and designed to enable, suppor= t, and<br>promote the production of more accessible web content by all au= thors<br>(Part B). ATAG 2.0 helps authors meet WCAG 2.0. Selecting author= ing<br>tools that conform to ATAG 2.0 can facilitate the process of creat= ing<br>accessible Web content, and can also remove barriers to content cr= eation<br>by people with disabilities. ATAG 2.0 is complete, ready for us= e and is<br>already being implemented by native and web-based authoring t= ools<br>including: social media tools, content management systems, learni= ng<br>management systems, WYSIWYG editors, and HTML editors. Please see<b= r>additional information in:<br><br>* How WAI Develops Accessibility Guid= elines through the W3C Process<br><<a href=3D"http://www.w3.org/WAI/in= tro/w3c-process">http://www.w3.org/WAI/intro/w3c-process</a>><br>* ATA= G Overview <<a href=3D"http://www.w3.org/WAI/intro/atag.php">http://www.w3.org/WAI/intro= /atag.php</a>>,<br>* ATAG at a Glance <<a href=3D"http://www.w3.org= /WAI/intro/atag-glance.php">http://www.w3.org/WAI/intro/atag-glance.php</= a>>,<br>* blog article on ATAG 2.0 Recommendation<br><<a href=3D"ht= tps://www.w3.org/blog/2015/09/more-accessible-web-authoring-with-atag-2-0= ">https://www.w3.org/blog/2015/09/more-accessible-web-authoring-with-atag= -2-0</a>/><br><br>ATAG 2.0 was developed by the Authoring Tool Accessi= bility Guidelines<br>Working Group (ATAG WG).<br><br>URI:<br>The first UR= I above goes to the latest version of the document. The<br>"dated" versio= n of this draft is:<br><<a href=3D"http://www.w3.org/WAI/AU/2015/REC-A= TAG20-20150924">http://www.w3.org/WAI/AU/2015/REC-ATAG20-20150924</a>/>= ;<br><<a href=3D"http://www.w3.org/WAI/AU/2015/REC-ATAG20-20150924">ht= tp://www.w3.org/WAI/AU/2015/REC-ATAG20-20150924</a>/> The difference<b= r>between these URIs are explained in Referencing and Linking to WAI<br>Guidelines and Technical Documents at:<br><<a href=3D= "http://www.w3.org/WAI/intro/linking.html">http://www.w3.org/WAI/intro/li= nking.html</a>><br><<a href=3D"http://www.w3.org/WAI/intro/linking.= html">http://www.w3.org/WAI/intro/linking.html</a>><br><br>Please let = us know if you have any questions. Thank you in advance for<br>your comme= nts.<br>Feel free to circulate this message to other lists; please avoid<= br>cross-postings where possible.<br><br>Regards,<br><br>Jutta Treviranus= ATAG WG Chair<br>Jeanne Spellman ATAG WG W3C Staff Contact<br>Judy Brewe= r, WAI Director<br><br><br><br><br></pre></blockquote></div></body></html= > ------4CARX6UY23A37Q6E27CQI3AQJY3K7T--