W3C WBS Home

Results of Questionnaire AUWG Survey for 7 January 2013 - part 4 (B.3 - B.4)

The results of this questionnaire are available to anybody.

This questionnaire was open from 2013-01-03 to 2013-03-29.

7 answers have been received.

Jump to results for question:

  1. B.3.1.1 tests
  2. B.3.1.2 tests
  3. B.3.1.3 tests
  4. B.3.1.4 tests
  5. B.3.1.5 tests
  6. B.3.2.1 tests
  7. B.4.1.1 tests
  8. B.4.1.2 tests
  9. B.4.1.3 tests
  10. B.4.1.4 tests
  11. B.4.2.1 tests
  12. B.4.2.2 tests
  13. B.4.2.3 tests
  14. B.4.2.4 tests

1. B.3.1.1 tests

Success Criteria

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

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

Test(s)

Test 0001 Assertion: Checking assistance (WCAG Level A) is present in less-restrictive authoring tools.

Test0001 Author: Jan

  1. Determine whether the authoring tool allows authors to open/paste-in pre-existing content (i.e., non-accessible test content file (Level A)). If this is not possible, then select SKIP.
  2. 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.
  3. Run the checker (if the checker is manual, this will entail following ALL checking instructions). If the checker provides detail about individual errors then you can open/paste-in all of the non-accessible test content file (Level A) at once. If the checker provides only aggregate results, open/paste-in the non-accessible test content file (Level A) one piece at a time.
  4. 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.

Test 0002 Assertion: Checking assistance (WCAG Level AA) is present in less-restrictive authoring tools. (Note: Only shown if the user has specified AA or AAA as the target level)

Test0002 Author: Jan

  1. Determine whether the authoring tool allows authors to open/paste-in pre-existing content (i.e., non-accessible test content file (Level AA)). If this is not possible, then select SKIP.
  2. 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.
  3. Run the checker (if the checker is manual, this will entail following ALL checking instructions). If the checker provides detail about individual errors then you can open/paste-in all of the non-accessible test content file (Level AA) at once. If the checker provides only aggregate results, open/paste-in the non-accessible test content file (Level AA) one piece at a time.
  4. 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.

Test 0003 Assertion: Checking assistance (WCAG Level AAA) is present in less-restrictive authoring tools. (Note: Only shown if the user has specified AAA as the target level)

Test0003 Author: Jan

  1. Determine whether the authoring tool allows authors to open/paste-in pre-existing content (i.e., non-accessible test content file (Level AAA)). If this is not possible, then select SKIP.
  2. 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.
  3. Run the checker (if the checker is manual, this will entail following ALL checking instructions). If the checker provides detail about individual errors then you can open/paste-in all of the non-accessible test content file (Level AAA) at once. If the checker provides only aggregate results, open/paste-in the non-accessible test content file (Level AAA) one piece at a time.
  4. 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.

Test 0004 Assertion: Checking assistance (WCAG Level A) is present in more-restrictive authoring tools.

Test0004 Author: Jan

  1. If the authoring tool allows allow authors to open/paste-in pre-existing content, select SKIP.
  2. Using non-accessible test content file (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.
  3. 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.
  4. Run the checker (if the checker is manual, this will entail following ALL checking instructions).
  5. 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.

Test 0005 Assertion: Checking assistance (WCAG Level AA) is present in more-restrictive authoring tools. (Note: Only shown if the user has specified AA or AAA as the target level)

Test0005 Author: Jan

  1. If the authoring tool allows allow authors to open/paste-in pre-existing content, select SKIP.
  2. Using non-accessible test content file (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.
  3. 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.
  4. Run the checker (if the checker is manual, this will entail following ALL checking instructions).
  5. 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.

Test 0006 Assertion: Checking assistance (WCAG Level AAA) is present in more-restrictive authoring tools. (Note: Only shown if the user has specified AAA as the target level)

Test0006 Author: Jan

  1. If the authoring tool allows allow authors to open/paste-in pre-existing content, select SKIP.
  2. Using non-accessible test content file (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.
  3. 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.
  4. Run the checker (if the checker is manual, this will entail following ALL checking instructions).
  5. 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.

Summary

ChoiceAll responders
Results
Accept the proposal 7
Recommend changes (see comments field)
The proposal needs more discussion (see comments field)
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.3.1.1 testsComments on B.3.1.1
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal
Greg Pisocky Accept the proposal
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

2. B.3.1.2 tests

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)

Test(s)

Test 0001 Assertion: Checking assistance (WCAG Level A) includes help to decide whether potential issues are actual issues, if user judgement is required.

Test0001 Author: Jan

  1. 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.
  2. If the checker automatically identifies all of the issues, the select SKIP.
  3. 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)

Test0002 Author: Jan

  1. 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.
  2. If the checker automatically identifies all of the issues, the select SKIP.
  3. 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)

Test0003 Author: Jan

  1. 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.
  2. If the checker automatically identifies all of the issues, the select SKIP.
  3. 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.

Summary

ChoiceAll responders
Results
Accept the proposal 7
Recommend changes (see comments field)
The proposal needs more discussion (see comments field)
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.3.1.2 testsComments on B.3.1.2
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal
Greg Pisocky Accept the proposal 0001.2 typo "then select skip"
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

3. B.3.1.3 tests

Success Criteria

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.

Test(s)

Test 0001 Assertion: Checking assistance (WCAG Level A) includes help to locate potential issues if user judgement is required.

Test0001 Author: Jan

  1. 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.
  2. If the checker automatically identifies all of the issues, then select SKIP.
  3. 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)

Test0002 Author: Jan

  1. 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.
  2. If the checker automatically identifies all of the issues, then select SKIP.
  3. 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)

Test0003 Author: Jan

  1. 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.
  2. If the checker automatically identifies all of the issues, then select SKIP.
  3. 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.

Summary

ChoiceAll responders
Results
Accept the proposal 7
Recommend changes (see comments field)
The proposal needs more discussion (see comments field)
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.3.1.3 testsComments on B.3.1.3
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal
Greg Pisocky Accept the proposal
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

4. B.3.1.4 tests

Success Criteria

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.

Test(s)

Test 0001 Assertion: Accessibility status reporting is present.

Test0001 Author: Jan

  1. Examine the checking functionality identified for B.3.1.1. If no checking functionality exists, then select SKIP.
  2. If the checking functionality does not result in any information being returned to the author about accessibility issues, then select FAIL.
  3. If the information returned is gathered together in some way (e.g., a conformance statement, a list of accessibility problems, etc.), then select PASS.

Summary

ChoiceAll responders
Results
Accept the proposal 7
Recommend changes (see comments field)
The proposal needs more discussion (see comments field)
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.3.1.4 testsComments on B.3.1.4
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal
Greg Pisocky Accept the proposal
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

5. B.3.1.5 tests

Success Criteria

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

Test 0001 Assertion: Checking results can be programmatically associated to the content.

Test0001 Author: Jan

  1. Examine the checking functionality identified for B.3.1.1. If no checking functionality exists, then select SKIP.
  2. 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. as a file containing the checking results that includes a hyperlink back to the checked content).
  3. If the checking results can be programmatically associated with the content, then select PASS. Otherwise, select FAIL.

Summary

ChoiceAll responders
Results
Accept the proposal 7
Recommend changes (see comments field)
The proposal needs more discussion (see comments field)
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.3.1.5 testsComments on B.3.1.5
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal
Greg Pisocky Accept the proposal
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

6. B.3.2.1 tests

Success Criteria

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

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

Test(s)

Test 0001 Assertion: Checking assistance (WCAG Level A) includes help to repair all detected issues.

Test0001 Author: Jan

  1. 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.
  2. If the authoring tool automatically repairs all identified issues, then select SKIP.
  3. For each identified issue, that is not automatically fixed:
    1. Check whether support of some kind (e.g. dialog with repair options, instructions on how to repair, etc.) is provided. If it is, go to the next issue.
    2. If no support is provided, then select FAIL.
    3. Go to the next issue (if any).
  4. Select PASS (all of the issues must have repair support)

Test 0002 Assertion: Checking assistance (WCAG Level AA) includes help to repair all detected issues. (Note: Only shown if the user has specified AA or AAA as the target level)

Test0002 Author: Jan

  1. 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.
  2. If the authoring tool automatically repairs all identified issues, then select SKIP.
  3. For each identified issue, that is not automatically fixed:
    1. Check whether support of some kind (e.g. dialog with repair options, instructions on how to repair, etc.) is provided. If it is, go to the next issue.
    2. If no support is provided, then select FAIL.
    3. Go to the next issue (if any).
  4. Select PASS (all of the issues must have repair support)

Test 0003 Assertion: Checking assistance (WCAG Level AAA) includes help to repair all detected issues. (Note: Only shown if the user has specified AAA as the target level)

Test0003 Author: Jan

  1. 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.
  2. If the authoring tool automatically repairs all identified issues, then select SKIP.
  3. For each identified issue, that is not automatically fixed:
    1. Check whether support of some kind (e.g. dialog with repair options, instructions on how to repair, etc.) is provided. If it is, go to the next issue.
    2. If no support is provided, then select FAIL.
    3. Go to the next issue (if any).
  4. Select PASS (all of the issues must have repair support)

Summary

ChoiceAll responders
Results
Accept the proposal 7
Recommend changes (see comments field)
The proposal needs more discussion (see comments field)
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.3.2.1 testsComments on B.3.2.1
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal
Greg Pisocky Accept the proposal
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

7. B.4.1.1 tests

Success Criteria

B.4.1.1 Features Active by Default: All accessible content support features are turned on by default. (Level A)

Test(s)

Test 0001 Assertion: All accessible content support features are turned on by default.

Test0001 Author: Jan

  1. Create or retrieve the List of Accessible Content Support Features (the "List')
  2. For each feature on the "List":
    1. If the feature is "always on", go to the next feature.
    2. If the feature can be turned off, check whether it is on by default. If it is, go to the next feature.
    3. If the future is off by default, then then select FAIL.
    4. Go to the next feature (if any).
  3. Select PASS (all of the accessible content support features must have passed)

Summary

ChoiceAll responders
Results
Accept the proposal 7
Recommend changes (see comments field)
The proposal needs more discussion (see comments field)
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.4.1.1 testsComments on B.4.1.1
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal TYPO: Future-->Feature
Greg Pisocky Accept the proposal
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

8. B.4.1.2 tests

Success Criteria

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

Test 0001 Assertion: All accessible content support features that can be turned off, can also be turned back on.

Test0001 Author: Jan

  1. Retrieve or create the List of Accessible Content Support Features (the "List").
  2. For each feature on the "List":
    1. Determine whether the feature can be turned off. If not, go to the next feature.
    2. Turn off the feature and then check whether it can be turned back on. If it can be turned back on, go to the next feature.
    3. If the feature cannot be turned back on, then select FAIL.
    4. Go to the next feature (if any).
  3. Select PASS (all of the accessible content support features must have passed)

Summary

ChoiceAll responders
Results
Accept the proposal 7
Recommend changes (see comments field)
The proposal needs more discussion (see comments field)
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.4.1.2 testsComments on B.4.1.2
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal
Greg Pisocky Accept the proposal
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

9. B.4.1.3 tests

Success Criteria

B.4.1.3 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(s)

Test 0001 Assertion: All accessible content support features that can be turned off include a warning of the potential consequences.

Test0001 Author: Jan

  1. Retrieve or create the List of Accessible Content Support Features (the "List").
  2. For each feature on the "List":
    1. Determine whether the feature can be turned off. If not, go to the next feature.
    2. 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 to the next feature.
    3. If no warning is presented, then select FAIL.
    4. Go to the next feature (if any).
  3. Select PASS (all of the accessible content support features must have passed)

Summary

ChoiceAll responders
Results
Accept the proposal 7
Recommend changes (see comments field)
The proposal needs more discussion (see comments field)
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.4.1.3 testsComments on B.4.1.3
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal
Greg Pisocky Accept the proposal
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

10. B.4.1.4 tests

Success Criteria

B.4.1.4 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(s)

Test 0001 Assertion: Content support features are as prominent as features related to either invalid markup, syntax errors, spelling errors or grammar errors.

Test0001 Author: Jan

  1. Retrieve or create the List of Accessible Content Support Features (the "List").
  2. For each feature on the "List":
    1. 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 to the next feature.
    2. If there is a comparable 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".)
    3. If the accessible content support feature requires the same or less "opening actions", go to the next feature.
    4. If the comparator feature requires less "opening actions", then select FAIL.
    5. Go to the next feature (if any).
  3. Select PASS (all of the accessible content support features must have passed)

Summary

ChoiceAll responders
Results
Accept the proposal 7
Recommend changes (see comments field)
The proposal needs more discussion (see comments field)
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.4.1.4 testsComments on B.4.1.4
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal
Greg Pisocky Accept the proposal
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

11. B.4.2.1 tests

Success Criteria

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

Test 0001 Assertion: At least two examples of Level A accessible authoring practices appear in the documentation. (Note: Only shown if the user has specified A as the target level)

Test0001 Author: Jan

  1. Locate the authoring tool's documentation.
  2. Locate examples of authoring practice being used in the documentation (e.g. examples of markup, screenshots, etc.).
  3. Referring to the Web Content Accessibility Test Procedure (Level A), determine whether the demonstrated authoring practice would meet WCAG 2.0 Level A (e.g. if an image insertion dialog box is shown with an inappropriately empty alt field).
  4. If two practices can be found that would meet WCAG 2.0 Level A, select PASS. Otherwise, select FAIL.

Test 0002 Assertion: At least two examples of Level AA accessible authoring practices appear in the documentation. (Note: Only shown if the user has specified AA as the target level)

Test0002 Author: Jan

  1. Locate the authoring tool's documentation.
  2. Locate examples of authoring practice being used in the documentation (e.g. examples of markup, screenshots, etc.).
  3. Referring to the Web Content Accessibility Test Procedure (Level AA), determine whether the demonstrated authoring practice would meet WCAG 2.0 Level AA (e.g. if an image insertion dialog box is shown with an inappropriately empty alt field).
  4. If two practices can be found that would meet WCAG 2.0 Level AA, select PASS. Otherwise, select FAIL.

Test 0003 Assertion: At least two examples of Level AAA accessible authoring practices appear in the documentation. (Note: Only shown if the user has specified AAA as the target level)

Test0003 Author: Jan

  1. Locate the authoring tool's documentation.
  2. Locate examples of authoring practice being used in the documentation (e.g. examples of markup, screenshots, etc.).
  3. Referring to the Web Content Accessibility Test Procedure (Level AAA), determine whether the demonstrated authoring practice would meet WCAG 2.0 Level AAA (e.g. if an image insertion dialog box is shown with an inappropriately empty alt field).
  4. If two practices can be found that would meet WCAG 2.0 Level AAA, select PASS. Otherwise, select FAIL.

Summary

ChoiceAll responders
Results
Accept the proposal 6
Recommend changes (see comments field)
The proposal needs more discussion (see comments field) 1
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.4.2.1 testsComments on B.4.2.1
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal TYPO: In line 4: two practices-->two examples
Greg Pisocky The proposal needs more discussion (see comments field) What is "the documentation"? There is no single authoritative guide in many instances or the "users manual" or help may make reference to yet another document/resource where such examples exist - would that count?
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

12. B.4.2.2 tests

Success Criteria

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

Test(s)

Test 0001 Assertion: Instructions for using any accessible content support features appear in the documentation.

Test0001 Author: Jan

  1. Search the authoring tool user interface (and linked support material) for documentation (e.g. a help system)
  2. If no documentation can be found, then select FAIL.
  3. Retrieve or create the List of Accessible Content Support Features (the "List").
  4. For each feature on the "List":
    1. If the feature does have instructions in the documentation, go to the next feature.
    2. If the feature does have instructions in the documentation, then select FAIL.
    3. Go to the next feature (if any).
  5. Select PASS (all of the accessible content support features must have passed)

Summary

ChoiceAll responders
Results
Accept the proposal 6
Recommend changes (see comments field)
The proposal needs more discussion (see comments field) 1
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.4.2.2 testsComments on B.4.2.2
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal TYPO: Line 2: does have-->does not have
Greg Pisocky The proposal needs more discussion (see comments field) What is "the documentation"? There is no single authoritative guide in many instances or the "users manual" or help may make reference to yet another document/resource where such examples exist - would that count?
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

13. B.4.2.3 tests

Success Criteria

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

Test 0001 Assertion: The authoring tool provides a tutorial for an accessible authoring process that is specific to that authoring tool.

Test0001 Author: Jan

  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).
  4. If any of the tutorials is specific to the authoring tool , then select PASS. Otherwise, select FAIL.

Summary

ChoiceAll responders
Results
Accept the proposal 6
Recommend changes (see comments field)
The proposal needs more discussion (see comments field) 1
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.4.2.3 testsComments on B.4.2.3
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal TYPO:
- tutorials is-->tutorials are
- " ,"
Greg Pisocky The proposal needs more discussion (see comments field) Does the tool have to point directly to an accessibility tutorial, or is it sufficient to point to the location where tutorials for the product exist and in that location provide tutorials on accessibility as well as other features of the document?
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

14. B.4.2.4 tests

Success Criteria

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

Test 0001 Assertion: The authoring tool documentation contains an index to the instructions for using any accessible content support features.

Test0001 Author: Jan

  1. Search the authoring tool user interface (and linked support material) for an instruction index (e.g. "Search Help", list of help topics, etc.).
  2. If no index can be found, then select FAIL.
  3. Retrieve or create the List of Accessible Content Support Features (the "List").
  4. For each feature on the "List":
    1. If the feature does not have instructions in the documentation, go to the next feature.
    2. If the feature does have instructions in the documentation, and is reachable from the index, go to the next feature.
    3. If the feature does have instructions in the documentation, but is not reachable from the index, then select FAIL.
    4. Go to the next feature (if any).
  5. Select PASS (all of the accessible content support features must have passed)

Summary

ChoiceAll responders
Results
Accept the proposal 6
Recommend changes (see comments field) 1
The proposal needs more discussion (see comments field)
Disagree with the proposal (see comments field)
Neutral - will accept the consensus of the group

Details

Responder B.4.2.4 testsComments on B.4.2.4
Roberto Scano Accept the proposal
Alessandro Miele Accept the proposal
Jan Richards Accept the proposal TYPO: In line 3 of the loop: is not reachable --> they are not reachable
Greg Pisocky Recommend changes (see comments field) I like this proposal. I would add add between 2 and 3 If an index exists, check for the term "accessibility", if the term is not found, then select "fail"
Jeanne F Spellman Accept the proposal
Frederick Boland Accept the proposal
Sueann Nichols Accept the proposal

More details on responses

Non-responders

The following persons have not answered the questionnaire:

  1. Jutta Treviranus <jtreviranus@faculty.ocadu.ca>
  2. Cynthia Shelly <cyns@microsoft.com>
  3. Andrew Ronksley <andrew.ronksley@rnib.org.uk>
  4. Alastair Campbell <acampbell@nomensa.com>
  5. Alex Li <alli@microsoft.com>
  6. Cherie Ekholm <cheriee@exchange.microsoft.com>
  7. Tom Babinszki <tbabins@us.ibm.com>

Send an email to all the non-responders.


Compact view of the results / list of email addresses of the responders

WBS home / Questionnaires / WG questionnaires / Answer this questionnaire


Maintained by Laurent Carcone, from a development by Dominique Hazaël-Massieux (dom@w3.org) on an original design by Michael Sperberg-McQueen $Id: showv.php3,v 1.127 2015-02-04 08:52:34 carcone Exp $. Please send bug reports and request for enhancements to lcarcone@w3.org with w3t-sys@w3.org copied (if your mail client supports it, send mail directly to the right persons)