| ZVON > References > ATAG 1.0 |
| Intro / Search / ZVON |
| Previous | Next | Guidelines | >> Priorities << |
| Priority | Description |
|---|---|
| 1 [goto] | If the checkpoint is essential to meeting the goals. |
| 2 [goto] | If the checkpoint is important to meeting the goals. |
| 3 [goto] | If the checkpoint is beneficial to meeting the goals. |
| relative [goto] | Some checkpoints that refer to generating, authoring, or checking Web content have multiple priorities. The priority depends on the corresponding priority in the Web Content Accessibility Guidelines (WCAG) 1.0. |
| Guideline 1 | 1.1 | Ensure that the author can produce accessible content in the markup language(s) supported by the tool. |
| 1.2 | Ensure that the tool preserves all accessibility information during authoring, transformations, and conversions. | |
| Guideline 2 | 2.2 | Ensure that the tool automatically generates valid markup. |
| Guideline 3 | 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. |
| Guideline 6 | 6.1 | Document all features that promote the production of accessible content. |
| Guideline 7 | 7.1 | Use all applicable operating system and accessibility standards and conventions [P1,P2,P3] |
| Guideline 7 | 7.2 | Allow the author to change the presentation within editing views without affecting the document markup. |
| 7.3 | Allow the author to edit all properties of each element and object in an accessible fashion. | |
| 7.4 | Ensure that the editing view allows navigation via the structure of the document in an accessible fashion. |
| Guideline 2 | 2.1 | Use the latest versions of W3C Recommendations when they are available and appropriate for a task. |
| Guideline 4 | 4.3 | Allow the author to preserve markup not recognized by the tool. |
| Guideline 5 | 5.1 | Ensure that functionality related to accessible authoring practices is naturally integrated into the overall look and feel of the tool. |
| 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. | |
| Guideline 6 | 6.2 | Ensure that creating accessible content is a naturally integrated part of the documentation, including examples. |
| Guideline 7 | 7.1 | Use all applicable operating system and accessibility standards and conventions [P1,P2,P3] |
| Guideline 7 | 7.5 | Enable editing of the structure of the document in an accessible fashion. |
| 7.6 | Allow the author to search within editing views. |
| Guideline 2 | 2.3 | If markup produced by the tool does not conform to W3C specifications, inform the author. |
| Guideline 3 | 3.5 | Provide functionality for managing, editing, and reusing alternative equivalents for multimedia objects. |
| Guideline 4 | 4.4 | Provide the author with a summary of the document's accessibility status. |
| 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. | |
| Guideline 6 | 6.3 | In a dedicated section, document all features of the tool that promote the production of accessible content. |
| Guideline 7 | 7.1 | Use all applicable operating system and accessibility standards and conventions [P1,P2,P3] |