Developer control: The Part A success criteria only apply to the authoring tool user interface as it is provided by the developer. They do not apply to any subsequent modifications by parties other than the authoring tool developer (e.g., user modifications of default settings, third-party plug-ins).

Accessibility of features provided to meet Part A: 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). The only exemption is for preview features,
as long as they meet the relevant success criteria in 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 functionality of user
agents that are actually in use by end users.

Unrecognizable content: When success criteria require authoring tools to treat web content according to semantic criteria, the success criteria do not apply when these semantics are missing (e.g., text that describes an image is only considered to be a text alternative when this role is encoded within markup).

For PART B: Support the production of accessible content:

Developer control: The Part B success criteria only apply to the authoring tool as it is provided by the developer. This does not include subsequent modifications by parties other than the authoring tool developer (e.g., third-party plug-ins, user-defined templates, user modifications of default settings).

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 tool).

Accessibility of features provided to meet Part B: The Part
A success criteria apply to the entire authoring tool user interface, including any features that must be present to meet the success criteria in Part B (e.g., checking tools, repair tools, tutorials, documentation).

Multiple authoring roles: Some authoring tools 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 authoring role. Accessible content support features should be made available to any authoring role where it would be useful.

Unrecognizable content: When success criteria require authoring tools to treat web content according to semantic criteria, the success criteria do not apply when these semantics are missing (e.g., text that describes an image is only considered to be a text alternative when this role is encoded within markup).

Guidelines and Success Criteria

Tools for Testing:

Web Content Accessibility Test Procedure: Procedure that is to be used whenever it is necessary to determine the accessibility of web content (e.g. in the authoring tool's own user interface or in the content produced by the tool).

The most complete test is a manual test following "How to Meet WCAG 2.0" (http://www.w3.org/WAI/WCAG20/quickref/)

@@(Semi-) Automated Web Content Accessibility Checker: Some may find it use a semi- or fully automated web content accessibility checker as part of this procedure. Free automated tools that accept URIs or pasted HTML code include:

WebAIM Wave

AChecker

etc.

@@Web Content Markup Examination Tool: These tools (e.g. Firebug) help testers discover and visualize the markup that gave rise to a particular onscreen rendering.

Platform Accessibility Service Test Procedure: Procedure that is to be used whenever it is necessary to determine whether information has been properly communicated to an Platform Accessibility Service (e.g. MSAA, IAccessible2 and UI Automation for Windows applications, AXAPI for Mac OS X applications, GNOME Accessibility Toolkit API for GNOME applications, Java Access for Java applications. @@For some platforms, semi-automated testing solutions may exist.

a complete file @@in the relevant web content technology (e.g. HTML) with no known accessibility problems to the given level.

@@the file should make use of as many WCAG techniques as feasible at the given level.

@@this file should include various types of non-text content (images) and time-based media with their required alternatives.

not needed if the tool does not import content or allow markup to be pasted in.

Comprehensive non-accessible test content (Level A, AA, AAA): Used to test checkers.@@The method for loading this content will depend on the nature of the authoring tool (e.g. opening a test file, pasting in content, authoring the content manually)

a complete file@@in the relevant web content technology (e.g. HTML) with at least one accessibility issue for each WCAG 2.0 SC at the given level.

@@this file should include various types of non-text content (images) and time-based media lacking their required alternatives.

not needed if the tool does not import content or allow markup to be pasted in.

Selection of separate pieces of content: To be used as needed to test various SCs.@@The method for loading this content will depend on the nature of the authoring tool (e.g. opening a test file, pasting in content, authoring the content manually)

List of Accessible Content Support Features:While testing the authoring tool against all of the following success criteria, compile a list of the authoring tool features that are relevant to each test (they do not necessarily have to pass) as well as whether the feature can be turned off, either directly from where it appears in the user interface (e.g., via a "Do not show this again" dialog) or from the authoring tool settings.

If the accessibility guideline (for the platform) used by the developer is known, this should be used to test the accessibility of the user interface. If the user interface has followed the guidelines, then select PASS, otherwise select FAIL.

If the accessibility guideline (for the platform) used by the developer is not known, choose the most relevant from this list of user interface accessibility guidelines for various platforms and use it to test the accessibility of the user interface. If you find instances where the user interface has not followed the guidelines, then select FAIL, otherwise select PASS.

Test 0001 Assertion: Any non-web-based components of the authoring tool user interface successfully communicate name and role with the platform accessibility services (accessibility APIs).[@@JR updated]

If the authoring tool is entirely web-based, then select SKIP.

For each user interface component in the authoring tool user interface:

A.2.1.2 Alternatives for Rendered Time-Based Media:

If an editing-viewrenders 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.

Test 0001 Assertion: Video or audio media in an editing view has an option to display captions or transcript OR an option to preview the media in user agent capable of rendering the captions or transcripts. [@@JR updated]

If the authoring tool does include editing views that render video or audio, then select
SKIP.

Check if the authoring tool allows the content being edited to be be previewed in a user agent (e.g. browser or media player) where the alternatives can be rendered OR
if the authoring tool can be set to render the alternatives itself. If not, select FAIL.

Check all of the editing-views for status indicators (often used to indicate errors (e.g., spelling errors), tracked changes, hidden elements, or other information.), possibly from a product feature list or trial and error.

If the authoring tool does not provide status indicators in any of its editing-views, select SKIP.

For each type of status indicator:

Open or author content that will trigger the status indicator (e.g. with spelling errors, add a hidden element, etc.), then examine the indicator with the Web Content Accessibility Test Procedure. If an indicator does not pass, then select FAIL

Check all of the editing-views for status indicators (often used to indicate errors (e.g., spelling errors), tracked changes, hidden elements, or other information.), possibly from a product feature list or trial and error.

If the authoring tool does not provide status indicators in any of its editing-views, select SKIP.

For each type of status indicator:

Open or author content that will trigger the status indicator (e.g. with spelling errors, add a hidden element, etc.), then examine the indicator with the Platform Accessibility Service Test Procedure to determine if the indicator (e.g. the validation error) has been communicated to the accessibility API. If an indicator does not pass, then select FAIL

A.2.2.2 Access to Rendered Text Properties:

Test 0001 Assertion: For web-based tools: Text formatting is passed through in the rendering. [@@JR updated]

If the editing view is non-web-based, then select SKIP.

Check all of the editing-views for text format rendering (i.e., when text being edited is rendered using the same text formatting properties that it will have when renedered by the user agent of end-users).

If the authoring tool does not text property rendering in any of its editing-views, select SKIP.

For each editing view that renders text formatting properties:

Open or author text content that includes text formatting (i.e., the text size, color, background, font, weight, etc. have been set).

Use a web content markup examination tool to examine how the text is actually presented in the editing view. If the text is presented in a way that blocks text formatting from being conveyed to the the browser (e.g. as images of text), then then select FAIL.

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.

Test 0001 Assertion:

Test 0001 Author: Tim Boland

@@

If the authoring tool does not support any form of keyboard interface, then select FAIL. @@(Note: If this is due to limitations of the platform, "Partial Comformance due to Platform Limitation" is still possible.)

Document presence of programmatic service allowing device-independent keystroke input for platform via which functionality of authoring tool will be accessed - if no such programmatic service exists for this platform, then SC fails (or is N/A?) for that authoring tool on that platform. Go to Step 10.

Open authoring tool on the selected platform and document (list) all functions of authoring tool (this could be from authoring tool documentation or author experience with the tool)

Of these functions, document functions where path-dependent input is required (document rationale for this aspect also) and exclude those functions from the list described in Step 2, to create a modified list of functions

For each function in the modified list from Step 3:

Check that the function works correctly according to specification/expectation by just using the programmatic service described in Step 1 and nothing else

Check that there is no time dependency required for any keystroke input for the programmatic service used in Step 5 in order to successfully complete the function from Step 5 (that is, if a time limit is exceeded, the function does not complete correctly).

If checks for both Steps 5 and 6 are successful for that function, then the SC for that function (on that platform) is TRUE; otherwise the SC for that function (on that platform) is FALSE

If for all functions checked from Steps 4 through 7 , the SC for that function is TRUE, then the SC is passed for that authoring tool (on that platform)

If for at least one function checked from Steps 4 through 7, the SC for that function is FALSE, then the SC fails for that authoring tool (on that platform)

Close authoring tool.

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)

Test 0001 Assertion:

Test 0001 Author: Tim Boland

@@

Step 0. Document specific platform via which authoring tool will be accessed. If a keyboard interface does not exist for this platform, this SC is N/A for this authoring tool; go to Step 7. Otherwise, go to Step 1.

Step 1. Document if keyboard focus is supported by authoring tool as a part of the keyboard interface. If keyboard focus is not supported, this SC is N/A for this authoring tool; go to Step 7. Otherwise, go to Step 2.

Step 2. Document all controls for a specific function supported by authoring tool. For each of these controls, document if there are explicit instructions given to you on how to move keyboard focus to and from that control. If there are no such controls, this SC is N/A for this authoring tool; go to Step 7. Otherwise, go to Step 3.

Step 3. (loop) For every function control (from Step 2) in the authoring tool, test the ability to move keyboard focus (from Step 1) to this function control by using the keyboard interface from Step 0. If keyboard focus can be moved to this function control as specified in the previous sentence (by following any instructions documented in Step 2 for this control), then place the control in Group A. Otherwise place the function control in Group B. If upon exiting the loop, there are no function controls in Group A (Group A is empty), then SC is N/A for this authoring tool on this platform; go to Step 7. Otherwise go to Step 2.

Step 4. (loop) For every function control in Group A, attempt to move keyboard focus from this function control by only using the keyboard interface from Step 0 (and by following any instructions documented for Step 2 for this control). If for any control, focus cannot be moved away from the control in the fashion from the previous sentence (focus is trapped), then stop; SC fails for this authoring tool on this platform; go to Step 7. If the previous condition does not apply for any function control in the loop for Group A (focus is not trapped), document the specific keystrokes/exit methods required for said movement for each function control in Group A. Go to Step 5.

Step 5. Document a list of "standard" or "common" exit methods for this authoring tool (or authoring tools in general).

Step 6. (loop) For every function control in Group A, check to ensure that any exit methods documented for that function control from Step 2 are covered in the list from Step 5. For any exit methods "outside" this list, check to determine if you are notified of the exit method needed prior to attempting to move keyboard focus from that function control, and if notified exit method works in moving keyboard focus from that control. If the preceding sentences in Step 6 are all true for all function controls in Group A, then this SC passes for this authoring tool on this platform. Otherwise, this SC fails for this authoring tool on this platform. Go to Step 7.

A.3.1.3 Efficient Keyboard Access:

Step 0. Determine if the platform on which the authoring tool is running supports a keyboard interface. If it does, then proceed to Step 1. If not, then skip to Step 8.

Step 1. Document all mechanisms of the user interface for the authoring tool under test (from authoring tool documentation or from experience). If there are no such mechanisms, then skip to Step 8. Otherwise proceed to Step 2.

Step 2. Document all keyboard access capabilities (via mechanisms from Step 1) supported by the keyboard interface (from Step 0) of the authoring tool(from authoring tool documentation or from experience). If there are fewer than two keyboard access capabilities supported, or if sequential keyboard access is not included, then skip to Step 7. Otherwise proceed to Step 3.

Step 3. Determine/document the efficiency criteria (including rationale?) for evaluating keyboard access mechanisms that you will use for this particular authoring tool, platform, etc. Go to Step 4.

Step 4. Document the "before state" of the authoring tool user interface on this platform. Use a sequential keyboard access mechanism (from Steps 1 and 2) that navigates the focus one-by-one through all of the items in an ordered set (e.g., menu items, form fields) until the desired item is reached and activated. Record the "after state" of the authoring tool user interface at this point. Determine the "efficiency" of this keyboard access mechanism using your criteria from Step 3. Then go back so the "before state" of the authoring tool user interface (using any mechanism available from Step 1 to do this). Go to Step 5.

Step 5. From the "before state" specified earlier, use a -different from sequentlal-? keyboard access mechanism (from Step 1) (such as keyboard shortcuts and the use of bypass links) on the same objects as used in Step 4. Record the "after state" of the authoring tool user interface at this point, and verify that this "after state" is the same as the "after state" from Step 4. Determine the "efficiency" of this access using the same criteria as used in Step 4. Go to Step 6.

Step 6. Compare/evaluate the "efficiencies" determined from Step 4 and from Step 5. If as a result of this comparison/evaluation, Step 5 is more "efficient" than Step 4, then this authoring tool "passes" this SC on this platform. If Step 5 is more "efficient" than Step 4, or the "efficiencies" are the same for Steps 4 and 5, then this authoring tool fails this SC for this platform. Go to Step 7.

Step 7. If the only keyboard access method supported (from Step 2) is sequential keyboard access, then this authoring tool "fails" this SC for this platform. Go to Step 8.

Step 8. If the authoring tool has not been evaluated as "pass" or "fail" on this platform in previous steps up to this point, then the authoring tool is "N/A" for this SC on this platform.

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)

If the authoring tool does not have any time limits (e.g. automatic logout), then select SKIP.

For each identified time limit on an authoring session:

Check to determine if the authoring tool can be configured (or is already configured) to automatically save any edits to web content before that time limit is reached. If not, then select FAIL.

Test the functionality by authoring content and then allowing the time limit to occur. If the web content changes cannot be recovered, then select FAIL.

If all time limits pass, then select PASS.

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.

Test 0001 Assertion:

Test 0001: Author: Jeanne Spellman

Test 0001 Steps:

If the authoring tool does not have any time limits (e.g. an automatic logout), then select SKIP.

If the authoring tool time limit is a real-time exception, that is, 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, then select SKIP. [@@ should this be a Skip, or a Pass?@@]

If the time limit is essential and extending it would invalidate the activity, then select SKIP.

If the time limit is longer than 20 hours, then select SKIP.

Check whether authors are allowed to turn off each time limit before encountering it and set up the appropriate conditions to test whether it works properly. If each time limit is turned off, then select PASS.

If authors are warned before each time limit expires and are 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, then select PASS.

If authors are allowed to adjust the time limit before encountering it, check the configuration parameters to insure that the time adjustment options are over a wide range that is at least ten times the length of the default setting. If this is true, select PASS.

If the authoring tool has time limits, and none of the above statements are true, then select FAIL.

Check the preference settings. If there is an option to automatically save edits, activate that feature.

Use a sample test file to load some content into the authoring tool. Make a noticable, but minor change to the content. If there is a visible indication that the file has been automatically saved, select PASS. Otherwise, wait 5-10 minutes, close the file without manually saving the changes. Reopen the file. If the change you made is displayed correctly, select PASS. If the change was not saved, select FAIL.

Search the documentation for information on auto-save feature. If an auto-save feature is included in the documentation, confirm that it is working correctly using the procedure in step 2 or other procedure appropriate to the authoring tool. If you can confirm the feature is working, select PASS, otherwise select FAIL.

If the tool is designed such that markup elements are never disclosed to the author, this SC is SKIP

Where markup elements are disclosed to the user (e.g. document outline view, source view, etc.), if it is not possible to select a disclosed element without selecting any of the content that surrounds it, then FAIL.

If the only way to move selection from one disclosed element to the other is by clearing the selection and manually selecting the start and end point of the new element in the source, then FAIL.

Otherwise PASS.

A.3.4.2 Navigate by Programmatic Relationships:

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.

Test 0001 Assertion:

If the tool is designed such that programmatic relationships (ID reference, data structure definition, function definition, etc.) are never disclosed to the author, this SC is SKIP

If a mechanism exists that allows the user to navigate between pieces of web content (elements, functions, etc.) where there is a programmatic relationship (ID reference, data structure definition, function definition, etc.) then PASS

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.

Test 0001 Assertion: All editing-views for enable text search where any text content that is editable by the editing-view is searchable, results can be made visible to authors and given focus, authors are informed when no results are found and search can be made forwards or backwards. @@Jan

Determine (from the user interface or documentation) whether the authoring tool includes settings that affect how the content being edited is perceived by the author. If these settings exist, then document them. If not, then select SKIP.

Create/open web content with the authoring tool.

Determine a "method for testing how the web content will be experienced by end-users" (this may be as simple as opening the content in a user agent; or it may involve ending the authoring session).

For each setting from Step 1, change the setting to a different value. Try to choose values that are as different as possible from the starting values, since this will make detecting differences easier. After changing each setting, save the content and then use the "method for testing how the web content will be experienced by end-users" (from Step 3). If the end user experience has changed for any of the settings, then select FAIL.

If all settings can be changed without affecting the produced web content, then select PASS.

A.4.1.1 Content Changes Reversible (Minimum):

Test 0001 Assertion: All authoring actions are either reversible or the authoring tool requires author confirmation to proceed.

Test 0001: Author: Tim Boland

Test 0001 Steps:

Open new content in the authoring tool with TEXT CONTENT or a mixture of TEXT CONTENT and NON-TEXT CONTENT WITH TEXT ALTERNATIVES, as appropriate to the authoring tool. You may also use the tool to create a sample page of content with text content or both text and non-text content.

Note "state" of web content within that authoring too

Edit that web content using that authoring tool, so that the "state" of web content after edit is different from that in step 2.

Attempt to "cancel" all edit(s) from step 3 by submitting request(s) to that authoring tool using appropriate mechanism provided by that authoring tool. If such mechanisms are not provided, go to step 6.

Immediately after step 4, check that as a result of the request(s) from step 4, the "state" of that web content is the same as the "state" of the same web content from step 2 edit(s). If this check is true, then select PASS. If this check is false, then select FAIL.

Check that this authoring tool provides explicit notification that no further action is possible unless permission is specifically granted by you using an appropriate mechanism provided by this authoring tool (i.e., authoring tool is "frozen" awaiting input from you). If such a notification is not provided, then select FAIL.

Answer "yes" to the "request to proceed" notification from step 6 , attempt to perform a subsequent action related to the authoring tool, and check that this subsequent action is successful. If this check is true, then select PASS. If this check is false, then select FAIL.

For each mechanism to change the preference settings, use those mechanisms to change the relevant preference settings within that authoring tool user interface, so that the "value" of those preference settings is different from that from step 2.

Check if the authoring tool user interface provides explicit notification that no further action is possible from this authoring tool unless permission is specifically granted by you using an appropriate "vehicle" provided by this authoring tool user interface (i.e., authoring tool is "frozen" awaiting input from you). Answer "yes" to the "request to proceed" notification, then verify that the change is successful. If this check is true for all such preference setting mechanisms, then select PASS.

Attempt to "reverse" all changes from step 3 by using the same mechanisms as were used in step 3 to make the changes as appropriate. Check that as a result of the attempted reversals from step 3, the "value" of that associated preference setting is the same as the "value" of the same preference setting from step 2. If this check is true for all such preference setting mechanisms, then select PASS.

Examine the user interface of the authoring tool, noting each user interface component that is necessary in order to meet part A of ATAG 2.0 (e.g. search functions). Note: Many of the success criteria in Part A are more qualitative and will not require particular user interface functionality (e.g. the requirement to follow WCAG 2.0). (Components are checked because they are the constituents of features)

For each of these user interface components:

If the user interface component is part of functionality provided by the platform (e.g. the menu bar of the browser in the case of a web-based tool), then skip to the next component.

If use of the user interface component is a convention of the platform (e.g. how to operate scrollbars, standard Save and Open dialog boxes), then skip to the next component.

If use of the user interface component is clear from its context (e.g. a page zoom feature with percentage values in a drop-down list) , then skip to the next component.

If the user interface component is documented in the interface (e.g. with text next to the item, context-sensitive help), then skip to the next component.

Look up the user interface component (or its associated functionality) in the documentation. If documentation exists, then skip to the next component.

If there is no way to discover how to use the user interface component besides trial-and-error then select FAIL.

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

Examine the user interface of the authoring tool, noting each user interface component that accepts input is available to the author. (Components are checked because they are the constituents of features)

For each of these user interface components:

If the user interface component is part of functionality provided by the platform (e.g. the menu bar of the browser in the case of a web-based tool), then skip to the next component.

If use of the user interface component is a convention of the platform (e.g. how to operate scrollbars, standard Save and Open dialog boxes), then skip to the next component.

If use of the user interface component is clear from its context (e.g. a page zoom feature with percentage values in a drop-down list) , then skip to the next component.

If the user interface component is documented in the interface (e.g. with text next to the item, context-sensitive help), then skip to the next component.

Look up the user interface component (or its associated functionality) in the documentation. If documentation exists, then skip to the next component.

If there is no way to discover how to use the user interface component besides trial-and-error then select FAIL. @@this would definitely benefit from a details section.

This SC applies only to authoring tools that automatically add content during the authoring session. Such processes can range from complex (e.g., a process that builds a whole page from just a few user entries - Note 1 applies here) to basic (e.g. adding a <strong> formatting tag when the user has selected to have text made "bold"). If the authoring tool does not automatically generate content, select SKIP.

Proceed by triggering as many automated authoring processes as possible. Trigger them one at a time with as little author-entered content as possible (e.g. triggering the automated processes on nearly empty pages).

If all of the automated authoring processes result in one of the follow outcomes then select PASS.
(a) The produced content (not necessarily the document as a whole) passes the "Web Content Accessibility Test Procedure (Level AAA)"; or
(b) During the automatic process, authors are prompted for any required accessibility information (WCAG) and if this is properly supplied then the produced content passes the "Web Content Accessibility Test Procedure (Level AAA)"; or
(c) After the automatic generation process, accessibility checking is automatically performed (check-as-you-type systems that check for accessibility continuously will meet this); or
(d) Checking Suggested: After the automatic generation process, the authoring tool prompts authors to perform accessibility checking (such prompts need not be obtrusive).

if any of the processes do not result in any of the outcomes in (3) then, select FAIL.

002 REPEAT WITH AA

003 REPEAT WITH A

Guideline B.1.2: Ensure accessibility information is preserved.

Tests

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)

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

Test 0001 Assertion:

This SC applies only to authoring tools that perform restructuring or recoding transformations. In restructuring transformations, the content technology (e.g. HTML) stays the same, but the structural features of the technology used to markup the content are changed (e.g., linearizing tables, splitting a document into pages. In recoding transformations, the content technology used to encode the content is changed (e.g., HTML to XHTML, a word processing format to HTML). If the authoring tool does not perform such transformations, then select SKIP.

Examine the user interface and documentation for potential processes (e.g. under "Save As", "Export", etc.). While determining candidates: - Note that these must be automatic processes. A general find-and-replace mechanism does not qualify. - Note that the definition of content transformations excludes clipboard actions (such as copy and paste), which are treated separately. - Note that for recoding transformations, only processes resulting in technologies "included" for conformance are applicable. Saving from an "included" technology to an "unincluded" technology is not covered. - Note 1 excludes text alternatives for non-text content, an important subset of the "Listing of Accessibility Information Types". - Note that an equivalent mechanism for preserving the accessibility information must exist (in order to preserve captions, both technologies must support captions). Consult the "Listing of Accessibility Information Types" for the input and output technologies.

If all of the restructuring or recoding transformation processes result in one of the follow outcomes (when operating on the "Comprehensive accessible test content (Level AAA)") then select PASS. (a) The transformed content passes the "Web Content Accessibility Test Procedure (Level AAA)"; or (b) Before the transformation process proceeds, authors are warned that accessibility information may be lost; or (c) After the transformation process, accessibility checking is automatically performed (check-as-you-type systems that check for accessibility continuously will meet this); or (d) Checking Suggested: After the transformation process, the authoring tool prompts authors to perform accessibility checking (such prompts need not be obtrusive).

If any of the transformation processes do not result in any of the outcomes in (3) then, select FAIL.

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)

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

Test 0001 Assertion:@@Jan

Test 0001 Steps:

PRINCIPLE B.2: Authors must be supported in producing accessible content

Tests

Guideline B.2.1: Ensure accessible content production is possible.

Tests

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)

(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.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.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)

Search the user interface (and documentation) for accessibility checking functionality (which can be automated, semi-automated, manual instructions or a combination). If checking functionality is not present, then select FAIL.

Search the user interface (and documentation) for accessibility checking functionality (which can be automated, semi-automated, manual instructions or a combination). If checking functionality is not present, then select FAIL.

Search the user interface (and documentation) for accessibility checking functionality (which can be automated, semi-automated, manual instructions or a combination). If checking functionality is not present, then select FAIL.

Using Comprehensive non-accessible test content (Level A) as a guide, attempt to create accessibility problems using the authoring tool. If this is not possible due to authoring restrictions (such as highly limited editing scope or compulsory fields), then select SKIP.

If accessibility problems have been added to the content, search the user interface (and documentation) for accessibility checking functionality (which can be automated, semi-automated, manual instructions or a combination). If checking functionality is not present, then select FAIL.

Run the checker (if the checker is manual, this will entail following ALL checking instructions.

If the checker is able to cause all of the accessibility problems to be detected (automatically, semi-automatically, manually or a combination), then select PASS. Otherwise, select FAIL.

Using Comprehensive non-accessible test content (Level AA) as a guide, attempt to create accessibility problems using the authoring tool. If this is not possible due to authoring restrictions (such as highly limited editing scope or compulsory fields), then select SKIP.

If accessibility problems have been added to the content, search the user interface (and documentation) for accessibility checking functionality (which can be automated, semi-automated, manual instructions or a combination). If checking functionality is not present, then select FAIL.

Run the checker (if the checker is manual, this will entail following ALL checking instructions.

If the checker is able to cause all of the accessibility problems to be detected (automatically, semi-automatically, manually or a combination), then select PASS. Otherwise, select FAIL.

Using Comprehensive non-accessible test content (Level AAA) as a guide, attempt to create accessibility problems using the authoring tool. If this is not possible due to authoring restrictions (such as highly limited editing scope or compulsory fields), then select SKIP.

If accessibility problems have been added to the content, search the user interface (and documentation) for accessibility checking functionality (which can be automated, semi-automated, manual instructions or a combination). If checking functionality is not present, then select FAIL.

Run the checker (if the checker is manual, this will entail following ALL checking instructions.

If the checker is able to cause all of the accessibility problems to be detected (automatically, semi-automatically, manually or a combination), then select PASS. Otherwise, select FAIL.

Examine the checking functionality identified in the WCAG Level A-related tests for B.3.1.1. If no checking functionality exists, then select SKIP.

If the checker automatically identifies all of the issues, the select SKIP.

If the checker relies on the author to verify any found issues (as semi-automatic checks do) or find issues (as manual instructions do), then check whether support of some kind (e.g. instructions) is provided in each case to help the user make the required decision. If such support is always provided, then select PASS, otherwise select FAIL.

Test 0002 Assertion: Checking assistance (WCAG Level AA) includes help to decide whether potential issues are actual issues, if user judgement is required. (Note: Only shown if the user has specified AA or AAA as the target level) [@@JR updated]

Examine the checking functionality identified in the WCAG Level AA-related tests for B.3.1.1. If no checking functionality exists, then select SKIP.

If the checker automatically identifies all of the issues, the select SKIP.

If the checker relies on the author to verify any found issues (as semi-automatic checks do) or find issues (as manual instructions do), then check whether support of some kind (e.g. instructions) is provided in each case to help the user make the required decision. If such support is always provided, then select PASS, otherwise select FAIL.

Test 0003 Assertion: Checking assistance (WCAG Level AAA) includes help to decide whether potential issues are actual issues, if user judgement is required. (Note: Only shown if the user has specified AAA as the target level) [@@JR updated]

Examine the checking functionality identified in the WCAG Level AAA-related tests for B.3.1.1. If no checking functionality exists, then select SKIP.

If the checker automatically identifies all of the issues, the select SKIP.

If the checker relies on the author to verify any found issues (as semi-automatic checks do) or find issues (as manual instructions do), then check whether support of some kind (e.g. instructions) is provided in each case to help the user make the required decision. If such support is always provided, then select PASS, otherwise select FAIL.

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.

Examine the checking functionality identified in the WCAG Level A-related tests for B.3.1.1. If no checking functionality exists, then select SKIP.

If the checker automatically identifies all of the issues, then select SKIP.

If the checker relies on the author to verify any found issues (as semi-automatic checks do) or find issues (as manual instructions do), then check whether a mechanism of some kind (e.g. hyperlink to the location, identification by line number, instructions on how to locate, etc.) is provided in each case to help the user determine where the potential issue is located within the content. If such a mechanism is always provided, then select PASS, otherwise select FAIL.

Test 0002 Assertion: Checking assistance (WCAG Level AA) includes help to locate potential issues if user judgement is required. (Note: Only shown if the user has specified AA or AAA as the target level) [@@JR updated]

Examine the checking functionality identified in the WCAG Level AA-related tests for B.3.1.1. If no checking functionality exists, then select SKIP.

If the checker automatically identifies all of the issues, then select SKIP.

If the checker relies on the author to verify any found issues (as semi-automatic checks do) or find issues (as manual instructions do), then check whether a mechanism of some kind (e.g. hyperlink to the location, identification by line number, instructions on how to locate, etc.) is provided in each case to help the user determine where the potential issue is located within the content. If such a mechanism is always provided, then select PASS, otherwise select FAIL.

Test 0003 Assertion: Checking assistance (WCAG Level AAA) includes help to locate potential issues if user judgement is required. (Note: Only shown if the user has specified AAA as the target level) [@@JR updated]

Examine the checking functionality identified in the WCAG Level AAA-related tests for B.3.1.1. If no checking functionality exists, then select SKIP.

If the checker automatically identifies all of the issues, then select SKIP.

If the checker relies on the author to verify any found issues (as semi-automatic checks do) or find issues (as manual instructions do), then check whether a mechanism of some kind (e.g. hyperlink to the location, identification by line number, instructions on how to locate, etc.) is provided in each case to help the user determine where the potential issue is located within the content. If such a mechanism is always provided, then select PASS, otherwise select FAIL.

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..

Examine the checking functionality identified for B.3.1.1. If no checking functionality exists, then select SKIP.

Examine the checking functionality (including settings and documentation) to see if it includes any functionality that allows the results of the checking to be programmatically associated with the content (e.g. a file containing the checking results that includes a hyperlink back to the checked content).

If the checking results can be programmatically associated with the content, then select PASS. Otherwise, select FAIL.

Guideline B.3.2: Assist authors in repairing accessibility problems.

Tests

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)

Determine whether the feature can be turned off. If not, go on to the next feature.

If it can be turned off, turn it off and check for any type of warning (text, icon, pop-up, etc.), before and/or after the feature is turned off, explaining that turning off the feature may increase the risk of accessibility problems being introduced. If a warning is present, go on to the next feature.

If no warning is presented, then select FAIL.

If all of the features that can be turned off include warnings, then select PASS.

Identify whether the feature is comparable to another feature of the authoring tool related to either invalid markup, syntax errors, spelling errors, or grammar errors (e.g., an accessibility checker is comparable with a spell checker). If there is no comparable feature, go on to the next feature.

If there is a comprable feature, for both the accessible feature and its comparator-feature, determine how many "opening actions" are required to access each.
"Opening actions" are actions made by authors on components within the user interface that result in new components becoming displayed or enabled. (e.g., keyboard shortcut to a top-level menu item to display a sub-menu, keyboard selection on a button to display a dialog box, mouse click on a checkbox to enable previously disabled sub-items, etc. Actions that do not cause new components to become actionable (e.g., moving focus, scrolling a list), are not counted as "opening actions".)

If the accessible content support feature requires the same or less "opening actions", go on to the next feature.

If the comparator feature requires less "opening actions", then select FAIL.

If all of the accessible content support features required the same or less "opening actions". select PASS.

Guideline B.4.2: Ensure that documentation promotes the production of accessible content.

If the feature does have instructions in the documentation, go on to the next feature.

If the feature does have instructions in the documentation, then select FAIL.

If all of the features have instructions that appear in the documentation, then select PASS.

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)

Test 0001 Assertion: The authoring tool provides a tutorial for an accessible authoring process that is specific to that authoring tool.
[@@JR updated]

Search the authoring tool user interface (and linked support material) for a step-by-step tutorial explaining how to use the tool to produce accessible web content.

If no accessibility-related tutorials can be found, then select FAIL.

If one or more accessibility-related tutorials are found, review the tutorials checking whether any of the tutorials are specific to the authoring tool or whether they only treat the subject generally (such that the tutorials could equally serve as a tutorial for a different authoring tool).

If any of the tutorials is specific to the authoring tool , then select PASS. Otherwise, select FAIL.