W3C

(Draft) ATAG 2.0 Testing

3 April 2011

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 concerned with producing the "included" web content technologies. This includes views of the web content being edited and features that are independent of the content being edited (e.g., menus, button bars, status bars, user preferences, documentation).
  2. Reflected content accessibility problems: The authoring tool is responsible for ensuring that editing-views display the web content being edited in a way that is more accessible to authors with disabilities (e.g., ensuring that text alternatives in the content can be programmatically determined). However, where an authoring tool user interface accessibility problem is caused directly by the content being edited (e.g., if an image in the content lacks a text alternative), then this would not be considered a deficiency in the accessibility of the authoring tool user interface.
  3. 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).
  4. User agent features: Web-based authoring tools may rely on user agent features (e.g., keyboard navigation, find functions, display preferences, undo features) to satisfy success criteria. Conformance claims are optional, but any claim that is made must record the user agent(s).
  5. 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.
  6. 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:

  1. Author availability: Any Part B success criteria that refer to authors only apply during authoring sessions.
  2. 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).
  3. Applicability after the end of an authoring session: Authoring tools are responsible for the web content accessibility (WCAG) of web content that they automatically generate after the end of an author's authoring session (see Success Criterion B.1.1.1). For example, if the developer changes the site-wide templates of a content management system, these would be required to meet the accessibility requirements for automatically-generated content. Authoring tools are not responsible for changes to the accessibility of content that the author causes, whether it is author-generated or automatically-generated by another system that the author has specified (e.g., a third-party feed).
  4. 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).
  5. 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).
  6. 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.
  7. 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).

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

Comprehensive accessible test content (Level A, AA, AAA): Used to test transformation, test checkers for false positives, etc.

Comprehensive non-accessible test content (Level A, AA, AAA): Used to test checkers.

Selection of separate pieces of content: To be used as needed to test various SCs.

 

PART A: Make the authoring tool user interface accessible Tests
PRINCIPLE A.1: Authoring tool user interfaces must follow applicable accessibility guidelines Tests
Guideline A.1.1: (For the authoring tool user interface) Ensure that web-based functionality is accessible. Tests

A.1.1.1 Web-Based Accessible (WCAG):

If the authoring tool contains web-based user interfaces, then those web-based user interfaces meet the WCAG 2.0 success criteria. (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)

Test 0001 Steps:

  1. If no parts of the authoring tool are web-based, then this SC is N/A.
  2. Check any web-based parts of the authoring tool with the Web Content Accessibility Test Procedure at the level being test (A, AA, or AAA).
  3. If WCAG 2.0 Level A, AA, or AA is reached, record this.
    Note: The WCAG 2.0 requirement that "only accessibility-supported ways of using technologies are relied upon to satisfy the WCAG 2.0 success criteria" does not need to be applied as described at: http://www.w3.org/TR/ATAG20/#conf-rel-wcag.
Guideline A.1.2: (For the authoring tool user interface) Ensure that non-web-based functionality is accessible. Tests

A.1.2.1 Accessibility Guidelines:

If the authoring tool contains non-web-based user interfaces, then those non-web-based user interfaces follow user interface accessibility guidelines for the platform. (Level A)

Test 0001 Steps:

  1. If no parts of the authoring tool are non-web-based, then this SC is N/A.
  2. If the accessibility guidelines (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 follwed the guidelines, then PASS, otherwise FAIL.
  3. If the accessibility guidelines (for the platform) used by the developer is not known, choose one from the list (http://www.w3.org/TR/2012/WD-IMPLEMENTING-ATAG20-20120410/#sc_a121) and use it to test the accessibility of the user interface. If the user interface has follwed the guidelines, then PASS, otherwise FAIL.

A.1.2.2 Platform Accessibility Services:

If the authoring tool contains non-web-based user interfaces, then those non-web-based user interfaces implement communication with platform accessibility services. (Level A)

Test 0001 Steps:

  1. If no parts of the authoring tool are non-web-based, then this SC is N/A.
  2. Check each user interface component with the Platform Accessibility Service Test Procedure to determine if it is (a) present, (b) has an accessible name and (c) has an appropriate UI component role. If (a)-(c) are all yes, then PASS, otherwise FAIL.
PRINCIPLE A.2: Editing-views must be perceivable Tests
Guideline A.2.1: (For the authoring tool user interface) Make alternative content available to authors. Tests

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)

Adapted from Tim B's Steps (for each editing view in the authoring tool):

  1. Open NON-TEXT CONTENT WITH TEXT ALTERNATIVES or create content with non-text content
  2. Check if the editing view can render the non-text content in the editing view, if not then this SC is N/A
  3. Check if the text alternatives can be programmatically determined: (a) for web-based tools, is WCAG2 1.1.1 passed? (b) for non-web-based tools is an accessible name/label present in the accessibility API (check with Platform Accessibility Service Test Procedure)

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.

(Jeanne) If the authoring tool renders time-based media (e.g. audio or video) in the editing view, then either one of the following options are true:

  • The authoring tool provides the option to render captions or transcript
  • authors are provided an option to preview the media in a user agent capable of rendering the captions or transcript
Guideline A.2.2: (For the authoring tool user interface) Editing-view presentation can be programmatically determined. Tests

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.

(Jeanne) If the editing view modifies the presentation to provide status information, such as spell-checking, then at least one of the following is true:

  • The status information (e.g. a dotted underline to indicate incorrectly spelled words) is coded semantically in HTML. [@@ get a code example of how this could be done. ARIA role?@@]
  • The status information properties are visible in a tool that shows the accessibility features for the platform. An example would be the access tool for the Microsoft windows platforms.

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)

  
PRINCIPLE A.3: Editing-views must be operable Tests
Guideline A.3.1: (For the authoring tool user interface) Provide keyboard access to authoring features. Tests

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,

then the authoring tool provides a way for authors to determine the keyboard commands associated with authoring tool user interface components. (Level AAA)		  
Guideline A.3.2: (For the authoring tool user interface) Provide authors with enough time. Tests

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)

  
Guideline A.3.3: (For the authoring tool user interface) Help authors avoid flashing that could cause seizures.  

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)

Test0001:

  1. If the authoring tool cannot be used to edit time-based content such as video, animation, animated gifs etc., then this SC is N/A
  2. If the authoring tool does not include editing views that render visual time-based content such as video, animation, animated gifs etc., then this SC is N/A
  3. If the renderings are non-editable, such as previews, this SC is N/A.
  4. Load sample video (audio, animation, animated gifs etc.)
  5. If the authoring tool can be set to never play time-based content automatically AND once playing the content can be paused, then PASS.
  6. If the editing view is web-based and the browser can be used to prevent auto-play and to pause the playing content then PASS.
Guideline A.3.4: (For the authoring tool user interface) Enhance navigation and editing via content structure. Tests

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)

Test0001 Steps:

  1. If the tool is designed such that markup elements are never disclosed to the author, this SC is N/A
  2. 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.
  3. 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.
  4. Otherwise PASS.

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.

Test0001 Steps:

  1. 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 N/A
  2. 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
Guideline A.3.5: (For the authoring tool user interface) Provide text search of the content. Tests

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.
  
Guideline A.3.6: (For the authoring tool user interface) Manage preference settings. Tests

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)

  
Guideline A.3.7: (For the authoring tool user interface) Ensure that previews are at least as accessible as in-market user agents. Tests

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)

  
PRINCIPLE A.4: Editing-views must be understandable Tests
Guideline A.4.1: (For the authoring tool user interface) Help authors avoid and correct mistakes. Tests

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)

  
Guideline A.4.2: (For the authoring tool user interface) Document the user interface including all accessibility features. Tests

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

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).
  
PART B: Support the production of accessible content Tests
PRINCIPLE B.1: Fully automatic processes must produce accessible content Tests
Guideline B.1.1: Ensure automatically specified content is accessible. Tests

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)

Test0001 Steps:

  1. This SC only applies to authoring tools that add anything to the end-user experience beyond what the author has experienced during the authoring session. Otherwise, the SC is N/A
  2. The SC's note also makes it clear that the SC refers to developer-provided processes, not processes created by the author or other third-parties.
  3. If the auto-generation system primarily works by creating a wrapper around the author's entries, try to test the auto-generation system with as little author-entered content as possible.
  4. If author input is required, ensure that only accessible content is added and that all prompts are followed correctly.
  5. If the auto-generation system acts differently depending on the author's entries, try to test the auto-generation system with the "comprehensive accessible test content"
  6. If additional author input is required, ensure that only accessible content is added and that all prompts are followed correctly.
  7. Once the system produces output, follow the Web Content Accessibility Test Procedure to determine if it meets the WCAG 2.0 success criteria TARGET_LEVEL

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

If the authoring tool provides the functionality for automatically generating web content during an authoring session, 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) 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.
 
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)

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

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

  
Guideline B.2.2: Guide authors to produce accessible content. Tests

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)

  
Guideline B.2.3: Assist authors with managing alternative content for non-text content. Tests

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,

when authors enter programmatically associated text alternatives for non-text content, then both of the following are true: (Level AAA)
  • (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.
  
Guideline B.2.4: Assist authors with accessible templates. Tests

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)

  
Guideline B.2.5: Assist authors with accessible pre-authored content. Tests

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)

  

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)

  
PRINCIPLE B.3: Authors must be supported in improving the accessibility of existing content Tests
Guideline B.3.1: Assist authors in checking for accessibility problems. Tests

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)

  

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)

  
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)

  
PRINCIPLE B.4: Authoring tools must promote and integrate their accessibility features Tests
Guideline B.4.1: Ensure the availability of features that support the production of accessible content. Tests

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)

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

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)