W3C

Appendix B. Comparison of ATAG 1.0 checkpoints to ATAG 2.0

Editors:
Jan Richards - ATRC, University of Toronto

This section is informative.

This mapping shows how the ATAG 1.0 checkpoints relate to the @@ATAG 2.0 Editor's Draft (29 June 2006)@@. Note that ATAG 2.0 is still a draft and the ATAG 2.0 Guidelines and success criteria in no way supersede the checkpoints in ATAG 1.0.

The Working Group is working carefully to enable developers that are currently using ATAG 1.0 (which remains a stable and referenceable document) to ensure that they will be able to make a smooth transition to ATAG 2.0 when it is released.

Comparison Table

Requirements in ATAG 1.0 Recommendation Location in ATAG 2.0 Draft
Guideline 1. Support accessible authoring practices. Guideline B.1: Enable the production of accessible content
1.1 Ensure that the author can produce accessible content in the markup language(s) supported by the tool. [Priority 1]

Removed due to the overly general wording.

1.2 Ensure that the tool preserves all accessibility information during authoring, transformations, and conversions. [Priority 1] B.1.2 Ensure that the authoring tool preserves accessibility information during transformations and conversions. [Priority 1]
1.3 Ensure that when the tool automatically generates markup it conforms to the W3C's Web Content Accessibility Guidelines 1.0. [Relative Priority] B.1.4 Ensure that when the authoring tool automatically generates content it conforms to WCAG. [Relative Priority]
1.4 Ensure that templates provided by the tool conform to the Web Content Accessibility Guidelines 1.0. [Relative Priority]
Made more general:
B.1.5 Ensure that all pre-authored content for the authoring tool conforms to WCAG. [Relative Priority]
Guideline 2. Generate standard markup. Combined under:
Guideline B.1: Enable the production of accessible content.
2.1 Use the latest versions of W3C Recommendations when they are available and appropriate for a task. [Priority 2] No longer W3C technology specific:
B.1.1 Support content types that enable the creation of content that conforms to WCAG. [Priority 1]
2.2 Ensure that the tool automatically generates valid markup. [Priority 1] Removed because this is a WCAG-level issue.
2.3 If markup produced by the tool does not conform to W3C specifications, inform the author. [Priority 3] Removed because this is covered by B.1.4.
Guideline 3. Support the creation of accessible content. GUIDELINE B.2: Support the author in the production of accessible content
3.1 Prompt the author to provide equivalent alternative information (e.g., captions, auditory descriptions, and collated text transcripts for video). [Relative Priority] Made more general:
B.2.1 Prompt and assist the author to create content that conforms to WCAG. [Relative Priority]
3.2 Help the author create structured content and separate information from its presentation. [Relative Priority] Combined into B.2.1.
3.3 Ensure that prepackaged content conforms to the Web Content Accessibility Guidelines 1.0. [Relative Priority] Combined into B.1.5.
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] B.2.4 Assist authors to ensure that equivalent alternatives for non-text objects are accurate and fit the context. [Priority 1]
3.5 Provide functionality for managing, editing, and reusing alternative equivalents for multimedia objects. [Priority 3] B.2.5 Provide functionality for managing, editing, and reusing equivalent alternatives. [Priority 3]
Guideline 4. Provide ways of checking and correcting inaccessible content. Combined under:
GUIDELINE B.2: Support the author in the production of accessible content.
4.1 Check for and inform the author of accessibility problems. [Relative Priority] B.2.2 Check for and inform the author of accessibility problems. [Relative Priority]
4.2 Assist authors in correcting accessibility problems. [Relative Priority] B.2.3 Assist authors in repairing accessibility problems. [Relative Priority]
4.3 Allow the author to preserve markup not recognized by the tool. [Priority 2] Combined into:
B.1.3 Ensure that the author is notified before content is automatically removed. [Priority 2]
4.4 Provide the author with a summary of the document's accessibility status. [Priority 3] B.2.6 Provide the author with a summary of 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 used for style into style sheets. [Priority 3] Removed because this is a repair strategy.
Guideline 5. Integrate accessibility solutions into the overall "look and feel". Combined into:
GUIDELINE B.3: Promote and integrate accessibility solutions
5.1 Ensure that functionality related to accessible authoring practices is naturally integrated into the overall look and feel of the tool. [Priority 2] Removed because it is not testable. The content has been moved into an informative note for Guideline B.3.
5.2 Ensure that accessible authoring practices supporting Web Content Accessibility Guidelines 1.0 Priority 1 checkpoints are among the most obvious and easily initiated by the author. [Priority 2]

B.3.1 Ensure that the most accessible option for an authoring task is given priority. [Priority 2]

Guideline 6. Promote accessibility in help and documentation. Combined into:
GUIDELINE B.3: Promote and integrate accessibility solutions
6.1 Document all features that promote the production of accessible content. [Priority 1] B.3.5 Document features of the authoring tool that support the production of accessible content. [Priority 1]
6.2 Ensure that creating accessible content is a naturally integrated part of the documentation, including examples. [Priority 2] B.3.6 Ensure that any authoring practices demonstrated in repair instructions and documentation are accessible. [Priority 3]
6.3 In a dedicated section, document all features of the tool that promote the production of accessible content. [Priority 3] Removed because this is an implementation option for B.3.5.
Guideline 7. Ensure that the authoring tool is accessible to authors with disabilities.

Expanded into:
GUIDELINE A.1: Authoring Tool User Interface must be Perceivable
GUIDELINE A.2: Authoring Tool User Interface must be Operable
GUIDELINE A.3: Authoring Tool User Interface must be Understandable
GUIDELINE A.4: Authoring Tool User Interface must be Access System Friendly

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). Covered in more detail by:
A.1.1 For the authoring tool user interface, provide text alternatives for all non-text objects. [Priority 1]
A.1.2 For the authoring tool user interface, provide synchronized alternatives for multimedia. [Priority 2]
A.1.3 For the authoring tool user interface, ensure that all display preferences are configurable. [Priority 1]
A.1.5: For the authoring tool user interface, ensure that information, functionality, and structure can be separated from presentation. [Priority 1]
A.2.1 For the authoring tool user interface, ensure that all functionality is operable via a keyboard or a keyboard interface. [Priority 1]
A.2.2 For the authoring tool user interface, ensure user configurable access to selectable items. [Priority 3]
A.2.3 For the authoring tool user interface, allow authors to control time limits. [Priority 1]
A.2.4 For the authoring tool user interface, allow authors to avoid flashing that could cause seizures due to photosensitivity. [Priority 1]
A.2.7 For the authoring tool user interface, provide an undo function. [Priority 2]
A.2.8 For the authoring tool user interface, allow the author to have multiple sets of keyboard operability and display preferences settings. [Priority 2]
A.2.9 For the authoring tool user interface, ensure previews emulate the accessible rendering features of target user agents. [Priority 2]
A.3.1 For the authoring tool user interface, observe the accessibility conventions of the platform. [Priority 2]
A.3.2 For the authoring tool user interface, maintain consistency. [Priority 2]
A.3.3 For the authoring tool user interface, document the user interface including all accessibility features. [Priority 1]
A.4.1 For the authoring tool user interface, support interoperability with assistive technologies. [Priority 1]
A.4.2 For the authoring tool user interface, document how the authoring interface makes use of existing accessibility architectures. [Priority 3]
7.2 Allow the author to change the presentation within editing views without affecting the document markup. [Priority 1] A.1.4 For the authoring tool user interface, ensure changes to the display settings of editing views do not affect the content being edited. [Priority 1].
7.3 Allow the author to edit all properties of each element and object in an accessible fashion. [Priority 1] Removed because editing properties is covered by all of the other checkpoints in Part A.
7.4 Ensure that the editing view allows navigation via the structure of the document in an accessible fashion. [Priority 1] A.2.5 For the authoring tool user interface, ensure that editing views enable the author to navigate the structure and perform structure-based edits. [Priority 2]
7.5 Enable editing of the structure of the document in an accessible fashion. [Priority 2] Removed because editing the structure is covered by all of the other checkpoints in Part A.
7.6 Allow the author to search within editing views. [Priority 2] A.2.6 For the authoring tool user interface, allow the author to search content, including markup, within the editing views. [Priority 2]