W3C

Appendix E. Checklist (for Authoring Tool Accessibility Guidelines 2.0)

Editors:
Jan Richards, ATRC, University of Toronto
Roberto Scano, IWA/HWG

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.

Applicability Notes:

For PART A: Make the authoring tool user interface accessible:

  1. Scope of authoring tool user interface: The Part A success criteria apply to all aspects of the authoring tool user interface that are under the control of the authoring tool developer. This includes views of the web content being edited, and features that are independent of the content being edited, such as menus, button bars, status bars, user preferences, documentation, etc.
  2. Reflected web content accessibility problems: The authoring tool is responsible for ensuring that editing views display the web content being edited in a way that is accessible to authors with disabilities (e.g., ensuring that a text alternative in the content can be programmatically determined). However, where an authoring tool user interface accessibility problem is caused directly by a web content accessibility problem in the content being edited (e.g., if an image in the content lacks a label), then this would not be considered a deficiency in the accessibility of the authoring tool user interface.
  3. User agent features: Web-based authoring tools may rely on user agent features (e.g., keyboard navigation, find functions, display preferences, undo features, etc.) to satisfy success criteria. If a conformance claim is made, the claim cites the user agent.
  4. Features for meeting Part A must be accessible: The Part A success criteria apply to the entire authoring tool user interface, including any features added to meet the success criteria in Part A (e.g., documentation, search functions, etc.). The only exemption is for preview features, as long as they meet Guideline A.3.7. Previews are treated differently than editing views because all authors, including those with disabilities, benefit when preview features accurately reflect the actual functionality of user agents.

For PART B: Support the production of accessible content :

  1. Author availability: Any Part B success criteria that refer to authors only apply during authoring sessions.
  2. Applicability after the end of an authoring session: For author-generated content, the requirements of Part B only apply during authoring sessions. For example, if the author includes a third-party feed in their web content, the authoring tool is not required to provide checking for web content accessibility problems in that feed after the end of the authoring session. In contrast, for automatically-generated content, Part B continues to apply after the end of the authoring session. For example, if the site-wide templates of a content management system are updated, these would be required to meet the accessibility requirements for automatically-generated content.
  3. Authoring systems: As per the ATAG 2.0 definition of authoring tool, several software tools (identified in any conformance claim) can be used in conjunction to meet the requirements of Part B. (e.g., an authoring tool could make use of a third-party software accessibility checking and repair tool).
  4. Features for meeting Part B must be accessible: The Part A success criteria apply to the entire authoring tool user interface, including any features added to meet the success criteria in Part B (e.g., checking tools, repair tools, tutorials, documentation, etc.).
  5. Multiple author roles: Some authoring tool include multiple author roles, each with different views and content editing permissions (e.g., a content management system may separate the roles of designers, content authors, and quality assurers). In these cases, the Part B success criteria apply to the authoring tool as a whole, not to the view provided to any particular author role.

Guidelines and Success Criteria

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.

Level A Success Criteria

GuidelineSuccess CriteriaYesNoN/A
A.1.1 [For the authoring tool user interface] Ensure that web-based functionality is accessible.      
A.1.2 [For the authoring tool user interface] Ensure that non-web-based functionality is accessible.      
A.2.1 [For the authoring tool user interface] Make alternative content available to the author.      
A.2.2 [For the authoring tool user interface] Editing view presentation can be programmatically determined.      
A.2.3: Ensure the independence of the authors' display preferences.      
A.3.1 [For the authoring tool user interface] Provide keyboard access to authoring features.
  • A.3.1.1 Keyboard Access (Minimum): All functionality of the authoring tool is operable through a keyboard interface, except where editing web content properties that encode continuous input.
    Note 1:
    This exception relates to the nature of web content, not the usual input technique. For example, setting the path of a freehand curve is exempt, while setting the endpoints of a straight line is not.
    Note 2:
    This should not be interpreted as discouraging mouse input or other input methods in addition to the keyboard interface.
  • A.3.1.2 No Content Keyboard Traps: Keyboard traps are prevented as follows:
    (a) In the Authoring Tool User Interface: If keyboard focus can be moved to a component using the keyboard, then focus can be moved away from that component using standard keyboard navigation commands (e.g., TAB key); and
    (b) In Editing Views that Render Web Content: If an editing view renders web content (e.g., WYSIWYG view), then a documented keyboard command is provided that will always restore keyboard focus to a known location (e.g., the menus).
     
A.3.2 [For the authoring tool user interface] Provide authors with enough time.
  • A.3.2.1 Data Saved (Minimum): If the authoring tool includes authoring session time limits, then the authoring tool saves all submitted content edits made by authors.
  • A.3.2.2 Timing Adjustable: If a time limit is set by the authoring tool, then at least one of the following is true:
    (a) Turn Off: Authors are allowed to turn off the time limit before encountering it; or
    (b) Adjust:
    Authors are allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or

    (c) Extend:
    Authors are warned before time expires and given at least 20 seconds to extend the time limit with a simple action (e.g., "press the space bar"), and authors are allowed to extend the time limit at least ten times; or

    (d) Real-time Exception: The time limit is a required part of a real-time event (e.g., a collaborative authoring system), and no alternative to the time limit is possible; or
    (e) Essential Exception: The time limit is essential and extending it would invalidate the activity; or
    (f) 20 Hour Exception:
    The time limit is longer than 20 hours.
  • A.3.2.3 Static Pointer Targets: User interface components that accept pointer input are either stationary or authors can pause the movement.
     
A.3.3 [For the authoring tool user interface] Help authors avoid flashing that could cause seizures.
  • A.3.3.1 Static View Option: Rendering of time-based content (e.g., animations) in editing views can be turned off.
     
A.3.4 [For the authoring tool user interface] Enhance navigation and editing via content structure.      
A.3.7 [For the authoring tool user interface] Ensure that previews are as accessible as existing user agents.
  • A.3.7.1 Return Mechanism: If a preview is provided, then authors can return from the preview using only keyboard commands.
  • A.3.7.2 Preview: If a preview is provided, then at least one of the following is true:
    (a) Third-Party User Agent:
    The preview makes use of an existing third-party user agent; or

    (b) UAAG (Level A): The preview conforms to the User Agent Accessibility Guidelines Level A [UAAG].
     
A.4.1 [For the authoring tool user interface] Help users avoid and correct mistakes.
  • A.4.1.1 Undo Content Changes: Authoring actions are either reversible by an "undo" function or include a warning to the authors that the action is irreversible.
    Note 1: It is acceptable to collect a series of text entry actions (e.g., typed words, a series of backspaces) into a single reversible authoring action.
    Note 2: It is acceptable for certain committing actions (e.g., "save", "publish") to make all previous authoring actions irreversible.
  • A.4.1.2 Undo Setting Changes: Actions that modify authoring tool settings are either reversible or include a warning to authors that the action is irreversible.
     
A.4.2 [For the authoring tool user interface] Document the user interface including all accessibility features.
  • A.4.2.1 Document Accessibility Features: All features that are specifically required to meet Part A of this document (e.g. keyboard shortcuts, text search, etc.) are documented.
     
B.1.1 Support web content technologies that enable the creation of content that is accessible.      
B.1.2 Ensure that the authoring tool preserves accessibility information.      
B.1.3 Ensure that automatically generated content is accessible.      
B.2.1 Guide authors to create accessible content.      
B.2.2 Assist authors in checking for accessibility problems.      
B.2.3 Assist authors in repairing accessibility problems.      
B.2.4 Assist authors with managing alternative content for non-text content.      
B.2.5 Assist authors with accessible templates and other pre-authored content.
  • B.2.5.1 Templates Accessible (WCAG Level A): If the authoring tool automatically selects templates or pre-authored content, then the selections conform to WCAG 2.0 Level A when used.
    Note: Templates may not pass accessibility checks due to their inherent incompleteness. The accessibility status of a template should instead be measured by the accessibility of completed web content (in the final web content technology) created when the template is used properly.
  • B.2.5.2 Provide Accessible Templates: If the authoring tool provides templates, then there are accessible template options for a range of template uses.
     
B.3.1 Ensure that accessible authoring actions are given prominence.      
B.3.2 Ensure that features of the authoring tool supporting the production of accessible content are available.      
B.3.3 Ensure that features of the authoring tool supporting the production of accessible content are documented.      
B.3.4 Ensure that any authoring practices demonstrated in documentation are accessible.      

Level AA Success Criteria

GuidelineSuccess CriteriaYesNoN/A
A.1.1 [For the authoring tool user interface] Ensure that web-based functionality is accessible.      
A.3.1 [For the authoring tool user interface] Provide keyboard access to authoring features.
  • A.3.1.3 Keyboard Shortcuts: Keyboard shortcuts are provided.
     
A.3.5 [For the authoring tool user interface] Provide text search of the content.
  • A.3.5.1 Text Search: Authors can perform text searches of web content as follows:
    (a) Search All Editable: Any information that is text and that the authoring tool can modify is searchable, including: text content, text alternatives for non-text content, metadata, markup elements and attributes; and
    Note: If the current editing view is not able to display the results of a search, then the authoring tool may provide a mechanism to switch to a different editing view to display the results.
    (b) Bi-Directional:
    The search can be made forwards or backwards; and

    (c) Case Sensitive:
    The search can be in both case sensitive and case insensitive modes.
     
A.3.6 [For the authoring tool user interface] Manage preference settings.      
A.4.1 [For the authoring tool user interface] Help users avoid and correct mistakes.
  • A.4.1.3 Undo is Reversible: Authors can immediately reverse the most recent "undo" action(s).
     
A.4.2 [For the authoring tool user interface] Document the user interface including all accessibility features.      
B.1.1 Support web content technologies that enable the creation of content that is accessible.      
B.1.2 Ensure that the authoring tool preserves accessibility information.      
B.1.3 Ensure that automatically generated content is accessible.      
B.2.2 Assist authors in checking for accessibility problems.      
B.2.3 Assist authors in repairing accessibility problems.      
B.2.4 Assist authors with managing alternative content for non-text content.      
B.2.5 Assist authors with accessible templates and other pre-authored content.
  • B.2.5.3 Templates Accessible (WCAG Level AA): If the authoring tool automatically selects templates or pre-authored content, then the selections conform to WCAG 2.0 Level AA when used.
    Note: Templates may not pass accessibility checks due to their inherent incompleteness. The accessibility status of a template should instead be measured by the accessibility of completed web content (in the final web content technology) created when the template is used properly.
  • B.2.5.4 Template Selection Mechanism: If authors are provided with a template selection mechanism, then both of the following are true:
    (a) Indicate:
    The selection mechanism indicates the accessibility status of templates (if known); and

    (b) Prominence:
    Any accessible template options are at least as prominent as other template options.
  • B.2.5.5 New Templates: If authors can use the authoring tool to create new templates for use by a template selection mechanism, they have the option to record the accessibility status of the new templates.
  • B.2.5.6 Pre-Authored Content Selection Mechanism: If authors are provided with a selection mechanism for pre-authored content other than templates (e.g., clip art gallery, widget repository, design themes), then both of the following are true:
    (a) Indicate: The selection mechanism indicates the accessibility status of the pre-authored content (if known); and
    (b) Prominence: Any accessible options are at least as prominent as other pre-authored content options.
     
B.3.1 Ensure that accessible authoring actions are given prominence.      
B.3.2 Ensure that features of the authoring tool supporting the production of accessible content are available.      
B.3.4 Ensure that any authoring practices demonstrated in documentation are accessible.      

Level AAA Success Criteria

GuidelineSuccess CriteriaYesNoN/A
A.1.1 [For the authoring tool user interface] Ensure that web-based functionality is accessible.      
A.2.2 [For the authoring tool user interface] Editing view presentation can be programmatically determined.      
A.3.1 [For the authoring tool user interface] Provide keyboard access to authoring features.      
A.3.2 [For the authoring tool user interface] Provide authors with enough time.
  • A.3.2.4 Content Edits Saved (Extended): The authoring tool can be set to save all content edits made by authors.
     
A.3.6 [For the authoring tool user interface] Manage preference settings.      
B.1.1 Support web content technologies that enable the creation of content that is accessible.      
B.1.3 Ensure that automatically generated content is accessible.      
B.2.2 Assist authors in checking for accessibility problems.      
B.2.3 Assist authors in repairing accessibility problems.      
B.2.5 Assist authors with accessible templates and other pre-authored content.
  • B.2.5.7 Templates in Repository: If the authoring tool provides a repository of templates, then each of the templates has a recorded accessibility status.
  • B.2.5.8 Pre-Authored Content in Repository: If the authoring tool provides a repository of pre-authored content, then each of the content objects has a recorded accessibility status.
  • B.2.5.9 Templates Accessible (WCAG Level AAA): If the authoring tool automatically selects templates or pre-authored content, then the selections conform to WCAG 2.0 Level AAA when used.
    Note: Templates may not pass accessibility checks due to their inherent incompleteness. The accessibility status of a template should instead be measured by the accessibility of completed web content (in the final web content technology) created when the template is used properly.
     
B.3.1 Ensure that accessible authoring actions are given prominence.      
B.3.3 Ensure that features of the authoring tool supporting the production of accessible content are documented.
  • B.3.3.2 Accessible Authoring Tutorial: A tutorial on an accessible authoring process that is specific to the authoring tool is provided.
     
B.3.4 Ensure that any authoring practices demonstrated in documentation are accessible.