This section is informative.
This mapping shows how the ATAG 1.0 checkpoints relate to the ATAG 2.0 Working Draft. 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.
| Requirements in ATAG 1.0 Recommendation | Location of Requirements 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] | Guideline B.1.1 (Support web content technologies that enable the creation of content that is accessible). Especially success criteria: B.1.1.1, B.1.1.2 and B.1.1.3. |
| 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). Especially success criteria: B.1.2.1, B.1.2.2, and B.1.2.3. |
| 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). Especially success criteria: B.1.3.1, B.1.3.2, and B.1.3.3. |
| 1.4 Ensure that templates provided by the tool conform to the Web Content Accessibility Guidelines 1.0. [Relative Priority] | Guideline B.2.5 (Assist authors with accessible templates and other pre-authored content). Especially success criteria: B.2.5.1, B.2.5.3, and B.2.5.9. |
| Guideline 2. Generate standard markup. | See details below. |
| 2.1 Use the latest versions of W3C Recommendations when they are available and appropriate for a task. [Priority 2] | Guideline B.1.1 (Support web content technologies that enable the creation of content that is accessible). Especially success criteria: B.1.1.1, B.1.1.2, and B.1.1.3. The W3C specificity has been dropped. |
| 2.2 Ensure that the tool automatically generates valid markup. [Priority 1] | Removed because this is covered by WCAG 2.0, which ATAG 2.0 references. |
| 2.3 If markup produced by the tool does not conform to W3C specifications, inform the author. [Priority 3] | Removed because higher priority requirements under Guideline B.1.3 (Ensure that automatically generated content is accessible) prevent this situation. |
| 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] | Now covered more generally by Guideline B.2.3 (Assist authors in repairing accessibility problems) and also by success criterion B.2.1.2 (Set Accessible Properties: Mechanisms that set the properties of web content (e.g., attribute values, etc.) also include the ability to set the accessibility-related properties. (Level A)). |
| 3.2 Help the author create structured content and separate information from its presentation. [Relative Priority] | Now covered more generally by Guideline B.2.3 (Assist authors in repairing accessibility problems.) |
| 3.3 Ensure that prepackaged content conforms to the Web Content Accessibility Guidelines 1.0. [Relative Priority] | Guideline B.2.5 (Assist authors with accessible templates and other pre-authored content). Especially success criteria: B.2.5.2 and B.2.5.8. |
| 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 with managing alternative content for non-text content). Especially success criteria: B.2.4.1, B.2.4.2 and B.2.4.3. |
| 3.5 Provide functionality for managing, editing, and reusing alternative equivalents for multimedia objects. [Priority 3] | Guideline B.2.4 (Assist authors with managing alternative content for non-text content). Especially success criterion: B.2.4.4. |
| Guideline 4. Provide ways of checking and correcting inaccessible content. | Now covered by 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. Especially success criteria: B.2.2.1, B.2.2.5 and B.2.2.10. |
| 4.2 Assist authors in correcting accessibility problems. [Relative Priority] | Guideline B.2.3 Assist authors in repairing accessibility problems. Especially success criteria: B.2.3.1, B.2.3.2 and B.2.3.3. |
| 4.3 Allow the author to preserve markup not recognized by the tool. [Priority 2] | Guideline B.1.2 Ensure that the authoring tool preserves accessibility information. Especially success criterion: B.1.2.4. |
| 4.4 Provide the author with a summary of the document's accessibility status. [Priority 3] | Guideline B.2.2 Assist authors in checking for accessibility problems. Especially success criterion: B.2.2.6. |
| 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 just one of many repair strategies. |
| Guideline 5. Integrate accessibility solutions into the overall "look and feel". | Now covered by 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] | Now covered more generally throughout PRINCIPLE B.3 (Accessibility solutions must be promoted and integrated). |
| 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. | Now covered by 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.3 Ensure that features of the authoring tool supporting the production of accessible content are documented. Especially success criterion: B.3.3.1. |
| 6.2 Ensure that creating accessible content is a naturally integrated part of the documentation, including examples. [Priority 2] | Guideline B.3.4 Ensure that any authoring practices demonstrated in documentation are accessible. Especially success criteria: B.3.4.1, B.3.4.2, and B.3.4.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 success criterion: B.3.3.1. |
| Guideline 7. Ensure that the authoring tool is accessible to authors with disabilities. | Expanded into Principle A.1 (Authoring tool user interfaces must follow applicable accessibility guidelines), Principle A.2 (Editing views must be perceivable), Principle A.3 (Editing views must be operable) and Principle A.4 (Editing views 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). | Now covered by Guideline A.1.1 ([For the authoring tool user interface] Ensure that web-based functionality is accessible) and Guideline A.1.2 ([For the authoring tool user interface] Ensure that non-web-based functionality is accessible). |
| 7.2 Allow the author to change the presentation within editing views without affecting the document markup. [Priority 1] | Guideline A.2.3 ([For the authoring tool user interface] Ensure the independence of the authors' display preferences) |
| 7.3 Allow the author to edit all properties of each element and object in an accessible fashion. [Priority 1] | Now covered more generally by Guideline A.1.1 ([For the authoring tool user interface] Ensure that web-based functionality is accessible) and Guideline A.1.2 ([For the authoring tool user interface] Ensure that non-web-based functionality is accessible). |
| 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] Enhance navigation and editing via content structure). Especially success criterion: B.3.4.2. |
| 7.5 Enable editing of the structure of the document in an accessible fashion. [Priority 2] | Now covered more generally by Guideline A.1.1 ([For the authoring tool user interface] Ensure that web-based functionality is accessible) and Guideline A.1.2 ([For the authoring tool user interface] Ensure that non-web-based functionality is accessible). |
| 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 of the content) |