W3C logoWeb Accessibility Initiative (WAI) logo

WAI: Strategies, guidelines, and resources to make the Web accessible to people with disabilities

[DRAFT] Promoting ATAG Analysis/Requirements
updated $Date: 2011/10/07 12:12:45 $


Page Contents

Objectives, Goals, Purpose

Ultimate goal: All authoring tools meet ATAG.

A goal for this promotional activity is that all target audiences:


Audiences and Desired Outcomes

  1. Tool vendors
    1. Authoring tool managers see to it that their tools meet ATAG and "vendors" promote that their tool meets ATAG.
    2. Authoring tool developers make their tools meet ATAG.
  2. Tool purchasers & users
    1. People who use the authoring tools (content editors, authors, designers, developers, etc.) encourage authoring tool vendors to meet ATAG.
    2. Procurers and procurement influencers (including IT and in some cases maybe HR) include conformance to ATAG in their selection criteria and in any requests for proposals/tenders.
  3. Policy makers
    1. Policy makers include ATAG in any accessibility-related or other appropriate policies.

Indirect audiences:


Materials and Activities

Core Materials

Outbound Materials

Responsive Materials

Be prepared for interviews, speaking, article writing, etc.

Promotional Activities

? What activities we might want to use to promote ATAG, e.g., encouraging influential bloggers to promote ATAG, speakers & trianers to include ATAG is presentations & trainers...

@@ target a few key tools providers ("web-writability makers")

@@ open source

@@ develop and promote ATAG comformance reports (& public comments)

Messages for Announcements

2.0 Last Call Working Draft:

2.0 "CR" Candidate Recommendation:

2.0 Done! Completed Standard "Recommendation":


Need compelling metaphor &/or diagram &/or image (e.g., components) - that would also show the two aspects (tools itself accessible, produce accessible content).

? Main point: when tools meet ATAG, developers job easier.
? Main point: everyone may write to the Web.

@@h: are there axillary/fringe benefits to ATAG e.g., buisiness case?

?an idea: Everyone who knows WCAG, can also give rough idea of what ATAG is and why it's important.

[Messaging to:

Open Issues:


Drafts and discussions:

Related materials:




All may write.

@@ hook with backend and they'll figure out the other side.

@@market differentiater

26 April targeted e-mail

Subject: Update on Authoring Tool Accessibility Guidelines (ATAG) 2.0
Date: Tue, 26 Apr 2011 18:43:17 -0400
From: Jeanne Spellman <jeanne@w3.org>
To: jeanne@w3.org

I'm writing to invite your input into the Authoring Tool Accessibility Guidelines (ATAG) 2.0 Working Draft [http://www.w3.org/TR/ATAG20/] that we published today. The update of the ATAG guidelines to version 2.0 is nearing completion and we'd welcome your comments by May 24, 2011.

I am contacting you because we either have discussed ATAG 2.0 at a meeting or conference, or because your name was referred to me by a colleague who knew your interest.  If you are not the correct person in your organization to receive this information, please forward this email to them, and cc: me, so that I am only sending email to people who want to receive it.

ATAG 2. and its companion document, Implementing ATAG 2.0 [http://www.w3.org/TR/IMPLEMENTING-ATAG20/] define how authoring tools can help developers produce accessible web content that 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 them.

This is a good time to look over the documents and let us know if you see any significant issues with ATAG 2.0. Comments are welcome at public-atag2-comments@w3.org through 24 May 2011.

We are particularly looking for examples of authoring tools that demonstrate accessible authoring practices in their documentation, and for examples of templates that are labeled as accessible.  Please contact me ASAP if you think you can contribute in these areas.

Over the next year, I will be sending a few emails to keep you informed as ATAG 2.0 progresses to becoming a finalized W3C recommendation (standard) for accessible authoring tools. Please let me know if you don't want to be included in future contact.


Jeanne Spellman W3C Web Accessibility Initiative jeanne@w3.org