(Draft) ATAG 2.0 Implementation Report

A.1.1.1 Web-Based Accessible (WCAG):

• 1.1.1(A): Y

• 1.2.1(A): Y-Not used
• 1.2.2(A): Y-Not used
• 1.2.3(A): Y-Not used
• 1.3.1(A): Y
• 1.3.2(A): Y
• 1.3.3(A):Y
• 1.4.1(A):Y
• 1.4.2(A): Y-Not used
• 2.1.1(A): N due to Spelling Checker (note: alt+F10 is a vital keystroke)

• 2.1.2(A):Y
• 2.2.1(A): Y-Not used
• 2.2.2(A):Y-Not used
• 2.3.1(A): Y
• 2.3.2(A): Y
• 2.4.1(A): Y (esp. in button bars)
• 2.4.2(A): NA
• 2.4.3(A): Y
• 2.4.4(A): Y
• 3.1.1(A): Y
• 3.2.1(A): Y
• 3.2.2(A): Y
• 3.3.1(A): Y-Not used
• 3.3.2(A): Y
• 4.1.1(A):Y
• 4.1.2(A): Y

• 1.1.1(A): Y

• 1.2.1(A): Y-Not used
• 1.2.2(A): Y-Not used
• 1.2.3(A): Y-Not used
• 1.2.4(AA): Y-Not used
• 1.2.5(AA): Y-Not used
• 1.3.1(A): Y
• 1.3.2(A): Y
• 1.3.3(A):Y
• 1.4.1(A):Y
• 1.4.2(A): Y-Not used
• 1.4.3(AA):Y
• 1.4.4(AA):Y
• 1.4.5(AA):Y
• 2.1.1(A): N due to Spelling Checker (note: alt+F10 is a vital keystroke)

• 2.1.2(A):Y
• 2.2.1(A): Y-Not used
• 2.2.2(A):Y-Not used
• 2.3.1(A): Y
• 2.3.2(A): Y
• 2.4.1(A): Y (esp. in button bars)
• 2.4.2(A): NA
• 2.4.3(A): Y
• 2.4.4(A): Y
• 2.4.5(AA): NA
• 2.4.6(AA): Y
• 2.4.7(AA): Y
• 3.1.1(A): Y
• 3.1.2(AA): Y
• 3.2.1(A): Y
• 3.2.2(A): Y
• 3.2.3(AA): Y
• 3.2.4(AA): Y
• 3.3.1(A): Y-Not used
• 3.3.2(A): Y
• 3.3.3(AA): Y-Not used
• 3.3.4(AA): Y-Not used
• 4.1.1(A):Y
• 4.1.2(A): Y

• 1.1.1(A): Y

• 1.2.1(A): Y-Not used
• 1.2.2(A): Y-Not used
• 1.2.3(A): Y-Not used
• 1.2.4(AA): Y-Not used
• 1.2.5(AA): Y-Not used
• 1.2.6(AAA): Y-Not used
• 1.2.7(AAA): Y-Not used
• 1.2.8(AAA): Y-Not used
• 1.2.9(AAA): Y-Not used
• 1.3.1(A): Y
• 1.3.2(A): Y
• 1.3.3(A):Y
• 1.4.1(A):Y
• 1.4.2(A): Y-Not used
• 1.4.3(AA):Y
• 1.4.4(AA):Y
• 1.4.5(AA):Y
• 1.4.6(AAA): Y
• 1.4.7(AAA): Y-Not used
• 1.4.8(AAA): @@@
• 1.4.9(AAA): Y-Not used
• 2.1.1(A): N due to Spelling Checker (note: alt+F10 is a vital keystroke)

• 2.1.2(A):Y
• 2.1.3(AAA)::Y
• 2.2.1(A): Y-Not used
• 2.2.2(A):Y-Not used
• 2.2.3(AAA): Y
• 2.2.4(AAA): Y-Not used
• 2.2.5(AAA): Y-Not used
• 2.3.1(A): Y
• 2.3.2(A): Y
• 2.4.1(A): Y (esp. in button bars)
• 2.4.2(A): NA
• 2.4.3(A): Y
• 2.4.4(A): Y
• 2.4.5(AA): NA
• 2.4.6(AA): Y
• 2.4.7(AA): Y
• 2.4.8(AAA): NA
• 2.4.9(AAA): Y
• 2.4.10(AAA): NA
• 3.1.1(A): Y
• 3.1.2(AA): Y
• 3.1.3(AAA): @@@
• 3.1.4(AAA): @@@
• 3.1.5(AAA): @@@
• 3.1.6(AAA): @@@
• 3.2.1(A): Y
• 3.2.2(A): Y
• 3.2.3(AA): Y
• 3.2.4(AA): Y
• 3.2.5(AAA): Y
• 3.3.1(A): Y-Not used
• 3.3.2(A): Y
• 3.3.3(AA): Y-Not used
• 3.3.4(AA): Y-Not used
• 3.3.5(AAA): N
• 3.3.6(AAA):Y
• 4.1.1(A):Y
• 4.1.2(A): Y

A.1.2.1 Accessibility Guidelines:

• Note: The (optional) explanation of conformance claim results should record the user interface accessibility guidelines that were followed.

A.1.2.2 Platform Accessibility Services:

• Note: The (optional) explanation of conformance claim results should record the platform accessibility service(s) that were implemented.

A.2.1.1 Text Alternatives for Rendered Non-Text Content:

If an editing-view renders non-text content, then any programmatically associated text alternatives for the non-text content can be programmatically determined. (Level A)

A.2.1.2 Alternatives for Rendered Time-Based Media:

If an editing-view renders time-based media, then at least one of the following is true: (Level A)

• (a) Option to Render: The authoring tool provides the option to render alternatives for the time-based media; or
• (b) User Agent Option: Authors have the option to preview the time-based media in a user agent that is able to render the alternatives.

A.2.2.1 Editing-View Status Indicators:

If an editing-view adds status indicators to the content being edited, then the status messages being indicated can be programmatically determined. (Level A)

• Note: Status indicators may indicate errors (e.g., spelling errors), tracked changes, hidden elements, or other information.

A.2.2.2 Access to Rendered Text Properties:

If an editing-view renders any text formatting properties that authors can also edit using the editing-view, then the properties can be programmatically determined. (Level AA)

A.3.1.1 Keyboard Access (Minimum):

All functionality of the authoring tool is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)

• Note 1: Keyboard interfaces are programmatic services provided by many platforms that allow operation in a device independent manner. This success criterion does not imply the presence of a hardware keyboard.
• Note 2: The path exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input, but the underlying function (text input) does not. The path exception encompasses other input variables that are continuously sampled from pointing devices, including pressure, speed, and angle.
• Note 3: This success criterion does not forbid and should not discourage other input methods (e.g., mouse, touch) in addition to keyboard operation.

A.3.1.2 No Keyboard Traps:

If keyboard focus can be moved to a component using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, authors are advised of the method for moving focus away. (Level A)

A.3.1.3 Efficient Keyboard Access:

The authoring tool user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access. (Level AA)

A.3.1.4 Keyboard Access (Enhanced):

All functionality of the authoring tool is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA)

A.3.1.5 Customize Keyboard Access:

If the authoring tool includes keyboard commands, then those keyboard commands can be customized. (Level AAA)

A.3.1.6 Present Keyboard Commands:

If the authoring tool includes keyboard commands,

A.3.2.1 Auto-Save (Minimum):

If the authoring tool includes authoring session time limits, then the authoring tool can be set to automatically save web content edits made using the authoring tool before the session time limits are reached. (Level A)

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: (Level A)

• (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 Input Components:

If authoring tool user interface components accept input and move, then authors can pause the movement. (Level A)

A.3.2.4 Content Edits Saved (Extended):

The authoring tool can be set to automatically save web content edits made using the authoring tool. (Level AAA)

A.3.3.1 Static View Option:

If the authoring tool contains editing-views that render visual time-based content, then those editing-views can be paused and can be set to not play automatically. (Level A)

A.3.4.1 Navigate By Structure:

If editing-views expose the markup elements in the web content being edited, then the markup elements (e.g., source code, content renderings) are selectable and navigation mechanisms are provided to move the selection focus between elements. (Level AA)

A.3.4.2 Navigate by Programmatic Relationships:

If editing-views allow editing of programmatic relationships within web content, then mechanisms are provided that support navigation between the related content. (Level AAA)

• Note: Depending on the web content technology and the nature of the authoring tool, relationships may include, but are not limited to, element nesting, headings, labeling, programmatic definitions, and ID relationships.

A.3.5.1 Text Search:

If the authoring tool provides an editing-view of text-based content, then the editing-view enables text search, such that all of the following are true: (Level AA)

• (a) All Editable Text: Any text content that is editable by the editing-view is searchable (including alternative content); and
• (b) Match: Matching results can be made visible to authors and given focus; and
• (c) No Match: Authors are informed when no results are found; and
• (d) Two-way: The search can be made forwards or backwards.

A.3.6.1 Independence of Display:

If the authoring tool includes display settings for editing-views, then the authoring tool allows authors to adjust these settings without modifying the web content being edited. (Level A)

A.3.6.2 Save Settings:

If the authoring tool includes display and/or control settings, then these settings can be saved between authoring sessions. (Level AA)

A.3.6.3 Apply Platform Settings:

The authoring tool respects changes in platform display and control settings, unless authors select more specific display and control settings using the authoring tool. (Level AA)

A.3.6.4 Multiple Sets:

If the authoring tool includes display and/or control settings, then the authoring tool provides the option of saving and reloading multiple configurations of settings. (Level AAA)

A.3.7.1 Preview (Minimum):

If a preview is provided, then at least one of the following is true: (Level A)

• (a) In-Market User Agent: The preview renders content using a user agent that is in-market; or
• (b) UAAG (Level A): The preview conforms to the User Agent Accessibility Guidelines 1.0 Level A [UAAG].

A.3.7.2 Preview (Enhanced):

If a preview is provided, then authors can specify which user agent performs the preview. (Level AAA)

A.4.1.1 Content Changes Reversible (Minimum):

All authoring actions are either reversible or the authoring tool requires author confirmation to proceed. (Level A)

A.4.1.2 Settings Change Confirmation:

If the authoring tool provides mechanisms for changing authoring tool user interface settings, then those mechanisms can reverse the setting changes, or the authoring tool requires author confirmation to proceed. (Level A)

A.4.1.3 Content Changes Reversible (Enhanced):

Authors can sequentially reverse a series of reversible authoring actions. (Level AAA)

• Note: It is acceptable to clear the authoring action history at the end of authoring sessions.

A.4.2.1 Describe Accessibility Features:

For each authoring tool feature that is used to meet Part A of ATAG 2.0, at least one of the following is true: (Level A)

• (a) Described in the documentation: Use of the feature is explained in the authoring tool's documentation; or
• (b) Described in the interface: Use of the feature is explained in the authoring tool user interface; or
• (c) Platform service: The feature is a service provided by an underlying platform; or
• (d) Not used by authors: The feature is not used directly by authors (e.g., passing information to a platform accessibility service).

• Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2.

A.4.2.2 Document All Features:

For each authoring tool feature, at least one of the following is true: (Level AA)

• (a) Described in the documentation: Use of the feature is explained in the authoring tool's documentation; or
• (b) Described in the interface: Use of the feature is explained in the authoring tool user interface; or
• (c) Platform service: The feature is a service provided by an underlying platform; or
• (d) Not used by authors: The feature is not used directly by authors (e.g., passing information to a platform accessibility service).

• Note: The accessibility of the documentation is covered by Guideline A.1.1 and Guideline A.1.2.

B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG):

If the authoring tool provides the functionality for automatically generating web content after the end of an authoring session, authors can specify that the content be accessible web content (WCAG). (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

• Note: This success criterion applies only to automatic processes specified by the authoring tool developer. It does not apply when author actions prevent generation of accessible web content (WCAG).

B.1.1.2 Content Auto-Generation During Authoring Sessions (WCAG):

• (a) Accessible: The content is accessible web content (WCAG) without author input; or
• (b) Prompting: During the automatic generation process, authors are prompted for any required accessibility information (WCAG); or
• (c) Automatic Checking: After the automatic generation process, accessibility checking is automatically performed; or
• (d) Checking Suggested: After the automatic generation process, the authoring tool prompts authors to perform accessibility checking.

• Note 1: Automatic generation includes automatically selecting templates for authors.
• Note 2: This success criterion applies only to automatic processes specified by the authoring tool developer. It does not apply when author actions prevent generation of accessible web content (WCAG).

B.1.2.1 Restructuring and Recoding Transformations (WCAG):

If the authoring tool provides restructuring transformations or re-coding transformations, and if equivalent mechanisms exist in the web content technology of the output, then at least one of the following is true: (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

• (a) Preserve: Accessibility information (WCAG) is preserved in the output; or
• (b) Warning: Authors have the default option to be warned that accessibility information (WCAG) may be lost (e.g., when saving a vector graphic into a raster image format); or
• (c) Automatic Checking: After the transformation, accessibility checking is automatically performed; or
• (d) Checking Suggested: After the transformation, the authoring tool prompts authors to perform accessibility checking.

• Note 1: For text alternatives for non-text content, see Success Criterion B.1.2.4.
• Note 2: This success criteria only applies when the output technology is "included" for conformance.

B.1.2.2 Copy-Paste Inside Authoring Tool (WCAG):

If the authoring tool supports copy and paste of structured content, then any accessibility information (WCAG) in the copied content is preserved when the authoring tool is both the source and destination of the copy-paste. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

B.1.2.3 Optimizations Preserve Accessibility:

If the authoring tool provides optimizing web content transformations, then any accessibility information (WCAG) in the input is preserved in the output. (Level A).

B.1.2.4 Text Alternatives for Non-Text Content are Preserved:

If the authoring tool provides web content transformations that preserve non-text content in the output, then any text alternatives for that non-text content are also preserved, if equivalent mechanisms exist in the web content technology of the output. (Level A).

• Note: This success criteria only applies when the output technology is "included" for conformance.

B.2.1.1 Accessible Content Possible (WCAG):

If the authoring tool places restrictions on the web content that authors can specify, then those restrictions do not prevent WCAG 2.0 success criteria from being met. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

B.2.2.1 Accessible Option Prominence (WCAG):

If authors are provided with a choice of authoring actions for achieving the same authoring outcome (e.g., styling text), then options that will result in accessible web content (WCAG) are at least as prominent as options that will not. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

B.2.2.2 Setting Accessibility Properties (WCAG):

If the authoring tool provides mechanisms to set web content properties (e.g., attribute values), then mechanisms are also provided to set web content properties related to accessibility information (WCAG). (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

• Note: Success Criterion B.4.1.4 addresses the prominence of the mechanisms.

B.2.3.1 Alternative Content is Editable (WCAG):

If the authoring tool provides functionality for adding non-text content, then authors are able to modify programmatically associated text alternatives for non-text content. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

B.2.3.2 Conditions on Automated Suggestions:

If the authoring tool automatically suggests text alternatives for non-text content during the authoring session, then the text alternatives may only be suggested under the following conditions: (Level A)

• (a) Author Control: Authors have the opportunity to accept, modify, or reject the suggested text alternatives prior to insertion; and
• (b) Relevant Sources: The suggested text alternatives are only derived from sources designed to fulfill the same purpose (e.g., suggesting the value of an image's "description" metadata field as a long description).

B.2.3.3 Let User Agents Repair:

If the authoring tool provides automatic repair of text alternatives for non-text content after the end of an authoring session, then the authoring tool avoids using text values that would also be available to user agents. (Level A)

• Note: Examples of text values that are also available to user agents, and should be avoided, include the filename, the file format, and generic phrases (e.g. "image").

B.2.3.4 Save for Reuse:

If the authoring tool provides the functionality for adding non-text content,

• (a) Save and Suggest: The text alternatives are automatically saved and suggested by the authoring tool, if the same non-text content is reused; and
• (b) Edit Option: The author has the option to edit or delete the saved text alternatives.

B.2.4.1 Accessible Template Options (WCAG):

If the authoring tool provides templates, then there are accessible template (WCAG) options for a range of template uses. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

B.2.4.2 Identify Template Accessibility (Minimum):

If the authoring tool includes a template selection mechanism and provides any non-accessible template (WCAG) options, then the templates are provided such that the template selection mechanism can display distinctions between the accessible and non-accessible options. (Level AA)

• Note: The distinction can involve providing information for the accessible templates, the non-accessible templates or both.

B.2.4.3 Author-Created Templates:

If the authoring tool includes a template selection mechanism and allows authors to create new non-accessible templates (WCAG), then authors can enable the template selection mechanism to display distinctions between accessible and non-accessible templates that they create. (Level AA)

• Note: The distinction can involve providing information for the accessible templates (WCAG), the non-accessible templates or both.

B.2.4.4 Identify Template Accessibility (Enhanced):

If the authoring tool provides any non-accessible templates (WCAG) options and does not include a template selection mechanism, then the non-accessible templates include accessibility warnings within the templates. (Level AAA)

B.2.5.1 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: (Level AA)

• (a) Indicate: The selection mechanism indicates the accessibility status of the pre-authored content (if known); and
• (b) Prominence: Any accessible (WCAG) options are at least as prominent as other pre-authored content options.

B.2.5.2 Pre-Authored Content Accessibility Status:

If the authoring tool provides a repository of pre-authored content, then each of the content objects has a recorded accessibility status. (Level AAA)

B.3.1.1 Checking Assistance (WCAG):

If the authoring tool provides authors with the ability to add or modify web content in such a way that a WCAG 2.0 success criterion can be violated, then accessibility checking for that success criterion is provided (e.g., an HTML authoring tool that inserts images should check for alternative text; a video authoring tool with the ability to edit text tracks should check for captions). (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

• Note: Automated and semi-automated checking is possible (and encouraged) for many types of web content accessibility problems (WCAG). However, manual checking is the minimum requirement to meet this success criterion. In manual checking, the authoring tool provides authors with instructions for detecting problems, which authors must carry out by themselves. For more information on checking, see Implementing ATAG 2.0 - Appendix B: Levels of Checking Automation.

B.3.1.2 Help Authors Decide:

If the authoring tool provides checks that require authors to decide whether a potential web content accessibility problem (WCAG) is correctly identified (i.e., manual checking and semi-automated checking), then instructions are provided from the check that describe how to decide. (Level A)

B.3.1.3 Help Authors Locate:

If the authoring tool provides checks that require authors to decide whether a potential web content accessibility problem (WCAG) is correctly identified (i.e., manual checking and semi-automated checking), then the relevant content is identified to the authors. (Level A)

• Note: Depending on the nature of the editing-view and the scope of the potential web content accessibility problem (WCAG), identification might involve highlighting elements or renderings of elements, displaying line numbers, or providing instructions.

B.3.1.4 Status Report:

If the authoring tool provides checks, then authors can receive an accessibility status report based on the results of the accessibility checks. (Level AA)

• Note: The format of the accessibility status report is not specified and they might include a listing of problems detected or a WCAG 2.0 conformance level, etc..

B.3.1.5 Programmatic Association of Results:

If the authoring tool provides checks, then the authoring tool can programmatically associate accessibility checking results with the web content that was checked. (Level AA)

B.3.2.1 Repair Assistance (WCAG):

If checking (see Success Criterion B.3.1.1) can detect that a WCAG 2.0 success criterion is not met, then repair suggestion(s) are provided: (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

• Note: Automated and semi-automated repair is possible (and encouraged) for many types of web content accessibility problems (WCAG). However, manual repair is the minimum requirement to meet this success criterion. In manual repair, the authoring tool provides authors with instructions for repairing problems, which authors must carry out by themselves. For more information on repair, see Implementing ATAG 2.0 - Appendix C: Levels of Repair Automation.

B.4.1.1 Features Active by Default:

All accessible content support features are turned on by default. (Level A)

B.4.1.2 Option to Reactivate Features:

If authors can turn off an accessible content support feature, then they can turn the feature back on. (Level A)

B.4.1.3 Feature Availability Information:

If the authoring tool supports production of any web content technologies for publishing for which the authoring tool does not provide support for the production of accessible web content (WCAG), then this is documented. (Level AA)

• Note: This success criterion concerns the presence or absence of support features, such as accessibility checkers, not any intrinsic property of web content technologies.

B.4.1.4 Feature Deactivation Warning:

If authors turn off an accessible content support feature, then the authoring tool informs them that this may increase the risk of content accessibility problems (WCAG). (Level AA)

B.4.1.5 Feature Prominence:

All accessible content support features are at least as prominent as features related to either invalid markup, syntax errors, spelling errors or grammar errors. (Level AA)

B.4.2.1 Model Practice (WCAG):

A range of examples in the documentation (e.g., markup, screen shots of WYSIWYG editing-views) demonstrate accessible authoring practices (WCAG). (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)

B.4.2.2 Feature Instructions:

Instructions for using any accessible content support features appear in the documentation. (Level A)

B.4.2.3 Tutorial:

The authoring tool provides a tutorial for an accessible authoring process that is specific to that authoring tool. (Level AAA)

B.4.2.4 Instruction Index:

The authoring tool documentation contains an index to the instructions for using any accessible content support features. (Level AAA)