ATAG 2.0 Accessible Authoring Practices and “support accessible authoring practices” discussion.

admin — Mon, 19 Nov 2007 02:25:05 +0000

In order to build an accessible website, authoring tools must produce content that upholds web content
accessibility standards and support accessible authoring practices. This is especially important if the organisation will be using a Content
Management System (CMS) to produce content automatically.
These practices are not well-defined within the W3C. When we say
“support accessible authoring practices” there is little sense of what
that means.
What we lack here is the audience that should be addressed.
- The primary audience for this document is the software developer involved in creating authoring tools.
- The Authoring Tool Accessibility Guidelines are also designed to be used by third parties to evaluate the
accessibility of existing tools.
Is this what the ATAG 2.0 spec is saying?

For those who are intrested in the subject matter of ATAG 2.0 here are the top10 Accessible Authoring Practices
that must be taken into account during the procurement of authoring tools and CMS.:
1. Provide Alternative Formats
* Alternatives for Text Presentations
* Alternatives for Other File Formats
* Alternatives for Images
* Alternatives for Programmed Objects
2. Provide Alternative Navigation
3. Provide a way to Bypass Repetitive Content
4. Present Text in a Linear Layout
5. Use Natural Language
6. Design for Device Independence
7. Provide Context Information
* Frame Context
* Table Context
* Lists, Layout, and Content Context
* Link Context
8. Explicitly Associate Labels with Form Elements and Group Related form Fields
9. Associate Table Headers with Table Cells
10. Describe the Access Strategies a Site Uses

Let the Web work better for everyone

ATAG 2.0 Accessible Authoring Practices and “support accessible authoring practices” discussion.