Implementation Status - Authoring Tool Accessibility Guidelines
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: email@example.com.
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
1.1 Ensure that the author can produce accessible content in the
markup language(s) supported by the tool. [Priority 1] (Techniques
- Amaya allows the author to do anything in HTML
except for a minor bug in the implementation of the MAP element.
- asWedit does the same.
1.2 Ensure that the tool preserves all accessibility information
during authoring, transformations and conversions. [Priority 1] (Techniques
- asWedit provides the ability to transform
elements but does not remove content.
2.2 Ensure that the tool automatically generates valid markup. [Priority 1] (Techniques
- Amaya generates valid markup.
- 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.
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
- Amaya does not generate alternatives
- Word does not generate alternatives.
6.1 Document all features that promote the production of accessible
content. [Priority 1] (Techniques
- Word provides an accessibility section in the
text-only version of Word accessibility features is available on
- HotMetal documents accessibility
7.2 Allow the author to change the presentation within editing views
without affecting the document markup. [Priority 1] (Techniques
- Amaya implements user-side style sheets, and
allows the author to disable linked stylesheets in a user
- Any tool that implements Cascading Style Sheets [CSS] will satisfy this checkpoint.
7.3 Allow the author to edit all properties of each element and object
in an accessible fashion. [Priority 1] (Techniques
- Amaya provides access to all elements through
the structure view or the attributes menu.
- Any text-editing tool.
7.4 Ensure the editing view allows navigation via the structure of the
document in an accessible fashion. [Priority 1] (Techniques
- Amaya provides a structure view and a Table of
Contents, both of which can be navigated and synchronized with other
- 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
Priority 2 checkpoints
2.1 Use the latest versions of W3C Recommendations when they
are available and appropriate for a task. [Priority 2] (Techniques
- Amaya implements XHTML 1.0
- asWedit implements HTML 4.0 (the latest state
of HTML when the tool was created).
4.3 Allow the author to preserve markup not recognized by the tool.
[Priority 2] (Techniques
- asWedit offers the author an option of fixing
unrecognized markup, or leaving it.
- HotMetal offers the author an option of
fixing unrecognized markup, or leaving it.
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
- Word has a single overall look and feel for
accessibility related practices and other tasks.
- Amaya has a single "look and feel" for almost
all tasks (transformations are slightly different).
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
- 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
- HotDog makes accessibility visible at the "top
level" of the user interface, highlighting problems and prompting for
6.2 Ensure that creating accessible content is a naturally integrated
part of the documentation, including examples. [Priority 2] (Techniques
- Amaya documentation has accessibility
requirements included throughout the documentation.
7.5 Enable editing of the structure of the document in an accessible
fashion. [Priority 2] (Techniques
- Word enables editing of the outline view.
- Amaya enables editing via the structure view,
or editing by structure (select, copy, cut, paste) within the
7.6 Allow the author to search within editing views. [Priority 2] (Techniques
- Most editing tools (including all those listed, but not some
graphics/multimedia tools) have a search function.
Priority 3 checkpoints
2.3 If markup produced by the tool does not conform to W3C
specifications, inform the author. [Priority 3] (Techniques
- asWedit drops out of HTML mode if the markup
is not valid.
- Amaya highlights invalid markup in the
3.5 Provide functionality for managing, editing, and reusing
alternative equivalents for multimedia objects. [Priority 3] (Techniques
- A-Prompt provides a database-type tool for
managing alternative content.
- TopPage associates alt text with images and
provides them for re-use.
4.4 Provide the author with a summary of the document's accessibility
status. [Priority 3] (Techniques
- HotMetal provides a summary of accessibility
errors that remain.
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
- Word allows this via search and replace, or more
powerfully via macro scripting.
- Amaya provides a mechanism for transforming
6.3 In a dedicated section, document all features of the tool that
promote the production of accessible content. [Priority 3] (Techniques
- Word has an accessibility section of the
- Amaya has an accessibility section of the
The following HTML authoring tools are referenced in this document:
- Description: The W3C testbed browser/editor. This is a WYSIWYG HTML authoring tool.
- Produced by: W3C (Amaya home).
- Versions: 2.4 on Linux.
- Description: Interactive authoring accessibility tool.
- Produced by: The University of Toronto's ATRC and the University of
Wisconsin's TRACE center.
- Description: A validating HTML source editor.
- Produced by: Advasoft (asWedit home).
- Versions: 4.0 on linux.
- Description: An accessibility testing service available online or
as a downloadable tool.
- Produced by: CAST (Bobby home).
- Versions: 3.1.1, online.
- Description: An HTML source editor.
- Produced by: Sausage.
- Versions: 6.0alpha on Windows.
- Description: A WYSIWYG HTML authoring tool.
- Produced by: SoftQaud.
- Versions: 4.0 and 5.0 on Windows. Version 5.0 is referenced unless
- Description: A WYSIWYG HTML authoring tool.
- Produced by: IBM
- Version: 2 on Windows.
- 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.
For the latest version of any W3C specification please consult the list of
W3C Technical Reports at http://www.w3.org/TR.
- "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/.
- "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
- " 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
- Two levels of Cascading Style Sheets are W3C Recommendations: CSS Level 1 and CSS
- "Web Content
Accessibility Guidelines 1.0," W. Chisholm, G. Vanderheiden, and I.
Jacobs, eds., 5 May 1999. This Recommendation is
Last modified: $Date: 2000/02/01 19:02:33 $
©1999, 2000 W3C® (MIT, INRIA, Keio), All
Rights Reserved. W3C liability,
use and software
licensing rules apply.