W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2012

Reminder: ATAG 2.0 Last Call Working Draft published

From: Shawn Henry <shawn@w3.org>
Date: Tue, 22 May 2012 09:20:36 -0500
Message-ID: <4FBBA0B4.7020400@w3.org>
To: WAI Interest Group <w3c-wai-ig@w3.org>
  Reminder: The comment deadline is *Tuesday 5 June 2012*, which is in two weeks.

-------- Original Message --------
Subject: 	ATAG 2.0 Last Call Working Draft published
Date: 	Tue, 10 Apr 2012 09:52:34 -0500
From: 	Shawn Henry <shawn@w3.org>
To: 	WAI Interest Group <w3c-wai-ig@w3.org>



Dear WAI Interest Group Participants,

WAI has published an updated Last Call Working Draft of the Authoring Tool Accessibility Guidelines (ATAG) 2.0 at:
          http://www.w3.org/TR/ATAG20/
  and an updated Working Draft of Implementing ATAG 2.0 at:
          http://www.w3.org/TR/IMPLEMENTING-ATAG20/

Last Call:
This third ATAG 2.0 Last Call Working Draft is provided for public review now that all resolutions from previous comments are incorporated. The Authoring Tool Accessibility Guidelines Working Group (AUWG) hopes that it has resolved all substantive issues with this draft, and looks forward to progressing to the next stages in completing ATAG 2.0. Last Call and the other development stages are described in: How WAI Develops Accessibility Guidelines through the W3C Process at http://www.w3.org/WAI/intro/w3c-process

Test Drive Today:
WAI encourages developers of web authoring tools (content management systems, HTML editors, social networking, and more[1]), to try using the ATAG 2.0 Working Draft now. (While we think it is stable, it might change some based on public feedback and implementation experience.) We are looking forward to learning about your experience implementing ATAG 2.0 in your tools. In the coming months, we'll be asking for tools that meet ATAG 2.0. *Will your tool be an example?*

Recent Updates:
For a list of changes since the last draft, see the Status section at: http://www.w3.org/TR/ATAG20/#status

Comments:
If there are any issues that you think could present a barrier to future adoption and implementation of ATAG 2.0, please submit comments to the publicly-archived list: public-atag2-comments@w3.org by *5 June 2012*

Background:
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: http://www.w3.org/WAI/intro/atag.php
ATAG is part of a series of accessibility guidelines/standards developed by WAI, which are listed in WAI Guidelines and Techniques at: http://www.w3.org/WAI/guid-tech.html
ATAG is developed by the Authoring Tool Accessibility Guidelines Working Group (AUWG), http://www.w3.org/WAI/AU/

URI:
The first URIs above go to the latest version of the documents. The "dated" version of these drafts are: http://www.w3.org/TR/2012/WD-ATAG20-20120410/ and http://www.w3.org/TR/2012/WD-IMPLEMENTING-ATAG20-20120410/
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

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 comments.

[1] Examples of authoring tools: http://www.w3.org/WAI/intro/atag.php#for

Regards,
~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@w3.org
phone: +1.617.395.7664
about: http://www.w3.org/People/Shawn/
Received on Tuesday, 22 May 2012 14:21:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 14:21:08 GMT