Implementation Status - Authoring Tool Accessibility Guidelines (ATAG) 1.0

This page documents how some authoring tools satisfy the checkpoints of the Authoring Tool Accessibility Guidelines 1.0 [ATAG10]. The intention of this page is to establish that at least one deployed authoring tool satisfies each checkpoint; there may be other tools that satisfy the checkpoint but are not listed.

Disclaimer. W3C makes available this information as a service to the Web community. W3C does not guarantee the accuracy or permanence of information regarding checkpoint implementations. W3C holds no liability for inaccuracies. The claims in these documents have not been reviewed by vendors.

This document has been produced as part of the Web Accessibility Initiative. The goals of the WAI Authoring Tool Guidelines Working Group (AUWG) are discussed in the Working Group charter.

Please send comments about this document to the public mailing list: w3c-wai-au@w3.org.

Authoring Tool Accessibility Guidelines 1.0 Checkpoints

The checkpoints are listed in the same order as they appear in the checklist appendix [ATAG10-CHKLIST]. Each checkpoint includes a link to where the checkpoint is explained in the guidelines [ATAG10] and Techniques Document [ATAG10-TECHS]. Each checkpoint is followed by a list of tools known to satisfy the checkpoint.

Note. All tools were added to this page on 29 December 1999 except where otherwise indicated.

Priority 1 checkpoints

Checkpoint 1.1 Ensure that the author can produce accessible content in the markup language(s) supported by the tool. [Priority 1] (Techniques for 1.1)
1. Amaya allows the author to do anything in HTML except for a minor bug in the implementation of the MAP element.
2. asWedit does the same.
Checkpoint 1.2 Ensure that the tool preserves all accessibility information during authoring, transformations and conversions. [Priority 1] (Techniques for 1.2)
1. asWedit provides the ability to transform elements but does not remove content.
Checkpoint 2.2 Ensure that the tool automatically generates valid markup. [Priority 1] (Techniques for 2.2)
1. Amaya generates valid markup.
2. asWedit validates markup as it is created. If the markup is not valid according to the DTD being used, the editor drops out of HTML mode and only the free text editing mode works.
Checkpoint 3.4 Do not automatically generate equivalent alternatives. Do not reuse previously authored alternatives without author confirmation, except when the function is known with certainty. [Priority 1] (Techniques for 3.4)
1. Amaya does not generate alternatives automatically.
2. Word does not generate alternatives.
Checkpoint 6.1 Document all features that promote the production of accessible content. [Priority 1] (Techniques for 6.1)
1. Word provides an accessibility section in the documentation. A text-only version of Word accessibility features is available on the Web.
2. HotMetal documents accessibility features.
Checkpoint 7.2 Allow the author to change the presentation within editing views without affecting the document markup. [Priority 1] (Techniques for 7.2)
1. Amaya implements user-side style sheets, and allows the author to disable linked stylesheets in a user session.
2. Any tool that implements Cascading Style Sheets [CSS] will satisfy this checkpoint.
Checkpoint 7.3 Allow the author to edit all properties of each element and object in an accessible fashion. [Priority 1] (Techniques for 7.3)
1. Amaya provides access to all elements through the structure view or the attributes menu.
2. Any text-editing tool.
Checkpoint 7.4 Ensure the editing view allows navigation via the structure of the document in an accessible fashion. [Priority 1] (Techniques for 7.4)
1. Amaya provides a structure view and a Table of Contents, both of which can be navigated and synchronized with other views.
2. Word provides an outline facility that can be used to navigate various levels of headers.

Relative Priority checkpoints

Note: These should be assessed by reference to the checkpoints of the Web Content Accessibility Guidelines [WCAG10], and may be met at three different levels.

Checkpoint 1.3 Ensure that when the tool automatically generates markup it conforms to the W3C's Web Content Accessibility Guidelines [WCAG10]. [Relative Priority] (Techniques for 1.3)
1. HotMetal provides an accessibility checking mode.
Checkpoint 1.4 Ensure that templates provided by the tool conform to the Web Content Accessibility Guidelines [WCAG10]. [Relative Priority] (Techniques for 1.4)
1. Amaya provides accessible templates.
2. HoTMetaL 4.0 provides accessible templates.
Checkpoint 3.1 Prompt the author to provide equivalent alternative information (e.g., captions, auditory descriptions and collated text transcripts for video). [Relative Priority] (Techniques for 3.1)
1. HotMetal prompts the author for alternatives to media objects.
2. Amaya prompts the author for alternative content, but not in all cases.
Checkpoint 3.2 Help the author create structured content and separate information from its presentation. [Relative Priority] (Techniques for 3.2)
1. Word provides an interface that allows the author to create style sheets for presentation, and structure the document by classes.
2. Amaya provides a structured editing environment and a simple way of abstracting presentation into [CSS] rules.
Checkpoint 3.3 Ensure that prepackaged content conforms to Web Content Accessibility Guidelines [WCAG10]. [Relative Priority] (Techniques for 3.3)
1. HoTMetaL 4.0 provides accessible template pages.
Checkpoint 4.1 Check for and inform the author of accessibility problems. [Relative Priority] (Techniques for 4.1)
1. A-Prompt checks for various accessibility problems.
2. HotMetal checks for accessibility errors.
3. Bobby checks for [WCAG10] conformance. Some tests require the author to confirm actions.
Checkpoint 4.2 Assist authors in correcting accessibility problems. [Relative Priority] (Techniques for 4.2)
1. A-Prompt corrects identified problems (providing assistance to do so).
2. HotMetal prompts the author to correct problems.
Checkpoint 7.1 Use all applicable operating system and accessibility standards and conventions (Priority 1 for standards and conventions that are essential to accessibility, Priority 2 for those that are important to accessibility, Priority 3 for those that are beneficial to accessibility). (Techniques for 7.1)
Note: Without access to source code it is difficult to verify this checkpoint. However there seems no reason to disbelieve manufacturers' claims.
1. Word (apparently) implements system standards and conventions.
2. asWedit (apparently) is implemented in Motif standard widgets, and provides keyboard access to all functions.

Priority 2 checkpoints

Checkpoint 2.1 Use the latest versions of W3C Recommendations when they are available and appropriate for a task. [Priority 2] (Techniques for 2.1)
1. Amaya implements XHTML 1.0
2. asWedit implements HTML 4.0 (the latest state of HTML when the tool was created).
Checkpoint 4.3 Allow the author to preserve markup not recognized by the tool. [Priority 2] (Techniques for 4.3)
1. asWedit offers the author an option of fixing unrecognized markup, or leaving it.
2. HotMetal offers the author an option of fixing unrecognized markup, or leaving it.
Checkpoint 5.1 Ensure that functionality related to accessible authoring practices is naturally integrated into the overall look and feel of the tool. [Priority 2] (Techniques for 5.1)
1. Word has a single overall look and feel for accessibility related practices and other tasks.
2. Amaya has a single "look and feel" for almost all tasks (transformations are slightly different).
Checkpoint 5.2 Ensure that accessible authoring practices supporting Web Content Accessibility Guidelines 1.0 [WCAG10] Priority 1 checkpoints are among the most obvious and easily initiated by the author. [Priority 2] (Techniques for 5.2)
1. Amaya provides an interface that makes it easy and obvious to implement style sheets, use structure, provide alternatives for some elements; some features are missing in the release tested.
2. HotDog makes accessibility visible at the "top level" of the user interface, highlighting problems and prompting for information.
Checkpoint 6.2 Ensure that creating accessible content is a naturally integrated part of the documentation, including examples. [Priority 2] (Techniques for 6.2)
1. Amaya documentation has accessibility requirements included throughout the documentation.
Checkpoint 7.5 Enable editing of the structure of the document in an accessible fashion. [Priority 2] (Techniques for 7.5)
1. Word enables editing of the outline view.
2. Amaya enables editing via the structure view, or editing by structure (select, copy, cut, paste) within the formatted view.
Checkpoint 7.6 Allow the author to search within editing views. [Priority 2] (Techniques for 7.6)
1. Most editing tools (including all those listed, but not some graphics/multimedia tools) have a search function.

Priority 3 checkpoints

Checkpoint 2.3 If markup produced by the tool does not conform to W3C specifications, inform the author. [Priority 3] (Techniques for 2.3)
1. asWedit drops out of HTML mode if the markup is not valid.
2. Amaya highlights invalid markup in the structure view.
Checkpoint 3.5 Provide functionality for managing, editing, and reusing alternative equivalents for multimedia objects. [Priority 3] (Techniques for 3.5)
1. A-Prompt provides a database-type tool for managing alternative content.
2. TopPage associates alt text with images and provides them for re-use.
Checkpoint 4.4 Provide the author with a summary of the document's accessibility status. [Priority 3] (Techniques for 4.4)
1. HotMetal provides a summary of accessibility errors that remain.
Checkpoint 4.5 Allow the author to transform presentation markup that is misused to convey structure into structural markup, and to transform presentation markup used for style into style sheets. [Priority 3] (Techniques for 4.5)
1. Word allows this via search and replace, or more powerfully via macro scripting.
2. Amaya provides a mechanism for transforming elements.
Checkpoint 6.3 In a dedicated section, document all features of the tool that promote the production of accessible content. [Priority 3] (Techniques for 6.3)
1. Word has an accessibility section of the documentation.
2. Amaya has an accessibility section of the documentation.

Tools

The following HTML authoring tools are referenced in this document:

Amaya

Description: The W3C testbed browser/editor. This is a WYSIWYG HTML authoring tool.
Produced by: W3C (Amaya home).
Versions: 2.4 on Linux.

A-Prompt

Description: Interactive authoring accessibility tool.
Produced by: The University of Toronto's ATRC and the University of Wisconsin's TRACE center.
Versions:

asWedit

Description: A validating HTML source editor.
Produced by: Advasoft (asWedit home).
Versions: 4.0 on linux.

Bobby

Description: An accessibility testing service available online or as a downloadable tool.
Produced by: CAST (Bobby home).
Versions: 3.1.1, online.

HotDog

Description: An HTML source editor.
Produced by: Sausage.
Versions: 6.0alpha on Windows.

HotMetal

Description: A WYSIWYG HTML authoring tool.
Produced by: SoftQaud.
Versions: 4.0 and 5.0 on Windows. Version 5.0 is referenced unless otherwise indicated.

TopPage

Description: A WYSIWYG HTML authoring tool.
Produced by: IBM
Version: 2 on Windows.

Word

Description: A word processor that, by virtue of its "save as web page" function can be used as a WYSIWYG HTML authoring tool.
Produced by: Microsoft
Versions: Word 2000 on Windows 2000 beta.

References

For the latest version of any W3C specification please consult the list of W3C Technical Reports at http://www.w3.org/TR.

[ATAG10]: "Authoring Tool Accessibility Guidelines 1.0," J. Treviranus, C. McCathieNevile, I. Jacobs, and J. Richards, eds., 2 February 2000. The 2 February Recommendation is http://www.w3.org/TR/2000/REC-ATAG10-20000202/.
[ATAG10-CHKLIST]: "List of Checkpoints for Authoring Tool Accessibility Guidelines 1.0 - Working Draft," J. Treviranus, C. McCathieNevile, I. Jacobs, and J. Richards, eds., 2 February 2000. The 2 February 2000 document is http://www.w3.org/TR/2000/REC-ATAG10-20000202/atag10-chklist.
[ATAG10-TECHS]: " Techniques for Authoring Tool Accessibility Guidelines 1.0," J. Treviranus, C. McCathieNevile, I. Jacobs, and J. Richards, eds., 2 February 2000. The 2 February Note is http://www.w3.org/TR/2000/NOTE-ATAG10-TECHS-20000202/.
[CSS]: Two levels of Cascading Style Sheets are W3C Recommendations: CSS Level 1 and CSS Level 2.
[WCAG10]: "Web Content Accessibility Guidelines 1.0," W. Chisholm, G. Vanderheiden, and I. Jacobs, eds., 5 May 1999. This Recommendation is http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505.

Charles McCathieNevile
Last modified: $Date: 2000/02/01 19:02:33 $