w3c/wbs-design or
by mail to sysreq.
W3C
Site Navigation
Nearby
Results of Questionnaire UAWG Survey for 6 October 2011
The results of this questionnaire are available to anybody. In addition, answers are sent to the following email addresses: w3c-archive@w3.org, jeanne@w3.org
This questionnaire was open from 2011-09-30 to 2011-10-21.
5 answers have been received.
Jump to results for question:
- Summary for Guideline 2.7
- Summary for Guideline 2.8
- Summary for Guideline 2.9
- Summary for Guideline 2.10
- Summary for Guideline 2.11
1. Summary for Guideline 2.7
Guideline 2.7 - Configure and store preference settings.
Users can configure, store and restore accessibility preference settings (2.7.1, 2.7.2, 2.7.3) that persist between sessions. Users can manage multiple sets of preference settings and restore groups of settings to defaults (2.7.4, 2.7.5); and users can set preference setting outside the user interface so the default user interface does not prevent access (2.7.6). It's also recommended that groups of settings can be transported to compatible systems, and a wizard is available to help users configure their preferences (2.7.7, 2.7.8).
Summary
| Choice | All responders |
|---|---|
| Results | |
| Agree with the proposal | 3 |
| Disagree with the proposal | |
| Neutral, will accept consensus of the group | |
| Suggest the following changes to the proposal | 2 |
Details
| Responder | Summary for Guideline 2.7 | Comments on 2.7 |
|---|---|---|
| Markku Hakkinen | Agree with the proposal | |
| Kimberly Patch | Suggest the following changes to the proposal | minor grammar change: ... and a wizard be available... |
| Greg Lowney | Suggest the following changes to the proposal | 2.7.2 does not match the summary "Users can...store...accessibility preference settings...that persist between sessions." Rather, it currently says accessibility preference settings are stored between sessions, without user action or option. 2.7.4 is not "so the *default* user interface does not prevent access" but rather so "the *current* user interface settings do not prevent access". Might consider using different verbs to indicate different priority levels, such as "Users can" for the Level A, "Users should be able to" for Level AA, and "It's also recommended" for Level AAA. Right now this summary uses the first and last, but doesn't distinguish between A and AA. Thus: "Users can configure and restore accessibility preference settings (2.7.1, 2.7.3), and accessibility settings persist between sessions (2.7.2). Users should be allowed to manage multiple sets of preference settings and restore groups of settings to defaults (2.7.4, 2.7.5), and adjust preference setting outside the user interface so the current user interface does not prevent access (2.7.6). It's also recommended that groups of settings can be transported to compatible systems, and a wizard is available to help users configure their preferences (2.7.7, 2.7.8)." |
| Simon Harper | Agree with the proposal | |
| Jan Richards | Agree with the proposal |
2. Summary for Guideline 2.8
Guideline 2.8 - Provide toolbar configuration.
Summary: It's recommended that users can add, remove and configure the position of graphical user agent controls (2.8.1) and restore them to their default settings (2.8.2).
Summary
| Choice | All responders |
|---|---|
| Results | |
| Agree with the proposal | 5 |
| Disagree with the proposal | |
| Neutral, will accept consensus of the group | |
| Suggest the following changes to the proposal |
Details
| Responder | Summary for Guideline 2.8 | Comments on 2.8 |
|---|---|---|
| Markku Hakkinen | Agree with the proposal | |
| Kimberly Patch | Agree with the proposal | |
| Greg Lowney | Agree with the proposal | |
| Simon Harper | Agree with the proposal | |
| Jan Richards | Agree with the proposal |
3. Summary for Guideline 2.9
Guideline 2.9 - Allow time-independent interaction.
Summary: Users can extend the time limit for user input (2.9.1) and the user agent shows the progress of content in the process of downloading (2.9.2).
Summary
| Choice | All responders |
|---|---|
| Results | |
| Agree with the proposal | 2 |
| Disagree with the proposal | |
| Neutral, will accept consensus of the group | |
| Suggest the following changes to the proposal | 3 |
Details
| Responder | Summary for Guideline 2.9 | Comments on 2.9 |
|---|---|---|
| Markku Hakkinen | Suggest the following changes to the proposal | I think it is important to stress that only limits controllable by the user agent can be extended. The present summary text implies too much. Suggested change: Users can extend the time limit for user input when such limits are controllable by the user agent (2.9.1)... |
| Kimberly Patch | Suggest the following changes to the proposal | minor grammar change: ... input(2.9.1); the user agent shows... |
| Greg Lowney | Suggest the following changes to the proposal | Mark's suggestion is more technically correct. The second clause is fine but could also be shortened to "Users can...*be shown* the progress of content in the process of downloading (2.9.2)." (I think the fact that it's the user agent doing the showing is implied.) However, I'd also like to suggest that SC 2.9.2 be rephrased so that it it's okay for user agents to let users disable progress updates. For example, could change "2.9.2 Retrieval Progress: The user agent shows the progress of content retrieval. (Level A)" to read "2.9.2 Retrieval Progress: *By default* the user agent shows the progress of content retrieval. (Level A)" |
| Simon Harper | Agree with the proposal | |
| Jan Richards | Agree with the proposal |
4. Summary for Guideline 2.10
Guideline 2.10 - Help users avoid flashing that could cause seizures
Summary: By default, the user agent does not display any component or content that flashes unless the flash is below the general flash and red flash thresholds (2.10.1). It's also recommended that the user agent does not display any component or content that flashes (2.10.2).
Summary
| Choice | All responders |
|---|---|
| Results | |
| Agree with the proposal | 4 |
| Disagree with the proposal | |
| Neutral, will accept consensus of the group | |
| Suggest the following changes to the proposal | 1 |
Details
| Responder | Summary for Guideline 2.10 | Comments on 2.10 |
|---|---|---|
| Markku Hakkinen | Agree with the proposal | |
| Kimberly Patch | Agree with the proposal | |
| Greg Lowney | Suggest the following changes to the proposal | The first sentence is fine, although leaving out "recognized" really changes the meaning from the SC. Even though it's longer, I'd prefer "By default, the user agent does not display any component or *recognized* content that flashes unless the flash is below the general flash and red flash thresholds (2.10.1)." Or, if in the summary you want to avoid technical terms like "recognized", it could be "By default, the user agent does not display any component or content *that it knows* flashes unless the flash is below the general flash and red flash thresholds (2.10.1)." I think the second sentence is far too misleading if it leaves out "by default". I'd recommend "It's also recommended that *by default* the user agent does not display any component or content that *it knows* flashes (2.10.2). |
| Simon Harper | Agree with the proposal | |
| Jan Richards | Agree with the proposal |
5. Summary for Guideline 2.11
Guideline 2.11 - Provide control of content that may reduce accessibility
Summary: The user can globally show/hide background images (2.11.1), load content to play only on on explicit request (2.11.2), render a placeholder for executable content (2.11.3), toggle executable content (2.11.4), adjust the playback rate of recorded content (2.11.5), control and navigate rendered audio and animation that's longer than three seconds (2.11.6, 2.11.7). It's also recommended that the user can navigate audio and animation based on semantics (2.11.8), discover,choose, scale and position available tracks (2.11.9, 2.11.11), adjust media size (2.11.10), and control media contrast and brightness (2.11.12).
Summary
| Choice | All responders |
|---|---|
| Results | |
| Agree with the proposal | 2 |
| Disagree with the proposal | |
| Neutral, will accept consensus of the group | |
| Suggest the following changes to the proposal | 3 |
Details
| Responder | Summary for Guideline 2.11 | Comments on 2.11 |
|---|---|---|
| Markku Hakkinen | Suggest the following changes to the proposal | Suggested change: It's also recommended that the user can navigate audio and animation based on authored (or recognized) structure and semantics (2.11.8)... |
| Kimberly Patch | Suggest the following changes to the proposal | Minor grammar change: Users can globally... |
| Greg Lowney | Suggest the following changes to the proposal | It might be possible to simplify the first sentence to read "Users can globally control the initial presentation/execution of background images (2.11.1), playable content (2.11.2) and executable content (2.11.3), as well as adjust the playback rate (2.11.5), stop/pause/resume (2.11.6), and navigate within (2.11.7) media being played." This is less detailed but less verbose. I agree with Marks's suggested change to the second sentence. |
| Simon Harper | Agree with the proposal | |
| Jan Richards | Agree with the proposal | typo: on on grammar: first sentence - missing and at the end |
More details on responses
- Markku Hakkinen: last responded on 6, October 2011 at 15:50 (UTC)
- Kimberly Patch: last responded on 6, October 2011 at 17:14 (UTC)
- Greg Lowney: last responded on 13, October 2011 at 04:02 (UTC)
- Simon Harper: last responded on 13, October 2011 at 16:21 (UTC)
- Jan Richards: last responded on 13, October 2011 at 17:21 (UTC)
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
Report issues
on GitHub project