This document is an appendix to the W3C "Authoring Tool Accessibility Guidelines 1.0 (working draft)". It provides a list of all checkpoints from the Authoring Tool Accessibility Guidelines 1.0 (working draft), organized by concept, as a checklist for authoring tool developers. Please refer to the Guidelines document for introductory information, information about related documents, a glossary of terms, and more.
This list may be used to review a tool or set of tools for accessibility. For each checkpoint, indicate whether the checkpoint has been satisfied, has not been satisfied, or is not applicable.
A list version of the checkpoints is also available.
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 appendix to a Working Draft. It is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". This is work in progress and does not imply endorsement by, or the consensus of, either W3C or Members of the WAI Authoring Tool Working Group.
Please send comments about this document to the public mailing list: email@example.com.
This document has been produced as part of the Web Accessibility Initiative. The goal of the WAI Authoring Tool Guidelines Working Group is discussed in the Working Group charter.
A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR.
Each checkpoint has a priority level. The priority level reflects the impact of the checkpoint in meeting the goals of this document. These goals are:
The three priority levels are assigned as follows:
Some checkpoints that refer to generating, authoring, or checking Web content have multiple priorities. The priority is dependent on the priority in the Web Content Accessibility Guidelines [WAI-WEBCONTENT].
For example providing text equivalents for
images and audio is a priority 1 requirement in [WAI-WEBCONTENT] since
without it one or more groups will find it impossible to access the
information. Therefore, it is a priority 1 requirement for the authoring
tool to check for (4.1) or ask the author for
(3.1) equivalent alternatives for these types of
content. Expansion of abbreviations and acronyms with
ACRONYM elements by using the "
attribute is a priority 3 in [WAI-WEBCONTENT]. Therefore it is only
priority 3 for the authoring tool to check for (4.1)
or ask the author for (3.2) this
|1.1 Ensure that the author can produce accessible content in the markup language(s) supported by the tool. [Priority 1]|
|1.2 Ensure that the tool preserves all accessibility information during authoring, transformations and conversions. [Priority 1]|
|2.2 Ensure that the tool generates valid markup. [Priority 1]|
|3.4 Do not insert automatically generated or place-holder equivalent alternatives. [Priority 1]|
|6.1 Document all features that promote the production of accessible content. [Priority 1]|
|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). [Priority 1]|
|7.2 Allow the author to change the presentation within editing views without affecting the document markup. [Priority 1]|
|7.3 Allow the author to edit all properties of each element and object in an accessible fashion. [Priority 1]|
|7.4 Ensure the editing view allows navigation via the structure of the document in an accessible fashion. [Priority 1]|
|1.3 Ensure that the tool generates markup that conforms to the W3C's Web Content Accessibility Guidelines [WAI-WEBCONTENT]. [Relative Priority]|
|1.4 Ensure that templates provided by the tool conform to the Web Content Accessibility Guidelines [WAI-WEBCONTENT]. [Relative Priority]|
|3.1 Prompt the author to provide equivalent alternative information (e.g., captions, long descriptions of graphics). [Relative Priority]|
|3.2 Help the author create structured content and separate information from its presentation. [Relative Priority]|
|3.3 Ensure that prepackaged content conforms to [WAI-WEBCONTENT]. [Relative Priority]|
|4.1 Check for and alert the author to accessibility problems. [Relative Priority]|
|4.2 Assist authors in correcting accessibility problems. [Relative Priority]|
|2.1 Use the latest versions of W3C Recommendations when they are available and appropriate for a task. [Priority 2]|
|4.3 Allow the author to preserve markup not recognized by the tool. [Priority 2]|
|5.1 Ensure that functionalities related to accessible authoring practices are integrated into the tool. [Priority 2]|
|5.2 Ensure that [WAI-WEBCONTENT] Priority 1 accessible authoring practices are among the most obvious and easily initiated by the author. [Priority 2]|
|6.2 Ensure that creating accessible content is a naturally integrated part of the documentation, including examples. [Priority 2]|
|7.5 Enable editing of the structure of the document in an accessible fashion. [Priority 2]|
|7.6 Allow the author to search within editing views. [Priority 2]|
|2.3 If markup generated by the tool does not conform to W3C specifications, inform the author. [Priority 3]|
|3.5 Provide a mechanism to manage alternative information for multimedia objects, that retains and offers for editing pre-written or previously linked equivalent alternative information. [Priority 3]|
|4.4 Provide the author with a summary of the document's accessibility status. [Priority 3]|
|4.5 Allow the author to transform presentation markup that is misused to convey structure into structural markup, and to transform presentation markup that is stylistic into style sheets. [Priority 3]|
|6.3 In a dedicated section, document all features of the tool that promote the production of accessible content. [Priority 3]|
For the latest version of any W3C specification please consult the list of W3C Technical Reports.