W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > July to September 2010

Re: Reminder: Call for Review: ATAG *Last Call* Working Draft

From: Yeliz Yesilada <yesilady@cs.man.ac.uk>
Date: Mon, 23 Aug 2010 15:48:58 +0300
Message-Id: <BF278026-DDAF-4AFE-BC1D-93295B3C621B@cs.man.ac.uk>
To: "EOWG (E-mail)" <w3c-wai-eo@w3.org>
I have some initial structural comments about <http://www.w3.org/TR/ 

1. In the Table of Contents (TOC), there are two items "abstract" and  
"status of this document", but these two items link to paragraphs  
above the TOC and others link to paragraphs  below the TOC. I think  
this is a bit confusing. I wonder if it will be better to take out  
"abstract" and "status of the document" from the TOC.
2. In the introduction, it says "The term "authoring tools" has a  
specific definition in ATAG 2.0", why not include the definition  
there? It's a short and important definition, but the user has to  
click on a link to reach to that short description.
3. To reach WCAG 2.0 from notes section, one needs to click on three  
different links. I wonder if this could be improved.

I haven't finished reading the document so probably I will have some  
more comments later.


On 18 Aug 2010, at 20:18, Shawn Henry wrote:

> ATAG comments are due in two weeks. Details below.
> Please prepare any comments that you want EOWG to discuss for this  
> week's teleconference.
> Thanks,
> ~Shawn
> -------- Original Message --------
> Subject: Call for Review: ATAG *Last Call* Working Draft
> Date: Thu, 08 Jul 2010 08:07:20 -0500
> From: Shawn Henry <shawn@w3.org>
> To: WAI Interest Group <w3c-wai-ig@w3.org>
> Dear WAI Interest Group Participants,
> The W3C WAI invites you to review and start using the Authoring  
> Tool Accessibility Guidelines (ATAG) 2.0 Last Call Working Draft  
> published 08 July 2010 at:
>    http://www.w3.org/TR/ATAG20/
> If you develop web authoring tools (content management systems,  
> HTML editors, blog software, websites that let users add content,  
> etc[1]), now is the time to take a good look at ATAG 2.0. We need  
> you to use this Last Call Working Draft in developing your tools  
> and let us know how it works for you. In the coming months, we'll  
> be asking for tools that meet ATAG 2.0. Will your tool be an example?
> People with disabilities and accessibility specialists are also  
> encouraged to review the document now to ensure that it addresses  
> accessibility needs.
> What is Last Call?: Last Call Working Draft and the other  
> development stages are described in:
>    How WAI Develops Accessibility Guidelines through the W3C Process
>    http://www.w3.org/WAI/intro/w3c-process
> Recent updates: For a list of changes since the last draft, see the  
> Status section: http://www.w3.org/TR/ATAG20/#status
> Comments: Please submit comments on any issues that you think could  
> present a barrier to future adoption and implementation of ATAG 2.0  
> to the publicly-archived list:
>    public-atag2-comments@w3.org
>    by *2 September 2010*
> 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/
> 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.
> [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 Monday, 23 August 2010 12:48:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:29:44 UTC