W3C

Results of Questionnaire UAWG Survey for 4 June

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 2009-06-02 to 2009-06-26.

3 answers have been received.

Jump to results for question:

  1. Action-183 / Comment #55. (Re 4.1.10 **) Proposal
  2. Proposal on 4.1 Event Handlers.
  3. proposal for comment #63 splitting 4.1.5 into A for content shortcuts and AA for UI shortcuts

1. Action-183 / Comment #55. (Re 4.1.10 **) Proposal

From a proposal from Jim Allan. Email comments on Action 183

Current:

4.1.10 Specify preferred keystrokes: The user can override any keyboard shortcut including recognized author supplied shortcuts (e.g accesskeys) and user interface controls, except for conventional bindings for the operating environment (e.g., for access to help)

4.1.11 User Override of Accesskeys: The user can override any author supplied content keybinding (i.e. access key) that the user agent can *recognize*. The user must have an option to save the override of user interface keyboard shortcuts so that the rebinding persists beyond the current session. (Level AA)

Proposed

4.1.10 User Override of Author Keyboard Commands: The user can override any recognized author supplied keyboard shortcuts (e.g accesskeys). (Level A)

4.1.11: Keyboard Command Override Persistence: The user must have an option to save the override of all keyboard shortcuts so that the rebinding persists beyond the current session. (Level A) [this may be covered in 4.5.1 Save Settings)

4.1.12 Keyboard Command conflict: The user agent should inform the user when a specified keybinding in content or the user interface is missing from the user's keyboard and allow an override.

4.1.13 Keyboard Command Reset: The user has the option to restore all keyboard overrides to their default values.

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 1

Details

Responder Action-183 / Comment #55. (Re 4.1.10 **) ProposalComments
Kelly Ford Neutral - will accept the consensus of the group
Simon Harper Accept the proposal
Henny Swan Accept the proposal

2. Proposal on 4.1 Event Handlers.

From Jan Richards email of 21 May:

3.13 becoming "Provide access to interactivity information" (the text would parallel 3.3 "Provide access to relationship information")

It would keep it's current SCs.

Then we add:

3.13.X Perceive Event Handlers: The user has the option to be alerted to any input device event handlers (including those for pointing devices, voice, etc.) that are associated with the current content focus (Level A).

And:

4.1.X Operate Event Handlers: The user can activate, via the keyboard, any input device event handlers (including those for pointing devices, voice, etc.) that are associated with the current content focus (Level A).

Summary

ChoiceAll responders
Results
Accept the proposal 1
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

Details

Responder Proposal on 4.1 Event Handlers. Comments
Kelly Ford Neutral - will accept the consensus of the group
Simon Harper Accept the proposal
Henny Swan Neutral - will accept the consensus of the group

3. proposal for comment #63 splitting 4.1.5 into A for content shortcuts and AA for UI shortcuts

From a proposal from Greg Lowney. Email comments

Current:

4.1.5 Discovery of Keyboard Commands: User has the option to have any *recognized* direct keyboard commands displayed with their associated controls. (Level A)

Proposed

4.1.5 Present Direct Commands in Rendered Content: The user has the option to have any recognized direct commands (e.g. accesskey) in rendered content be presented with their associated elements (e.g. "[Ctrl+t]" displayed after a link whose accesskey value is "t", or an audio browser reading the value or label of a form control followed by "accesskey control plus t"). (Level A)

4.1.x Present Direct Commands in User Interface: The user has the option to have any direct commands (e.g. keyboard shortcuts) in the user agent user interface be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). (Level AA)

4.1.12 Keyboard Command conflict: The user agent should inform the user when a specified keybinding in content or the user interface is missing from the user's keyboard and allow an override.

Greg has extensive notes in his email at http://lists.w3.org/Archives/Public/w3c-wai-ua/2009AprJun/0067.html.

Summary

ChoiceAll responders
Results
Accept the proposal
Recommend changes (see comments field)
The proposal needs more discussion (see comments field) 3
Disagree with the proposal
Neutral - will accept the consensus of the group

Details

Responder proposal for comment #63 splitting 4.1.5 into A for content shortcuts and AA for UI shortcuts Comments
Kelly Ford The proposal needs more discussion (see comments field) Generally accept but there is overlap between this and Jim's item here.
Simon Harper The proposal needs more discussion (see comments field)
Henny Swan The proposal needs more discussion (see comments field)

More details on responses

  • Kelly Ford: last responded on 4, June 2009 at 16:04 (UTC)
  • Simon Harper: last responded on 9, June 2009 at 15:41 (UTC)
  • Henny Swan: last responded on 11, June 2009 at 15:38 (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