W3C

Checklist for Authoring Tool Accessibility Guidelines "Wombat"

Working Group Internal Draft, 12 July 2001

This version:
http://www.w3.org/WAI/AU/wombat/010712-checklist
Latest version:
http://www.w3.org/WAI/AU/wombat/checklist
Previous version:
http://www.w3.org/WAI/AU/wombat/010622-checklist
ATAG 1.0 Recommendation Checklist:
http://www.w3.org/TR/2000/REC-ATAG10-20000203/atag10-chklist
Editors:
Jutta Treviranus - ATRC, University of Toronto
Charles McCathieNevile - W3C
Jan Richards - University of Toronto

Status of this document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.

This document is an informative appendix to the working draft document Authoring Tool Accessibility Guidelines "Wombat" Working Group Internal Draft, 12 July 2001. For more information please consult that document.

This document is an attempt to reflect the consensus of the Authoring Tool working group, but has not been endorsed by that group, the W3C or any of its members. It is inappropriate to reference this document as other than work-in-progress.

A list of current W3C Recommendations and other technical documents including Working Drafts and Notes can be found at http://www.w3.org/TR.

Table of contents


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 checkpoint 1.1
Checkpoint 1.2 Ensure that the tool preserves all accessibility information during transformations, and conversions. [Priority 1]
Techniques for checkpoint 1.2
Checkpoint 2.2 Ensure that markup which the tool automatically generates is valid for the language the tool is generating. [Priority 1]
Techniques for checkpoint 2.2
Checkpoint 3.3 Do not automatically generate equivalent alternatives or reuse previously authored alternatives without author confirmation, except when the function is known with certainty. [Priority 1]
Techniques for checkpoint 3.3
Checkpoint 5.1 Ensure that the functionalities for checkpoints 3.1, 3.2 and 4.1 are always clearly available to the user [Priority 1]

Techniques for checkpoint 5.2

Checkpoints 6.1 Document all features that promote the production of accessible content. [Priority 1]
Techniques for checkpoint 6.1
Checkpoint 7.1 Ensure that the authoring interface follows all operating environment conventions that benefit accessibility [Priority 1] for standards and conventions that are essential to accessibility
Techniques for checkpoint 7.1
Checkpoint 7.2 Ensure that the authoring interface enables accessible editing of all element and object properties. [Priority 1]
Techniques for checkpoint 7.2
Checkpoint 7.4 Allow the display preferences of the authoring interface to be changed without affecting the document markup. [Priority 1]
Techniques for checkpoint 7.4

Relative priority checkpoints:

Checkpoint 1.3 Ensure that when the tool automatically generates markup it conforms to the W3C's Web Content Accessibility Guidelines 1.0 [WCAG10]. [Relative Priority]
Techniques for checkpoint 1.3
Checkpoint 1.4 Ensure that all pre-authored content for the tool conforms to Web Content Accessibility Guidelines 1.0 [WCAG10]. [Relative Priority]
Techniques for checkpoint 1.4
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 checkpoint 3.1
Checkpoint 3.2 Help the author create structured content and separate information from its presentation. [Relative Priority]
Techniques for checkpoint 3.2
Checkpoint 4.1 Check for and inform the author of accessibility problems. [Relative Priority]
Techniques for checkpoint 4.1
Checkpoint 4.2 Assist authors in correcting accessibility problems. [Relative Priority]
Techniques for checkpoint 4.2
Checkpoint 5.4 Ensure that creating accessible content is a naturally integrated part of the documentation, including examples. [Relative Priority]

Techniques for checkpoint 5.4

Checkpoint 6.2 Document the process of using the tool to produce accessible content. [Relative Priority]

Techniques for checkpoint 6.2

Priority 2 Checkpoints:

Checkpoint 1.5 Allow the author to preserve markup not recognized by the tool. [Priority 2]
Techniques for checkpoint 1.5
Checkpoint 2.1 Use the latest versions of W3C Recommendations when they are available and appropriate for a task. [Priority 2]
Techniques for checkpoint 2.1
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 checkpoint 5.2
Checkpoint 5.3 Ensure that all functionality (prompts, checkers, information icons, etc.) related to accessible authoring practices is naturally integrated into the overall look and feel of the tool. [Priority 2]
Techniques for checkpoint 5.3
Checkpoint 7.1 Ensure that the authoring interface follows all operating environment conventions that benefit accessibility [Priority 2] for standards and conventions that are important to accessibility
Techniques for checkpoint 7.1
Checkpoint 7.3 Ensure that the authoring interface enables the author to edit the structure of the document [Priority 2]
Techniques for checkpoint 7.3
Checkpoint 7.5 Ensure that the authoring interface enables accessible navigation of editing views via the document structure. [Priority 2 (was P1 in ATAG10)]
Techniques for checkpoint 7.5
Checkpoint 7.6 Ensure the authoring interface allows the author to search within the editing views. [Priority 2]
Techniques for checkpoint 7.6

Priority 3 Checkpoints:

Checkpoint 3.4 Provide functionality for managing, editing, and reusing alternative equivalents for multimedia objects. [Priority 3]
Techniques for checkpoint 3.5
Checkpoint 4.3 Provide the author with a summary of the document's accessibility status. [Priority 3]
Techniques for checkpoint 4.3
Checkpoint 7.1 Ensure that the authoring interface follows all operating environment conventions that benefit accessibility. [Priority 3] for standards and conventions that are beneficial to accessibility
Techniques for checkpoint 7.1

Level Double-A conformance icon, W3C-WAI Web Content Accessibility Guidelines 1.0 Valid CSS! Valid XHTML 1.0!