W3C WBS Home

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:

  1. Proposal for 5.3.5 Context Sensitive Help
  2. Proposal for 5.3.6 Appropriate Language
  3. Proposal for 3.10.1 Highlight Viewport
  4. Proposal for 3.10.2 Move Viewport to Selection
  5. Proposal for 3.10.3 Move Viewport to Focus
  6. Proposal for 3.10.4 Resizable
  7. Proposal for 3.10.5 Scrollbars
  8. Proposal for 3.10.8 Do Not Take Focus
  9. Proposal for 3.10.9 Stay on Top
  10. Proposal for 3.10.10 Close Viewport
  11. Proposal for 3.10.11 Same UI
  12. 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

ChoiceAll 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 HelpComments 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

ChoiceAll 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 LanguageComments 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

ChoiceAll 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 ViewportComments 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

ChoiceAll 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 SelectionComments 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

ChoiceAll 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 FocusComments 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

ChoiceAll 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 ResizableComments 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

ChoiceAll 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 ScrollbarsComments 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

ChoiceAll 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 FocusComments 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

ChoiceAll 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 TopComments 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

ChoiceAll 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 ViewportComments 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

ChoiceAll 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 UIComments 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

ChoiceAll 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 PositionComments 3.10.12
Kelly Ford Accept the proposal
Simon Harper Accept the proposal
Greg Lowney
Kimberly Patch

More details on responses

Non-responders

The following persons have not answered the questionnaire:

  1. Judy Brewer <jbrewer@w3.org>
  2. Jim Allan <jimallan@tsbvi.edu>
  3. Jan Richards <jrichards@ocadu.ca>
  4. Eric Hansen <ehansen@ets.org>
  5. Markku Hakkinen <mhakkinen@ets.org>
  6. Wayne Dick <wayneedick@gmail.com>
  7. Peter Parente <pparent@us.ibm.com>
  8. Simon Pieters <simonp@opera.com>
  9. Takeshi Kurosawa <kurosawa-takeshi@mitsue.co.jp>
  10. Alan Cantor <alan@cantoraccess.com>
  11. Jeanne F Spellman <jeanne@w3.org>
  12. he wen <rockywen@tencent.com>

Send an email to all the non-responders.


Compact view of the results / list of email addresses of the responders

WBS home / Questionnaires / WG questionnaires / Answer this questionnaire


Completed and maintained by Dominique Hazaël-Massieux (dom@w3.org) on an original design by Michael Sperberg-McQueen $Id: showv.php3,v 1.124 2014-10-06 13:46:23 dom Exp $. Please send bug reports and request for enhancements to dom@w3.org with w3t-sys@w3.org copied (if your mail client supports it, send mail directly to the right persons)