This Checklist serves as an appendix to the Authoring Tool Accessibility Guidelines 2.0. It lists all of the guidelines and success criteria from ATAG 2.0 in a checkable list. For many readers, the Checklist provides a quick reference and overview to the information in ATAG 2.0.
This list may be used to review an authoring tool for accessibility. For each guideline, indicate whether the success criteria has been satisfied, has not been satisfied, or is not applicable.
Under each guideline there are success criteria that describe specifically what must be achieved in order to conform . They are similar to the "checkpoints" in ATAG 1.0. Each success criterion is written as a statement that will be either true or false when a specific authoring tool is tested against it.
All ATAG 2.0 success criteria are written to be testable. While some can be tested by software, others require human testers for part or all of the test.
For more information, see the ATAG 2.0 Conformance section.
Guideline | Success Criteria | Yes | No | N/A |
---|---|---|---|---|
A.1.1 [For the authoring tool user interface] Ensure that Web-based functionality is accessible. [Techniques] |
Note: This guideline does not apply to non-Web-based authoring tool user interfaces. |
|||
A.1.2 [For the authoring tool user interface] Support interoperability with assistive technologies. [Techniques] |
Applicability Note: This guideline does not apply to Web-based authoring tool user interface functionality. |
|||
A.1.3 [For the authoring tool user interface] Follow the accessibility conventions of the platform. [Techniques] |
|
|||
A.2.1 [For the authoring tool user interface] Display text alternatives for non-text objects. [Techniques] |
|
|||
A.2.2 [For the authoring tool user interface] Display synchronized alternatives for synchronized media. [Techniques] |
|
|||
A.2.3 [For the authoring tool user interface] Ensure that the interface can be presented in different ways. [Techniques] |
|
|||
A.2.4 [For the authoring tool user interface] Make it easier to see and hear the interface. [Techniques] |
Note: While the success criteria for this guideline are based on the capabilities of the platforms (e.g., operating systems, user agents, GUI toolkits) listed in the conformance profile, additional configuration settings may be provided. |
|||
A.3.1 [For the authoring tool user interface] Ensure that all functionality is available from a keyboard. [Techniques] |
Note 1: Web-based authoring tool user interface functionality may rely on the keyboard navigation functions of the user agent listed in the conformance profile to satisfy some of these success criteria. Note 2: This guideline should not discourage the support of other input methods (such as a mouse) in addition to keyboard operation. Also see Guideline A.3.1 when choosing keystrokes. |
|||
A.3.2 [For the authoring tool user interface] Enable time-independent interaction. [Techniques] |
|
|||
A.3.3 [For the authoring tool user interface] Help authors to avoid flashing that could cause seizures. [Techniques] |
|
|||
A.3.4 [For the authoring tool user interface] Provide navigation and editing via content structure. [Techniques] |
|
|||
A.3.7 [For the authoring tool user interface] Ensure that previews are as accessible as existing user agents. [Techniques] |
Note: Previews are treated differently than editing views because authors, including those with disabilities, will not be well-served if preview features diverge too much from the actual functionality of available user agents. Therefore, preview features are exempted from necessarily having to meet all of the other requirements in Part A of this guidelines document, if they meet this guideline. |
|||
A.4.2 [For the authoring tool user interface] Make functionality predictable. [Techniques] |
|
|||
A.4.3 [For the authoring tool user interface] Help users avoid and correct mistakes. [Techniques] |
Note 1: Web-based authoring tool user interface functionality may rely on the "undo" function of the user agent listed in the conformance profile to perform the undo function for some editing actions that do not involve server communication (e.g., typing in a text area). Note 2: It is acceptable to collect text entry actions (e.g., typed words, a series of backspaces) into a single reversible authoring action. |
|||
A.4.4 [For the authoring tool user interface] Document the user interface including all accessibility features. [Techniques] |
|
|||
B.1.1 Support Web content technologies that enable the creation of content that is accessible. [Techniques] |
Applicability Note: This guideline only applies when benchmarked technologies are available for authoring the particular type of content required (e.g., text, images, synchronized media). |
|||
B.1.2 Ensure that the authoring tool preserves accessibility information. [Techniques] |
|
|||
B.1.3 Ensure that automatically generated content is accessible. [Techniques] |
Applicability Note 1: This guidelines does apply to any accessibility problems that informed authorshave specifically allowed (e.g., by setting less strict preferences) (see Guideline B.3.3 for more on informing the author). Applicability Note 2: This guideline does not apply when authors have caused the accessibility problem(s) (e.g., by ignoring prompts for accessibility information, providing faulty information, etc.). |
|||
B.2.1 Prompt authors to create accessible content. [Techniques] |
|
|||
B.2.2 Assist authors in checking for accessibility problems. [Techniques] |
Note: While automated checking or more advanced implementations of semi-automated checking may improve the authoring experience, these are not required to meet the success criteria for this guideline. Applicability Note: This guideline does not apply if the authoring tool controls the authoring process to an extent that it is not possible for authors to introduce accessibility problems. |
|||
B.2.3 Assist authors in repairing accessibility problems. [Techniques] |
Note: While automated repairing or more advanced implementations of semi-automated repairing may improve the authoring experience, these are not required to meet the success criteria for this guideline. Applicability Note: This guideline does not apply if the authoring tool controls the authoring process to an extent that it is not possible for authors to introduce accessibility problems. |
|||
B.2.4 Assist authors to manage, edit, and reuse equivalent alternatives for non-text objects. [Techniques] |
Note: Equivalent alternatives should not be automatically generated from unreliable sources (e.g., file names should not be used as text alternatives). |
|||
B.2.5 Assist authors with accessible templates and other pre-authored content. [Techniques] |
Note: Templates may be complicated to check for accessibility due to their inherent incompleteness. The accessibility status of templates is instead measured by the accessibility of content created through their proper use. |
|||
B.3.1. Ensure that accessible authoring actions are given prominence. [Techniques] |
|
|||
B.3.3. Ensure that features of the authoring tool supporting the production of accessible content are available. [Techniques] |
|
|||
B.3.4. Ensure that features of the authoring tool supporting the production of accessible content are documented. [Techniques] |
|
Guideline | Success Criteria | Yes | No | N/A |
---|---|---|---|---|
A.1.1 [For the authoring tool user interface] Ensure that Web-based functionality is accessible. [Techniques] |
Note: This guideline does not apply to non-Web-based authoring tool user interfaces. |
|||
A.1.2 [For the authoring tool user interface] Support interoperability with assistive technologies. [Techniques] |
Applicability Note: This guideline does not apply to Web-based authoring tool user interface functionality. |
|||
A.1.3 [For the authoring tool user interface] Follow the accessibility conventions of the platform. [Techniques] |
|
|||
A.2.2 [For the authoring tool user interface] Display synchronized alternatives for synchronized media. [Techniques] |
|
|||
A.2.4 [For the authoring tool user interface] Make it easier to see and hear the interface. [Techniques] |
Note: While the success criteria for this guideline are based on the capabilities of the platforms (e.g., operating systems, user agents, GUI toolkits) listed in the conformance profile, additional configuration settings may be provided. |
|||
A.3.1 [For the authoring tool user interface] Ensure that all functionality is available from a keyboard. [Techniques] |
Note 1: Web-based authoring tool user interface functionality may rely on the keyboard navigation functions of the user agent listed in the conformance profile to satisfy some of these success criteria. Note 2: This guideline should not discourage the support of other input methods (such as a mouse) in addition to keyboard operation. Also see Guideline A.3.1 when choosing keystrokes. |
|||
A.3.4 [For the authoring tool user interface] Provide navigation and editing via content structure. [Techniques] |
|
|||
A.3.5 [For the authoring tool user interface] Provide text search. [Techniques] |
Note: Web-based authoring tool user interface functionality may rely on the "find" function of the user agent listed in the conformance profile to help perform the searches. |
|||
A.3.6 [For the authoring tool user interface] Manage preference settings. [Techniques] |
|
|||
A.4.2 [For the authoring tool user interface] Make functionality predictable. [Techniques] |
|
|||
A.4.3 [For the authoring tool user interface] Help users avoid and correct mistakes. [Techniques] |
Note 1: Web-based authoring tool user interface functionality may rely on the "undo" function of the user agent listed in the conformance profile to perform the undo function for some editing actions that do not involve server communication (e.g., typing in a text area). Note 2: It is acceptable to collect text entry actions (e.g., typed words, a series of backspaces) into a single reversible authoring action. |
|||
B.1.1 Support Web content technologies that enable the creation of content that is accessible. [Techniques] |
Applicability Note: This guideline only applies when benchmarked technologies are available for authoring the particular type of content required (e.g., text, images, synchronized media). |
|||
B.1.2 Ensure that the authoring tool preserves accessibility information. [Techniques] |
|
|||
B.1.3 Ensure that automatically generated content is accessible. [Techniques] |
Applicability Note 1: This guidelines does apply to any accessibility problems that informed authorshave specifically allowed (e.g., by setting less strict preferences) (see Guideline B.3.3 for more on informing the author). Applicability Note 2: This guideline does not apply when authors have caused the accessibility problem(s) (e.g., by ignoring prompts for accessibility information, providing faulty information, etc.). |
|||
B.2.1 Prompt authors to create accessible content. [Techniques] |
|
|||
B.2.2 Assist authors in checking for accessibility problems. [Techniques] |
Note: While automated checking or more advanced implementations of semi-automated checking may improve the authoring experience, these are not required to meet the success criteria for this guideline. Applicability Note: This guideline does not apply if the authoring tool controls the authoring process to an extent that it is not possible for authors to introduce accessibility problems. |
|||
B.2.3 Assist authors in repairing accessibility problems. [Techniques] |
Note: While automated repairing or more advanced implementations of semi-automated repairing may improve the authoring experience, these are not required to meet the success criteria for this guideline. Applicability Note: This guideline does not apply if the authoring tool controls the authoring process to an extent that it is not possible for authors to introduce accessibility problems. |
|||
B.2.4 Assist authors to manage, edit, and reuse equivalent alternatives for non-text objects. [Techniques] |
Note: Equivalent alternatives should not be automatically generated from unreliable sources (e.g., file names should not be used as text alternatives). |
|||
B.2.5 Assist authors with accessible templates and other pre-authored content. [Techniques] |
Note: Templates may be complicated to check for accessibility due to their inherent incompleteness. The accessibility status of templates is instead measured by the accessibility of content created through their proper use. |
|||
B.3.2. Ensure that sequential authoring processes integrate accessible authoring practices. [Techniques] |
|
|||
B.3.3. Ensure that features of the authoring tool supporting the production of accessible content are available. [Techniques] |
|
|||
B.3.5. Ensure that any authoring practices demonstrated in documentation are accessible. [Techniques] |
|
Guideline | Success Criteria | Yes | No | N/A |
---|---|---|---|---|
A.1.1 [For the authoring tool user interface] Ensure that Web-based functionality is accessible. [Techniques] |
Applicability Note: This guideline does not apply to non-Web-based authoring tool user interfaces. |
|||
A.1.2 [For the authoring tool user interface] Support interoperability with assistive technologies. [Techniques] |
Applicability Note: This guideline does not apply to Web-based authoring tool user interface functionality. |
|||
A.2.2 [For the authoring tool user interface] Display synchronized alternatives for synchronized media. [Techniques] |
|
|||
A.2.3 [For the authoring tool user interface] Ensure that the interface can be presented in different ways. [Techniques] |
|
|||
A.2.4 [For the authoring tool user interface] Make it easier to see and hear the interface. [Techniques] |
Note: While the success criteria for this guideline are based on the capabilities of the platforms (e.g., operating systems, user agents, GUI toolkits) listed in the conformance profile, additional configuration settings may be provided. |
|||
A.3.1 [For the authoring tool user interface] Ensure that all functionality is available from a keyboard. [Techniques] |
Note 1: Web-based authoring tool user interface functionality may rely on the keyboard navigation functions of the user agent listed in the conformance profile to satisfy some of these success criteria. Note 2: This guideline should not discourage the support of other input methods (such as a mouse) in addition to keyboard operation. Also see Guideline A.3.1 when choosing keystrokes. |
|||
A.3.2 [For the authoring tool user interface] Enable time-independent interaction. [Techniques] |
|
|||
A.3.3 [For the authoring tool user interface] Ensure that authors can avoid flashing that could cause seizures. [Techniques] |
|
|||
A.3.6 [For the authoring tool user interface] Manage preference settings. [Techniques] |
|
|||
A.4.1 Make text content readable and understandable. |
|
|||
A.4.2 [For the authoring tool user interface] Make functionality predictable. [Techniques] |
|
|||
A.4.3 [For the authoring tool user interface] Help users avoid and correct mistakes. [Techniques] |
Note 1: Web-based authoring tool user interface functionality may rely on the "undo" function of the user agent listed in the conformance profile to perform the undo function for some editing actions that do not involve server communication (e.g., typing in a text area). Note 2: It is acceptable to collect text entry actions (e.g., typed words, a series of backspaces) into a single reversible authoring action. |
|||
B.1.1 Support Web content technologies that enable the creation of content that is accessible. [Techniques] |
Applicability Note: This guideline only applies when benchmarked technologies are available for authoring the particular type of content required (e.g., text, images, synchronized media). |
|||
B.1.3 Ensure that automatically generated content is accessible. [Techniques] |
Applicability Note 1: This guidelines does apply to any accessibility problems that informed authorshave specifically allowed (e.g., by setting less strict preferences) (see Guideline B.3.3 for more on informing the author). Applicability Note 2: This guideline does not apply when authors have caused the accessibility problem(s) (e.g., by ignoring prompts for accessibility information, providing faulty information, etc.). |
|||
B.2.1 Prompt authors to create accessible content. [Techniques] |
|
|||
B.2.2 Assist authors in checking for accessibility problems. [Techniques] |
Note: While automated checking or more advanced implementations of semi-automated checking may improve the authoring experience, these are not required to meet the success criteria for this guideline. Applicability Note: This guideline does not apply if the authoring tool controls the authoring process to an extent that it is not possible for authors to introduce accessibility problems. |
|||
B.2.3 Assist authors in repairing accessibility problems. [Techniques] |
Note: While automated repairing or more advanced implementations of semi-automated repairing may improve the authoring experience, these are not required to meet the success criteria for this guideline. Applicability Note: This guideline does not apply if the authoring tool controls the authoring process to an extent that it is not possible for authors to introduce accessibility problems. |
|||
B.2.4 Assist authors to manage, edit, and reuse equivalent alternatives for non-text objects. [Techniques] |
Note: Equivalent alternatives should not be automatically generated from unreliable sources (e.g., file names should not be used as text alternatives). |
|||
B.2.5 Assist authors with accessible templates and other pre-authored content. [Techniques] |
Note: Templates may be complicated to check for accessibility due to their inherent incompleteness. The accessibility status of templates is instead measured by the accessibility of content created through their proper use. |
|||
B.3.1. Ensure that accessible authoring actions are given prominence. [Techniques] |
|
|||
B.3.4. Ensure that features of the authoring tool supporting the production of accessible content are documented. [Techniques] |
|