w3c/wbs-design or
by mail to sysreq.
W3C
Site Navigation
Nearby
Results of Questionnaire UAWG Survey for 13 May
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 2010-05-07 to 2010-05-14.
4 answers have been received.
Jump to results for question:
- Proposal for 5.3.5 Context Sensitive Help
- Proposal for 5.3.6 Appropriate Language
- Proposal for 3.10.1 Highlight Viewport
- Proposal for 3.10.2 Move Viewport to Selection
- Proposal for 3.10.3 Move Viewport to Focus
- Proposal for 3.10.4 Resizable
- Proposal for 3.10.5 Scrollbars
- Proposal for 3.10.8 Do Not Take Focus
- Proposal for 3.10.9 Stay on Top
- Proposal for 3.10.10 Close Viewport
- Proposal for 3.10.11 Same UI
- Proposal for 3.10.12 Indicate Viewport Position
1. Proposal for 5.3.5 Context Sensitive Help
See 5.3.5 Context Sensitive Help Intent, Examples and Related Resources.
Summary
| Choice | All responders |
|---|---|
| Results | |
| Accept the proposal | 2 |
| Recommend changes (see comments field) | |
| The proposal needs more discussion (see comments field) | 1 |
| Disagree with the proposal | |
| Neutral - will accept the consensus of the group | 1 |
Details
| Responder | Proposal for 5.3.5 Context Sensitive Help | Comments 5.3.5 |
|---|---|---|
| Kelly Ford | Neutral - will accept the consensus of the group | |
| Simon Harper | Accept the proposal | |
| Greg Lowney | The proposal needs more discussion (see comments field) | Re the SC itself, see last week's comments at http://www.w3.org/2002/09/wbs/36791/20100427/results#xq1. I think the Intent and/or Examples really should try to make the case for this being more important than merely having the feature covered in general, non-context-sensitive help. Right now that seems to be taken for granted but not demonstrated or explained. For example, can you show in this example that using context-sensitive help is really that much better than the user activating general help and searching for "Use My Style Sheet", and that even if it's slightly easier, that it will be done often enough to make significant difference overall? |
| Kimberly Patch | Accept the proposal | minor proofing: Activating help the user should be By activating help, |
2. Proposal for 5.3.6 Appropriate Language
See 5.3.6 Appropriate Language
Intent, Examples and Related Resources.Summary
| Choice | All responders |
|---|---|
| Results | |
| Accept the proposal | 3 |
| Recommend changes (see comments field) | |
| The proposal needs more discussion (see comments field) | 1 |
| Disagree with the proposal | |
| Neutral - will accept the consensus of the group |
Details
| Responder | Proposal for 5.3.6 Appropriate Language | Comments 5.3.6 |
|---|---|---|
| Kelly Ford | Accept the proposal | |
| Simon Harper | Accept the proposal | |
| Greg Lowney | The proposal needs more discussion (see comments field) | Re the SC itself and by extension the Intent, see last week's comments at http://www.w3.org/2002/09/wbs/36791/20100427/results#xq2. |
| Kimberly Patch | Accept the proposal |
3. Proposal for 3.10.1 Highlight Viewport
See 3.10.1 Highlight Viewport Intent, Examples and Related Resources.
Summary
| Choice | All responders |
|---|---|
| Results | |
| Accept the proposal | 3 |
| Recommend changes (see comments field) | |
| The proposal needs more discussion (see comments field) | 1 |
| Disagree with the proposal | |
| Neutral - will accept the consensus of the group |
Details
| Responder | Proposal for 3.10.1 Highlight Viewport | Comments 3.10.1 |
|---|---|---|
| Kelly Ford | Accept the proposal | |
| Simon Harper | Accept the proposal | |
| Greg Lowney | The proposal needs more discussion (see comments field) | Interesting that the SC and Intent spend a lot of time explaining why highlighting shouldn't be just by color of rendered text, but are there any user agents that do this with color alone? If this is a problem with rendered text, wouldn't it be approximately as much of a problem when using color alone for non-textual elements? The need to use something in addition to color is touched in the Intent, but not required by the SC. It seems like a scrollable, single-line text field would count as a nested viewport. Are there any UA that highlight such fields, other than merely putting a text cursor in it? Would the presence of a text cursor be enough to satisfy the SC? Conversely, many existing UA use a very subtle highlighting mechanism (e.g. a barely-visible, fixed-width dotted rectangle) to identify the active frame. That seems to be contrary to the spirit of the SC, but not to its wording. For comparison, ISO addresses doesn't give viewports special treatment, but rather accomplishes the same goal by several more generally-applicable requirements. To paraphrase: (1) a keyboard focus cursor (e.g. highlight) must visually indicate which user-interface element has the keyboard focus at a given moment, as well as a text cursor to indicate the focus location within a text element; (2) where the hardware supports it, users must be able to individualize attributes of all keyboard focus cursors, text cursors and pointers, including, but not limited to, shape, size, stroke width, color, blink rate (if any), and pointer trails (if any); and (3) software must provide high-visibility focus and text cursors. |
| Kimberly Patch | Accept the proposal |
4. Proposal for 3.10.2 Move Viewport to Selection
See 3.10.2 Move Viewport to Selection Intent, Examples and Related Resources.
Summary
| Choice | All responders |
|---|---|
| Results | |
| Accept the proposal | 3 |
| Recommend changes (see comments field) | |
| The proposal needs more discussion (see comments field) | |
| Disagree with the proposal | |
| Neutral - will accept the consensus of the group |
(1 response didn't contain an answer to this question)
Details
| Responder | Proposal for 3.10.2 Move Viewport to Selection | Comments 3.10.2 |
|---|---|---|
| Kelly Ford | Accept the proposal | |
| Simon Harper | Accept the proposal | |
| Greg Lowney | ||
| Kimberly Patch | Accept the proposal |
5. Proposal for 3.10.3 Move Viewport to Focus
See 3.10.3 Move Viewport to Focus Intent, Examples and Related Resources.
Summary
| Choice | All responders |
|---|---|
| Results | |
| Accept the proposal | 3 |
| Recommend changes (see comments field) | |
| The proposal needs more discussion (see comments field) | |
| Disagree with the proposal | |
| Neutral - will accept the consensus of the group |
(1 response didn't contain an answer to this question)
Details
| Responder | Proposal for 3.10.3 Move Viewport to Focus | Comments 3.10.3 |
|---|---|---|
| Kelly Ford | Accept the proposal | |
| Simon Harper | Accept the proposal | |
| Greg Lowney | ||
| Kimberly Patch | Accept the proposal |
6. Proposal for 3.10.4 Resizable
See 3.10.4 Resizable Intent, Examples and Related Resources.
Summary
| Choice | All responders |
|---|---|
| Results | |
| Accept the proposal | 3 |
| Recommend changes (see comments field) | |
| The proposal needs more discussion (see comments field) | |
| Disagree with the proposal | |
| Neutral - will accept the consensus of the group |
(1 response didn't contain an answer to this question)
Details
| Responder | Proposal for 3.10.4 Resizable | Comments 3.10.4 |
|---|---|---|
| Kelly Ford | Accept the proposal | |
| Simon Harper | Accept the proposal | |
| Greg Lowney | ||
| Kimberly Patch | Accept the proposal |
7. Proposal for 3.10.5 Scrollbars
See 3.10.5 Scrollbars Intent, Examples and Related Resources.
Summary
| Choice | All responders |
|---|---|
| Results | |
| Accept the proposal | 3 |
| Recommend changes (see comments field) | |
| The proposal needs more discussion (see comments field) | |
| Disagree with the proposal | |
| Neutral - will accept the consensus of the group |
(1 response didn't contain an answer to this question)
Details
| Responder | Proposal for 3.10.5 Scrollbars | Comments 3.10.5 |
|---|---|---|
| Kelly Ford | Accept the proposal | |
| Simon Harper | Accept the proposal | |
| Greg Lowney | ||
| Kimberly Patch | Accept the proposal |
8. Proposal for 3.10.8 Do Not Take Focus
See 3.10.8 Do Not Take Focus Intent, Examples and Related Resources.
Summary
| Choice | All responders |
|---|---|
| Results | |
| Accept the proposal | 2 |
| Recommend changes (see comments field) | |
| The proposal needs more discussion (see comments field) | |
| Disagree with the proposal | |
| Neutral - will accept the consensus of the group |
(2 responses didn't contain an answer to this question)
Details
| Responder | Proposal for 3.10.8 Do Not Take Focus | Comments 3.10.8 |
|---|---|---|
| Kelly Ford | Accept the proposal | |
| Simon Harper | Accept the proposal | |
| Greg Lowney | ||
| Kimberly Patch |
9. Proposal for 3.10.9 Stay on Top
See 3.10.9 Stay on Top Intent, Examples and Related Resources.
Summary
| Choice | All responders |
|---|---|
| Results | |
| Accept the proposal | 2 |
| Recommend changes (see comments field) | |
| The proposal needs more discussion (see comments field) | |
| Disagree with the proposal | |
| Neutral - will accept the consensus of the group |
(2 responses didn't contain an answer to this question)
Details
| Responder | Proposal for 3.10.9 Stay on Top | Comments 3.10.9 |
|---|---|---|
| Kelly Ford | Accept the proposal | |
| Simon Harper | Accept the proposal | |
| Greg Lowney | ||
| Kimberly Patch |
10. Proposal for 3.10.10 Close Viewport
See 3.10.10 Close Viewport Intent, Examples and Related Resources.
Summary
| Choice | All responders |
|---|---|
| Results | |
| Accept the proposal | 2 |
| Recommend changes (see comments field) | |
| The proposal needs more discussion (see comments field) | |
| Disagree with the proposal | |
| Neutral - will accept the consensus of the group |
(2 responses didn't contain an answer to this question)
Details
| Responder | Proposal for 3.10.10 Close Viewport | Comments 3.10.10 |
|---|---|---|
| Kelly Ford | Accept the proposal | |
| Simon Harper | Accept the proposal | |
| Greg Lowney | ||
| Kimberly Patch |
11. Proposal for 3.10.11 Same UI
See 3.10.11 Same UI Intent, Examples and Related Resources.
Summary
| Choice | All responders |
|---|---|
| Results | |
| Accept the proposal | 2 |
| Recommend changes (see comments field) | |
| The proposal needs more discussion (see comments field) | |
| Disagree with the proposal | |
| Neutral - will accept the consensus of the group |
(2 responses didn't contain an answer to this question)
Details
| Responder | Proposal for 3.10.11 Same UI | Comments 3.10.11 |
|---|---|---|
| Kelly Ford | Accept the proposal | |
| Simon Harper | Accept the proposal | |
| Greg Lowney | ||
| Kimberly Patch |
12. Proposal for 3.10.12 Indicate Viewport Position
See 3.10.12 Indicate Viewport Position Intent, Examples and Related Resources.
Summary
| Choice | All responders |
|---|---|
| Results | |
| Accept the proposal | 2 |
| Recommend changes (see comments field) | |
| The proposal needs more discussion (see comments field) | |
| Disagree with the proposal | |
| Neutral - will accept the consensus of the group |
(2 responses didn't contain an answer to this question)
Details
| Responder | Proposal for 3.10.12 Indicate Viewport Position | Comments 3.10.12 |
|---|---|---|
| Kelly Ford | Accept the proposal | |
| Simon Harper | Accept the proposal | |
| Greg Lowney | ||
| Kimberly Patch |
More details on responses
- Kelly Ford: last responded on 13, May 2010 at 16:47 (UTC)
- Simon Harper: last responded on 13, May 2010 at 16:59 (UTC)
- Greg Lowney: last responded on 13, May 2010 at 17:06 (UTC)
- Kimberly Patch: last responded on 13, May 2010 at 17:08 (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