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.
8 answers have been received.
Jump to results for question:
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.
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 |
(1 response didn't contain an answer to this question)
Responder | A.4.1.1 tests | Comments on A.4.1.1 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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, 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 |
(1 response didn't contain an answer to this question)
Responder | A.4.1.2 tests | Comments on A.4.1.2 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Recommend changes (see comments field) | TYPO: within that authoring-->within the authoring -proceeed CHANGE TO: 1. Examine the authoring tool for mechanisms to change any preference settings within that authoring tool user interface. If there are none, then select SKIP. 2. For each mechanism for changing the preference settings: 1. Note "values" of preference settings within the mechanism. 2. Use the mechanisms to change the relevant preference settings, so that the "value" of those preference settings is different. 3. If an OK button (or similar) is required to save the preferences, select the button. 4. If the authoring tool prompts the user for confirmation to proceed, then go to the next mechanism for changing the preference settings. 5. Attempt to "reverse" the change. If the original value can be set then go to the next mechanism for changing the preference settings. 6. Otherwise, select FAIL. 3. Select PASS. (all of the settings must have met the requirement) |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
A.4.1.3 Content Changes Reversible (Enhanced): Authors can sequentially reverse a series of reversible authoring actions. (Level AAA) Note: It is acceptable to clear the authoring action history at the end of authoring sessions.
Test 0001 Assertion: A sequence of authoring actions can be reversed sequentially.
Choice | All responders |
---|---|
Results | |
Accept the proposal | 6 |
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 |
(2 responses didn't contain an answer to this question)
Responder | A.4.1.3 tests | Comments on A.4.1.3 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | ||
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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: Accessibility features are either described, part of the platform, or not used directly by authors.
Test 0001 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 |
(1 response didn't contain an answer to this question)
Responder | A.4.2.1 tests | Comments on A.4.2.1 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | TYPO: " ," |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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: All features are either described, part of the platform, or not used directly by authors.
Test 0001 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 |
(1 response didn't contain an answer to this question)
Responder | A.4.2.2 tests | Comments on A.4.2.2 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | TYPO: that accepts input is-->that accepts input and is |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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) Note: This success criterion applies only to automatic processes specified by the authoring tool developer. It does not apply when author actions prevent generation of accessible web content (WCAG).
Test 0001 Assertion: 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.
Test 0001: 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 |
(1 response didn't contain an answer to this question)
Responder | B.1.1.1 tests | Comments on B.1.1.1 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Recommend changes (see comments field) | CHANGE: beyond what the author has experienced --> beyond what the author has specified |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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: Content generated automatically during authoring sessions is either accessible or the user is prompted or checking is enabled automatically or checking is suggested.
Test 0001 Author: Jan
<strong>
formatting tag when the user has selected to have text made "bold"). If the authoring tool does not automatically generate content, select . 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 |
(1 response didn't contain an answer to this question)
Responder | B.1.1.2 tests | Comments on B.1.1.2 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | TYPO: Determing whther --> Determine whether |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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: Restructuring transformations either preserve accessibility information or the user is prompted or checking is enabled automatically or checking is suggested.
Test 0001 Author: Jan
Test 0002 Assertion: Recoding transformations either preserve accessibility information or the user is prompted or checking is enabled automatically or checking is suggested.
Test 0002 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 |
(1 response didn't contain an answer to this question)
Responder | B.1.2.1 tests | Comments on B.1.2.1 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | TYPO: wheret he - also remove the table markup for the conditions |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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 and the source and destination use the same web content technology. (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: Accessibility information in the copied content is preserved when the same authoring tool editing view is both the source and destination of the copy-paste.
Test0001 Author: Jan
Choice | All responders |
---|---|
Results | |
Accept the proposal | 7 |
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.1.2.2 tests | Comments on B.1.2.2 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li | Recommend changes (see comments field) | Shouldn't step 3 just be copy a structured content instead of as much content as possible? Also, the condition of the SC is "support copy and past of structured content", not "support copy and paste". The test need to add the possibility that the structure did not copy over, no? |
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: Optimizing web content transformations preserve accessibility information.
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 |
(1 response didn't contain an answer to this question)
Responder | B.1.2.3 tests | Comments on B.1.2.3 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | The proposal needs more discussion (see comments field) | Some accessibility information need not be preserved in the optimization because it doesn't apply to the optimization - the example cited for example - unless it's a preview of the "pretty print" but why would you necessarily preserve alt text for content meant exclusively for hard copy? |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | TYPO: ":." |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
B.1.2.4 Text Alternatives for Non-Text Content are Preserved: If the authoring tool provides web content transformations that preserve non-text content in the output, then any text alternatives for that non-text content are also preserved, if equivalent mechanisms exist in the web content technology of the output. (Level A). Note: This success criterion only applies when the output technology is "included" for conformance.
Test 0001 Assertion: 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.
Test0001 Author: Jan
Choice | All responders |
---|---|
Results | |
Accept the proposal | 5 |
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 |
(2 responses didn't contain an answer to this question)
Responder | B.1.2.4 tests | Comments on B.1.2.4 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Recommend changes (see comments field) | Output intended for online viewing. The print issue again comes to mind. |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | |
Frederick Boland | Accept the proposal | |
Sueann Nichols | ||
Alex Li |
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 Any restrictions on the web content that authors can edit do not prevent the web content from conforming to WCAG.
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 |
(1 response didn't contain an answer to this question)
Responder | B.2.1.1 tests | Comments on B.2.1.1 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | TYPO: Remove table markup |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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: The authoring tool interface first presents authors with the most accessible options when provided with several choices for achieving a desired result.
Test 0001 Author: Greg, 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 |
(1 response didn't contain an answer to this question)
Responder | B.2.2.1 tests | Comments on B.2.2.1 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | TYPO: Remove table markup |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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) Note: Success Criterion B.4.1.4 addresses the prominence of the mechanisms.
Test 0001 Assertion: The authoring tool provides access to content properties related to accessibility information.
Test 0001 Author: Greg, 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 |
(1 response didn't contain an answer to this question)
Responder | B.2.2.2 tests | Comments on B.2.2.2 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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: : Authors are able to modify programmatically associated text alternatives for non-text content.
Test 0001 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 |
(1 response didn't contain an answer to this question)
Responder | B.2.3.1 tests | Comments on B.2.3.1 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | TYPO: non-->none |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
B.2.3.2 Repair of Text Alternatives During Authoring Sessions: If the authoring tool attempts to automatically or semi-automatically repair text alternatives for non-text content ("repair strings") during an authoring session, then the following conditions are both true: (Level A)
Test 0001 Assertion: Any automatic or semi-automatic repair attempts for text alternatives for non-text content ("repair strings") made during an authoring session, must not use generic strings and irrelevant strings and Authors have the opportunity to accept, modify, or reject the repair strings prior to insertion in the content.
Test 0001 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 |
(1 response didn't contain an answer to this question)
Responder | B.2.3.2 tests | Comments on B.2.3.2 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | TYPO: |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
B.2.3.3 Repair of Text Alternatives After Authoring Sessions: If the authoring tool attempts to automatically repair text alternatives for non-text content after an authoring session has ended, then the following are both true: (Level A)
Test 0001 Assertion: Any automatic or semi-automatic repair attempts for text alternatives for non-text content ("repair strings") made after authoring sessions, must not use generic strings and irrelevant strings and Authors have the opportunity to accept, modify, or reject the repair strings prior to insertion in the content.
Test 0001 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 |
(1 response didn't contain an answer to this question)
Responder | B.2.3.3 tests | Comments on B.2.3.3 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | TYPO: If no the automatic repairs-->If no automatic repairs |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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: When authors enter programmatically associated text alternatives for non-text content, then the text alternatives are automatically saved and suggested by the authoring tool, if the same non-text content is reused, and the author has the option to edit or delete the saved text alternatives.
Test 0001 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 |
(1 response didn't contain an answer to this question)
Responder | B.2.3.4 tests | Comments on B.2.3.4 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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: There are accessible template (WCAG) options for a range of template uses.
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 |
(1 response didn't contain an answer to this question)
Responder | B.2.4.1 tests | Comments on B.2.4.1 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
B.2.4.2 Identify Template Accessibility (Minimum): If the authoring tool includes a template selection mechanism and provides any non-accessible template (WCAG) options, then the templates are provided such that the template selection mechanism can display distinctions between the accessible and non-accessible options. (Level AA) Note: The distinction can involve providing information for the accessible templates, the non-accessible templates or both.
Test 0001 Assertion: Template selection mechanisms can display distinctions between the accessible and non-accessible options.
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 |
(1 response didn't contain an answer to this question)
Responder | B.2.4.2 tests | Comments on B.2.4.2 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | TYPO: If the authoring tool does not provide a mechanism for selecting templates that is not just a standard file selection mechanism, then select SKIP.--> If the authoring tool only provides a standard file selection mechanism for selecting templates, then select SKIP. - not distinction-->no distinction |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
B.2.4.3 Author-Created Templates: If the authoring tool includes a template selection mechanism and allows authors to create new non-accessible templates (WCAG), then authors can enable the template selection mechanism to display distinctions between accessible and non-accessible templates that they create. (Level AA) Note: The distinction can involve providing information for the accessible templates (WCAG), the non-accessible templates or both.
Test 0001 Assertion: Authors can enable the template selection mechanism to display distinctions between accessible and non-accessible templates that they create.
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 |
(1 response didn't contain an answer to this question)
Responder | B.2.4.3 tests | Comments on B.2.4.3 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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: Template selection mechanisms can display distinctions between the accessible and non-accessible options.
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 |
(1 response didn't contain an answer to this question)
Responder | B.2.4.4 tests | Comments on B.2.4.4 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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: Any repositories of pre-authored content records the accessibility status of each piece of content and makes accessible options sufficiently prominent.
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 |
(1 response didn't contain an answer to this question)
Responder | B.2.5.1 tests | Comments on B.2.5.1 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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: Any repositories of pre-authored content records the accessibility status of each piece of 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 |
(1 response didn't contain an answer to this question)
Responder | B.2.5.2 tests | Comments on B.2.5.2 |
---|---|---|
Roberto Scano | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Greg Pisocky | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Jan Richards | Accept the proposal | TYPO: pre-authored content records-->pre-authored content record |
Frederick Boland | Accept the proposal | |
Sueann Nichols | Accept the proposal | |
Alex Li |
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
.