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

Re: Accessible content management system

From: Charles McCathieNevile <chaals@opera.com>
Date: Sat, 06 Aug 2011 19:16:47 +0930
To: w3c-wai-ig@w3.org, "Shawn Henry" <shawn@w3.org>
Message-ID: <op.vzsdf9pwwxe0ny@pa114-74-254-156.pa.vic.optusnet.com.au>
On Fri, 05 Aug 2011 00:10:56 +0930, Shawn Henry <shawn@w3.org> wrote:

>   Hi WAI IG folks,
>
> I want to take the opportunity of this thread to remind you about ATAG -  
> Authoring Tool Accessibility Guidelines. ATAG covers content management  
> systems (CMS).
...
> ATAG 1.0 has been around for 10+ years. ATAG 2.0 is available as a  
> complete Working Draft -- while some points might change, it's pretty  
> settled and usable now. ATAG is introduced in:
> http://www.w3.org/WAI/intro/atag.php
>
> Actions you can take:

One of the most useful things you can do is to review the tools you use  
for conformance to ATAG 2.0

Note that this is a bunch of work, and the sort of thing that a framework  
for doing collaboratively would help (both in spreading understanding of  
ATAG and in raising vendor awareness by seeing themselves being rated).  
But it is extremely valuable to have unbiased openly available reviews,  
rather than endless discussions like this one which are generally fairly  
impressionistic rather than based on careful analyses that no individual  
had the time to do completely.

IMHO

cheers

> - Review ATAG 2.0 Working Draft to help ensure that it is comprehensive
> - Tell authoring tool developers that you want them to meet ATAG
> - Ask authoring tool vendors how their tool conforms to ATAG
> - Include ATAG compliance in deciding which tools to use, in  
> procurement, in RFPs/RFTs (requests for proposals/tender), etc.
>
> More info is in the e-mail below.
>
> Regards,
> ~Shawn
>
>
> -------- Original Message --------
> Subject: 	Call for Review: ATAG 2.0 Updated Working Drafts
> Resent-Date: 	Fri, 22 Jul 2011 18:07:49 +0000
> Resent-From: 	w3c-wai-ig@w3.org
> Date: 	Fri, 22 Jul 2011 13:07:30 -0500
> From: 	Shawn Henry <shawn@w3.org>
> To: 	WAI Interest Group <w3c-wai-ig@w3.org>
>
>
>
> Dear WAI Interest Group Participants,
>
> W3C WAI invites you to review the updated Working Drafts of Authoring  
> Tool Accessibility Guidelines (ATAG) 2.0 and Implementing ATAG 2.0  
> published 21 July 2011 at:
> 	http://www.w3.org/TR/ATAG20/
> 	http://www.w3.org/TR/IMPLEMENTING-ATAG20/
>
> ATAG is particularly relevant to you if you use tools to create web  
> content -- tools such as, blogs, wikis, social networking websites,  
> content management systems (CMS), HTML editors, or other such tools[1].  
> ATAG defines how these tools should help you make your blog posts,  
> websites, etc. accessible -- and how the tools themselves should be  
> accessible so that people with disabilities can use them.
>
> To tool developers:
> We invite authoring tool developers to prepare to implement ATAG 2.0,  
> with the caution that the guidelines might change. In the coming months,  
> we'll be asking for tools that meet ATAG 2.0. Will your tool be an  
> example? If you are considering implementing ATAG 2.0 soon, please  
> e-mail Jeanne@w3.org
>
> Recent updates:
> For a list of significant changes since the last drafts and specific  
> questions for feedback, see the Status sections:
> 	http://www.w3.org/TR/ATAG20/#status
> 	http://www.w3.org/TR/IMPLEMENTING-ATAG20/#status
>
> Comments:
> Please submit comments on how ATAG 2.0 can be improved to better meet  
> the needs of people with disabilities to the publicly-archived list:
> 	public-atag2-comments@w3.org
> 	by *15 September 2011*
>
> 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/
>
> Note about Working Draft status:
> ATAG 2.0 was published as a Last Call Working Draft on 8 July 2010. The  
> Authoring Tool Accessibility Guidelines Working Group (AUWG) decided to  
> return to Working Draft stage to refine the document based on the  
> comments received. The Working Group expects to publish another Last  
> Call Working Draft later this year. Last Call and other development  
> stages are described in: How WAI Develops Accessibility Guidelines  
> through the W3C Process at:
> 	http://www.w3.org/WAI/intro/w3c-process
>
> 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.
> Short URI to this archived e-mail: http://bit.ly/atag2011july
>
> [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/
>
>
>
>


-- 
Charles 'chaals' McCathieNevile  Opera Software, Standards Group
     je parle franšais -- hablo espa˝ol -- jeg lŠrer norsk
http://my.opera.com/chaals       Try Opera: http://www.opera.com
Received on Saturday, 6 August 2011 09:47:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 6 August 2011 09:47:24 GMT