w3c/wbs-design
or
by mail to sysreq
.
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:
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 0001 Assertion: Checking assistance (WCAG Level A) is present in less-restrictive authoring tools.
Test0001 Author: Jan
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
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
Test 0004 Assertion: Checking assistance (WCAG Level A) is present in more-restrictive authoring tools.
Test0004 Author: Jan
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
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
Choice | All 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 |
Responder | B.3.1.1 tests | Comments 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 |
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: Checking assistance (WCAG Level A) includes help to decide whether potential issues are actual issues, if user judgement is required.
Test0001 Author: Jan
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
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
Choice | All 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 |
Responder | B.3.1.2 tests | Comments 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 |
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 0001 Assertion: Checking assistance (WCAG Level A) includes help to locate potential issues if user judgement is required.
Test0001 Author: Jan
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
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
Choice | All 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 |
Responder | B.3.1.3 tests | Comments 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 |
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 0001 Assertion: Accessibility status reporting is present.
Test0001 Author: Jan
Choice | All 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 |
Responder | B.3.1.4 tests | Comments 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 |
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: Checking results can be programmatically associated to the content.
Test0001 Author: Jan
Choice | All 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 |
Responder | B.3.1.5 tests | Comments 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 |
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 0001 Assertion: Checking assistance (WCAG Level A) includes help to repair all detected issues.
Test0001 Author: Jan
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
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
Choice | All 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 |
Responder | B.3.2.1 tests | Comments 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 |
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.
Test0001 Author: Jan
Choice | All 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 |
Responder | B.4.1.1 tests | Comments 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 |
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 also be turned back on.
Test0001 Author: Jan
Choice | All 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 |
Responder | B.4.1.2 tests | Comments 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 |
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 0001 Assertion: All accessible content support features that can be turned off include a warning of the potential consequences.
Test0001 Author: Jan
Choice | All 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 |
Responder | B.4.1.3 tests | Comments 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 |
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 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
Choice | All 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 |
Responder | B.4.1.4 tests | Comments 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 |
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 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
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
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
Choice | All 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 |
Responder | B.4.2.1 tests | Comments 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 |
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.
Test0001 Author: Jan
Choice | All 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 |
Responder | B.4.2.2 tests | Comments 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 |
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.
Test0001 Author: Jan
Choice | All 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 |
Responder | B.4.2.3 tests | Comments 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 |
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.
Test0001 Author: Jan
Choice | All 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 |
Responder | B.4.2.4 tests | Comments 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 |
Everybody has responded to this questionnaire.
Compact view of the results / list of email addresses of the responders
WBS home / Questionnaires / WG questionnaires / Answer this questionnaire
w3c/wbs-design
or
by mail to sysreq
.