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 Working Draft (6 February 2008). 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. PRINCIPLE B.1 Production of accessible content must be enabled
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] Guideline B.1.2 Ensure that the authoring tool preserves accessibility information.
1.3 Ensure that when the tool automatically generates markup it conforms to the W3C's Web Content Accessibility Guidelines 1.0. [Relative Priority] Guideline B.1.3 Ensure that automatically generated content is accessible
1.4 Ensure that templates provided by the tool conform to the Web Content Accessibility Guidelines 1.0. [Relative Priority] Made more general:
Guideline B.2.5 Assist authors with accessible templates and other pre-authored content.
Guideline 2. Generate standard markup. Combined under:
PRINCIPLE B.1 Production of accessible content must be enabled
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:
Guideline B.1.1 Support Web content technologies that enable the creation of content that is accessible.
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 Guideline B.1.3.
Guideline 3. Support the creation of accessible content. PRINCIPLE B.2 Authors must be supported 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:
Guideline B.2.1 Prompt authors to create accessible content.
3.2 Help the author create structured content and separate information from its presentation. [Relative Priority] Combined into Guideline B.2.1
3.3 Ensure that prepackaged content conforms to the Web Content Accessibility Guidelines 1.0. [Relative Priority] Combined into Guideline B.2.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] Guideline B.2.4 Assist authors to manage, edit, and reuse equivalent alternatives for non-text objects.
3.5 Provide functionality for managing, editing, and reusing alternative equivalents for multimedia objects. [Priority 3] Combined into Guideline B.2.4.
Guideline 4. Provide ways of checking and correcting inaccessible content. Combined under:
PRINCIPLE B.2 Authors must be supported in the production of accessible content
4.1 Check for and inform the author of accessibility problems. [Relative Priority] Guideline B.2.2 Assist authors in checking for accessibility problems.
4.2 Assist authors in correcting accessibility problems. [Relative Priority] Guideline B.2.3 Assist authors in repairing accessibility problems.
4.3 Allow the author to preserve markup not recognized by the tool. [Priority 2] Combined into Guideline B.1.2.
4.4 Provide the author with a summary of the document's accessibility status. [Priority 3] Combined into Guideline B.2.2.
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:
PRINCIPLE B.3 Accessibility solutions must be promoted and integrated
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 Principle 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]

Guideline B.3.1 Ensure that accessible authoring actions are given prominence.

Guideline 6. Promote accessibility in help and documentation. Combined into:
PRINCIPLE B.3 Accessibility solutions must be promoted and integrated
6.1 Document all features that promote the production of accessible content. [Priority 1] Guideline B.3.4 Ensure that features of the authoring tool supporting the production of accessible content are documented.
6.2 Ensure that creating accessible content is a naturally integrated part of the documentation, including examples. [Priority 2] Guideline B.3.5 Ensure that any authoring practices demonstrated in documentation are accessible.
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 Guideline B.3.4.
Guideline 7. Ensure that the authoring tool is accessible to authors with disabilities.

Expanded into:
PRINCIPLE A.1 Authoring tool must facilitate access by assistive technologies
PRINCIPLE A.2 Authoring tool user interface must be perceivable
PRINCIPLE A.3 Authoring tool user interface must be operable
PRINCIPLE A.4 Authoring tool user interface must be understandable

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:
Guideline A.1.1 [For the authoring tool user interface] Ensure that Web-based functionality is accessible.
Guideline A.1.2 [For the authoring tool user interface] Support interoperability with assistive technologies.
Guideline A.1.3 [For the authoring tool user interface] Follow the accessibility conventionsb of the platform.
Guideline A.2.1 [For the authoring tool user interface] Display text alternatives for non-text objects.
Guideline A.2.2 [For the authoring tool user interface] Display synchronized alternatives for synchronized media.
Guideline A.2.3 [For the authoring tool user interface] Ensure that the interface can be presented in different ways.
Guideline A.2.4 [For the authoring tool user interface] Make it easier to see and hear the interface.
Guideline A.3.1 [For the authoring tool user interface] Ensure that all functionality is available from a keyboard.
Guideline A.3.2 [For the authoring tool user interface] Enable time-independent interaction.
Guideline A.3.3 [For the authoring tool user interface] Help authors avoid flashing that could cause seizures.
Guideline A.3.6 [For the authoring tool user interface] Manage preference settings.
Guideline A.3.7 [For the authoring tool user interface] Ensure that previews are as accessible as existing user agents.
Guideline A.4.1 Make text content readable and understandable.
Guideline A.4.2 [For the authoring tool user interface] Make functionality predictable.
Guideline A.4.3 [For the authoring tool user interface] Help users avoid and correct mistakes.
Guideline A.4.4 [For the authoring tool user interface] Document the user interface including all accessibility features.

7.2 Allow the author to change the presentation within editing views without affecting the document markup. [Priority 1] Combined into Guideline A.2.4.
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] Guideline A.3.4 [For the authoring tool user interface] Provide navigation and editing via content structure.
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] Guideline A.3.5 [For the authoring tool user interface] Provide text search.