[DRAFT] Promoting ATAG Analysis/Requirements
updated $Date: 2011/10/07 12:12:45 $
Ultimate goal: All authoring tools meet ATAG.
A goal for this promotional activity is that all target audiences:
- are aware of ATAG
- embrace ATAG
- advocate for ATAG
- Tool vendors
- Authoring tool managers see to it that their tools meet ATAG and "vendors" promote that their tool meets ATAG.
- Authoring tool developers make their tools meet ATAG.
- Tool purchasers & users
- People who use the authoring tools (content editors, authors, designers, developers, etc.) encourage authoring tool vendors to meet ATAG.
- 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.
- Policy makers
- Policy makers include ATAG in any accessibility-related or other appropriate policies.
- Trainers and speakers use WAI material to help them encourage above.
- People with disabilities and accessibility advocates (individuals and organizations) use WAI material to help them encourage above.
- @@Including tools developed to sell, as well as internal CMSs, which are often built upon existing frameworks. (which, fyi, is a requirement in many orgs because of employment anti-discrimination regulations)
- @@Frameworks could encourage accessibility, e.g., in their development guidelines.
- Authoring Tool Accessibility Guidelines (ATAG) Overview - update. ?provide in PDF version designed for printing?
- ? ATAG 2 at a Glance (e.g., see WCAG 2 at a Glance)
- ? ATAG 2 FAQ - ?one? ?separate ones for different audiences? (see WAI-ARIA FAQ & WCAG 2 FAQ)
- ? Presentation material (slides)
- [Selecting and Using Authoring Tools for Web Accessibility - ?update]
- Usual announcements: W3C news, WAI home page highlight, WAI RSS feed, tweets, WAI IG e-mails, targeted e-mails, blog posts
- Handout - maybe just something simple but permanent with acronym, short description, image/metaphor/diagram, and landing URI - maybe a "postcard". (something that doesn't get outdated easily)
- Press release - ?for CR? ?different ones for different audiences?
- ? blurbs for bloggers, newsletters
Be prepared for interviews, speaking, article writing, etc.
? 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)
2.0 Last Call Working Draft:
- WG thinks it's done. Now is the time to review it!
- To managers and developers: Benefits of implementing now. Contact Jeanne if you want to be part of candidate recommendation implementation.
- ??? Procurers & policy makers: You can include "ATAG" without a version number, which can cover 1.0 now and 2.0 when it's done.
2.0 "CR" Candidate Recommendation:
- To managers and developers: Benefits of implementing now. Contact Jeanne asap if you want to be part of candidate recommendation implementation.
2.0 Done! Completed Standard "Recommendation":
- Procurers & policy makers: It's ready for you to include now.
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.
- ? Establish ATAG as an enabler
- ? Focus on best practices
- ? Outline ATAG's key features
- ? Clearly articulate the benefits of building accessibility into the core platform
- ? Tone: authoritative, credible, positive, enthusiastic, gentle, welcoming.
- ? Make emotional connection, create desire and impetus for them to engage. (Not technical sell.)
- ? "We want to [help] encourage you implement ATAG" and not "This is what you have to do to implement the ATAG"
- Timelines for ATAG announcements:
- Last Call Working Draft - maybe Q4 (fourth quarter) 2011
- Candidate Recommendation
- Completed Standard "Recommendation"
Drafts and discussions:
- Authoring Tool Accessibility Guidelines (ATAG) Overview - this follows a template to match the others for WAI-ARIA, WCAG, UAAG
- [Draft] W3C Authoring Tools page (Analysis) - Liam McGee is working on these
- 26 April 2011 call for review e-mail, targeted e-mail
- ATAG 2.0 Working Draft, ATAG Implementation Guide
- WCAG 2 blog posts for Last Call, CR, Proposed Rec, done!
- Fact Sheet for "Authoring Tool Accessibility Guidelines 1.0" - very old FAQ
- Press releases: ATAG 1.0 press release, WCAG 2.0 CR press release, WCAG 2.0 done
- Selecting and Using Authoring Tools for Web Accessibility - this is out of date
- Analysis of physical materials for WAI outreach - this is rough and not currently being worked on
- [Rough Draft] Promotional Campaign: Integrating Web Accessibility in Courses - this is incomplete and not currently being worked on
- [EARLY ROUGH DRAFT] Requirements and Changelog for [Promoting and Advocating for Web Accessibility] - this is old
All may write.
@@ hook with backend and they'll figure out the other side.
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 firstname.lastname@example.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 email@example.com