w3c/wbs-design
or
by mail to sysreq
.
The results of this questionnaire are available to anybody.
This questionnaire was open from 2013-06-21 to 2013-07-12.
7 answers have been received.
Jump to results for question:
from Jan's email of 18 June 2013
Proposal #1: To align the wording of B.2.5.1 with that of B.2.4.2 ("Identify Template Accessibility"). I also suggest moving the e.g. list to a new definition (proposal#3) - and removing "themes" since these are already examples of templates (http://www.w3.org/WAI/AU/2013/ED-ATAG20-20130614/#def-Template):
B.2.5.1 Identify Pre-Authored Content Accessibility: If the *authoring tool* includes a *selection mechanism for pre-authored content* and provides any non-*accessible pre-authored content* *options*, then the content is provided such that the selection mechanism can display distinctions between the accessible and non-accessible options. (Level AA)
- Note: The distinction can involve providing information for the accessible pre-authored content, the non-accessible pre-authored content or both.
Choice | All responders |
---|---|
Results | |
Accept the proposal | 3 |
Recommend changes (see comments field) | 4 |
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.2.5.1 Identify Pre-Authored Content Accessibility (Proposal 1) | Proposal #1 |
---|---|---|
Jan Richards | Accept the proposal | |
Jeanne F Spellman | Recommend changes (see comments field) | remove "the content is provided such that" so it reads: If the *authoring tool* includes a *selection mechanism for pre-authored content* and provides any non-*accessible pre-authored content* *options*, then the selection mechanism can display distinctions between the accessible and non-accessible options. (Level AA) |
Alessandro Miele | Recommend changes (see comments field) | Agree with Jeanne |
Frederick Boland | Recommend changes (see comments field) | agree with Jeanne |
Tom Babinszki | Accept the proposal | |
Alastair Campbell | Recommend changes (see comments field) | Also agree with Jeanne... |
Jutta Treviranus | Accept the proposal |
from Jan's email of 18 June 2013
Proposal #2: To drop B.2.5.2 and replace it with a Level AA requirement modelled on the Level A template requirement (B.2.4.1). In a way this a lower bar than the current version (which requires every item to be tagged), but it can also been seen as higher since previously the SC was AAA and all of the content could be inaccessible as long as it was tagged as such:
B.2.5.2 Accessible Pre-Authored Content Options (WCAG): If the *authoring tool* provides *pre-authored content*, then a range of *accessible pre-authored content (to WCAG 2.0 Level AA)* *options* are provided. (Level AA)
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.2.5.2 Accessible Pre-Authored Content Options (WCAG) Proposal #2 | Proposal #2 |
---|---|---|
Jan Richards | Accept the proposal | |
Jeanne F Spellman | Accept the proposal | |
Alessandro Miele | Accept the proposal | |
Frederick Boland | Accept the proposal | |
Tom Babinszki | Accept the proposal | |
Alastair Campbell | Accept the proposal | |
Jutta Treviranus | Accept the proposal |
from Jan's email of 18 June 2013
PROPOSAL #3: To define THREE "pre-authored content"-related terms that are missing from the glossary:
Pre-authored content:
Pieces of web content, created prior to an authoring session, that the authoring tool developer makes available to authors to use in the content being edited. Examples include clip art, sample videos, user interface widgets.
Note 1: For templates, an incomplete form of pre-authored content, refer to Guideline B.2.4.
Note 2: If the authoring tool uses pre-authored content automatically, refer to Guideline B.1.1.
Accessible pre-authored content (WCAG):
*Pre-authored content* that is either already *accessible content (WCAG)* or would be accessible, if it was appropriately inserted into an empty document.
Note: If extensive author input is required to make use of pre-authored content, the content may in fact be a *template*.
Pre-authored selection mechanism
A function beyond standard file selection that allows *authors* to select *pre-authored content* to use in an *authoring session* (e.g. clip art gallery, widget palette).
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 | PROPOSAL #3: To define THREE "pre-authored content"-related terms that are missing from the glossary: | Proposal #3 |
---|---|---|
Jan Richards | Accept the proposal | |
Jeanne F Spellman | Recommend changes (see comments field) | Pre-authored content: add "or previous authors" Pieces of web content created prior to an authoring session, that the authoring tool developer or previous authors makes available to authors to use in the content being edited. |
Alessandro Miele | Accept the proposal | |
Frederick Boland | Accept the proposal | |
Tom Babinszki | Accept the proposal | |
Alastair Campbell | Accept the proposal | |
Jutta Treviranus | 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
.