W3C home > Mailing lists > Public > w3c-wai-au@w3.org > July to September 2012

RE: ATAG2 test writing - Principle B4

From: Richards, Jan <jrichards@ocadu.ca>
Date: Tue, 17 Jul 2012 18:28:58 +0000
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <0B1EB1C972BCB740B522ACBCD5F48DEB03ABF79B@ocadmail-maildb.ocad.ca>
Hi all,

My tests are below...

(BTW: See my note under "B.4.1.3 Feature Availability Information")

=============

A NEW Tool: "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. 
- Note 1: In some cases, the same feature will meet multiple success criteria. For example, an appropriately-designed accessibility checker might serve to meet B.1.1.2, B.2.3.2, B.2.3.4, B.3.1.1, B.3.1.2, B.3.1.3, B.3.1.4 and B.3.1.5.)
- Note 2: The list should only include features that can be used to produce content using the "included" technology (for conformance).
B.1.1.1 Content Auto-Generation After Authoring Sessions (WCAG)
B.1.1.2 Content Auto-Generation During Authoring Sessions (WCAG)
B.1.2.1 Restructuring and Recoding Transformations (WCAG)
B.1.2.2 Copy-Paste Inside Authoring Tool (WCAG)
B.1.2.3 Optimizations Preserve Accessibility
B.1.2.4 Text Alternatives for Non-Text Content are Preserved
B.2.1.1 Accessible Content Possible (WCAG)
B.2.2.1 Accessible Option Prominence (WCAG)
B.2.2.2 Setting Accessibility Properties (WCAG)
B.2.3.1 Alternative Content is Editable (WCAG)
B.2.3.2 Repair of Text Alternatives During Authoring Sessions
B.2.3.3 Repair of Text Alternatives After Authoring Sessions
B.2.3.4 Save for Reuse
B.2.4.1 Accessible Template Options (WCAG)
B.2.4.2 Identify Template Accessibility (Minimum)
B.2.4.3 Author-Created Templates
B.2.4.4 Identify Template Accessibility (Enhanced)
B.2.5.1 Pre-Authored Content Selection Mechanism
B.2.5.2 Pre-Authored Content Accessibility Status
B.3.1.1 Checking Assistance (WCAG)
B.3.1.2 Help Authors Decide
B.3.1.3 Help Authors Locate
B.3.1.4 Status Report
B.3.1.5 Programmatic Association of Results
B.3.2.1 Repair Assistance (WCAG)


B.4.1.1 Features Active by Default: All accessible content support features are turned on by default. (Level A)
----
Test 0001 Assertion: All accessible content support features are turned on by default.
Test 0001: Author: Jan Richards
Test 0001 Steps: 
1. Create or retrieve the "List of Accessible Content Support Features"
2. If none of the features on the "List" can be turned off, then select PASS.
3. For any of the features on the "List" that can be turned off, check whether the authoring tool (in its default state, e.g. after installation) has them turned on.
4. If all of the features (that can be turned off) are turned on by default, then select PASS. If any of the features (that can be turned off) are not turned on, then select FAIL.


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: All accessible content support features that can be turned off, can be turned back on.
Test 0001: Author: Jan Richards
Test 0001 Steps:
1. Retrieve or create the "List of Accessible Content Support Features".
2. If none of the features on the "List" can be turned off, then select SKIP.
3. For any of the features on the "List" that can be turned off, turn off the feature and then attempt to turn it back on.
4. If all of the features (that can be turned off) can be turned back on, then select PASS. If any of the features (that can be turned off), cannot be turned back on, then select FAIL.


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.
----
Test 0001 Assertion: 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.
Test 0001: Author: Jan Richards
Test 0001 Steps:
1. Check whether the authoring tool can be used to publish web content technologies besides the(s) included in your evaluation. If not, then select SKIP.
2. Check whether the authoring tool (in its user interface or documentation) includes a statement to the effect that accessible content production is not supported in that other technology. If so, then PASS.
3. Check whether the authoring tool meets SC B.2.1.1 Accessible Content Possible (WCAG) with respect to the other technolog(ies).

@@ISSUE: This is tricky because it just says "support for production", not that the production of the other format needs to meet ATAG 2.0. This makes some sense because if it did imply ATAG 2.0 conformance then to do an ATAG 2.0 conformance check on any format for a tool would actually require doing one on all of them. But, what, then, does "support" mean? One (weak) possibility is above - that accessible content be possible. Another (stronger) possibility is that a "supported" format has to have a checker. If that's what we mean...I think we should fix the SC to say that. @@


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: All accessible content support features that can be turned off, include a warning of the potential consequences. 
Test 0001: Author: Jan Richards
Test 0001 Steps:
1. Retrieve or create the "List of Accessible Content Support Features".
2. For any of the features on the "List" that can be turned off, bring up the functionality to turn off the feature.
3. 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.
4. If all of the features include such a warning, then select PASS. If any of the features do not include such a warning, then select FAIL.


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: Content support features are as prominent as features related to either invalid markup, syntax errors, spelling errors or grammar errors
Test 0001: Author: Jan Richards
Test 0001 Steps: 
1. Retrieve or create the "List of Accessible Content Support Features".
2. For each feature, identify another feature of the authoring tool that serves the same or similar purpose with respect to a different content quality issue (e.g. syntax errors, spelling errors, or grammar errors).
3. For each 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. For example: (a) keyboard shortcut to a top-level menu item to display a sub-menu, (b) keyboard selection on a button to display a dialog box, (c) 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".
4. If, in any case the comparator feature requires less "opening actions", then select FAIL. Otherwise, select PASS.


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: At least two  example of Level AAA accessible authoring practices appear in the documentation.
Test 0001: Author: Jan Richards
Test 0001 Steps:
1. Locate the documentation.
2. Locate examples of authoring practice being used (e.g. markup, screen shot, etc.).
3. Using the Web Content Accessibility Test Procedure, test whether the authoring practice (as shown) would result in content that meets WCAG 2.0 Level AAA. Note, if the authoring practice shows only a section of content, assume for the test that the rest of the document will meet WCAG 2.0 Level AAA.

Test 0002 Assertion: At least two  example of Level AA accessible authoring practices appear in the documentation.
Test 0002: Author: Jan Richards
Test 0002 Steps:
1. Locate the documentation.
2. Locate examples of authoring practice being used (e.g. markup, screen shot, etc.).
3. Using the Web Content Accessibility Test Procedure, test whether the authoring practice (as shown) would result in content that meets WCAG 2.0 Level AA. Note, if the authoring practice shows only a section of content, assume for the test that the rest of the document will meet WCAG 2.0 Level AA.

Test 0003 Assertion: At least two  example of Level A accessible authoring practices appear in the documentation.
Test 0003: Author: Jan Richards
Test 0003 Steps:
1. Locate the documentation.
2. Locate examples of authoring practice being used (e.g. markup, screen shot, etc.).
3. Using the Web Content Accessibility Test Procedure, test whether the authoring practice (as shown) would result in content that meets WCAG 2.0 Level A. Note, if the authoring practice shows only a section of content, assume for the test that the rest of the document will meet WCAG 2.0 Level A.


B.4.2.2 Feature Instructions: Instructions for using any accessible content support features appear in the documentation. (Level A)
----
Test 0001 Assertion: Instructions for using any accessible content support features appear in the documentation.
Test 0001: Author: Jan Richards
Test 0001 Steps:
1. Retrieve or create the "List of Accessible Content Support Features".
2. For each feature, check whether any instructions are available (in the user interface or documentation).
3. If instructions are available, then PASS. If instructions are not available, then FAIL.


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.
Test 0001: Author: Jan Richards
Test 0001 Steps:
1. 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.
2. If no accessibility-related tutorials can be found, then select FAIL.
3. 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. If none are specific to the authoring tool, then select FAIL.


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 The authoring tool documentation contains an index to the instructions for using any accessible content support features.
Test 0001: Author: Jan Richards
Test 0001 Steps:
1. Search the authoring tool user interface (and linked support material) for an instruction index (e.g. "Search Help"). 
2. If no accessibility-related tutorials can be found, then select FAIL.
3. Retrieve or create the "List of Accessible Content Support Features".
4. If all of the features on the "List" have instructions listed in the instruction index, then select PASS. Otherwise, select FAIL.
Received on Tuesday, 17 July 2012 18:29:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 17 July 2012 18:29:23 GMT