11 July 2012
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 Assertion: The web-based portions of an authoring tool user interface meet WCAG 2.0 at AAA level. Test 0001 Steps:
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 in ATAG 2.0 section Relationship to the Web Content Accessibility Guidelines (WCAG) 2.0. Test 0002 Assertion: The web-based portions of an authoring tool user interface meet WCAG 2.0 at AA level. Test 0002 Steps:
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 in ATAG 2.0 section Relationship to the Web Content Accessibility Guidelines (WCAG) 2.0. Test 0003 Assertion: The web-based portions of an authoring tool user interface meet WCAG 2.0 at A level. Test 0003 Steps:
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 in ATAG 2.0 section Relationship to the Web Content Accessibility Guidelines (WCAG) 2.0. |
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 Assertion: Any non-web-based portions of the authoring tool user interface follow the accessibility guidelines for the platform. Test 0001 Steps:
|
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 Assertion: All non-web-based components of the authoring tool user interface successfully communicate name and role with the platform accessibility services (accessibility APIs). Test 0001 Steps:
|
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) |
Test 0001 Assertion: For web-based tools, any text alternatives for programmatically associated non text content in the editing view meets WCAG 2.0 1.1.1. . Test 0001 Steps: [Adapted from Tim B's Steps (for each editing view in the authoring tool):]
Test 0002 Assertion: For non-web-based tools, any text alternatives for programmatically associated non text content in the editing view can be programmatically determined. Test 0002 Steps: [Adapted from Tim B's Steps (for each editing view in the authoring tool):]
|
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)
|
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. Test 0001 Steps:
|
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)
|
Test 0001 Assertion: For web-based tools: Status information about the content (e.g. spellchecking) can be programatically determined. Test 0001: Author: Jeanne Spellman Test 0001 Steps:
Test 0002 Assertion: For non-web-based tools: Status information about the content (e.g. spellchecking) can be programatically determined. Test 0002 Steps:
|
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) |
Test 0001 Assertion:Text formatting properties can be programmatically determined. Test 0001: Author: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
A.3.1.5 Customize Keyboard Access:If the authoring tool includes keyboard commands, then those keyboard commands can be customized. (Level AAA) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001: Author: Tim Boland Test 0001 Steps:
|
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)
|
Test 0001 Assertion: Test 0001: Author: Jeanne Spellman Test 0001 Steps:
|
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) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
Guideline A.3.3: (For the authoring tool user interface) Help authors avoid flashing that could cause seizures. | Tests |
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:
|
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) |
Test 0001 Assertion: Test0001 Steps:
|
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)
|
Test 0001 Assertion: Test0001 Steps:
|
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
A.3.7.2 Preview (Enhanced):If a preview is provided, then authors can specify which user agent performs the preview. (Level AAA) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
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:
|
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) |
Test 0001 Assertion:User interface setting changes can be reversed, or require author confirmation to proceed. Test 0001: Author: Tim Boland Test 0001 Steps:
|
A.4.1.3 Content Changes Reversible (Enhanced):Authors can sequentially reverse a series of reversible authoring actions. (Level AAA)
|
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
A.4.2.2 Document All Features:For each authoring tool feature, at least one of the following is true: (Level AA)
|
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test0001 Steps:
|
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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). |
Test 0001 Assertion: Test 0001 Steps: |
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).
|
Test 0001 Assertion: 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) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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)
|
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |
B.4.2.2 Feature Instructions:Instructions for using any accessible content support features appear in the documentation. (Level A) |
Test 0001 Assertion: Test 0001 Steps: |
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: Test 0001 Steps: |
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) |
Test 0001 Assertion: Test 0001 Steps: |