W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2009

Proposal on Action 183:

From: Jim Allan <jimallan@tsbvi.edu>
Date: Wed, 27 May 2009 12:30:54 -0500
To: "'UAWG list'" <w3c-wai-ua@w3.org>
Message-ID: <038201c9def0$e4177670$ac466350$@edu>
This was Issue #55. (Re 4.1.10 **) 
Clarify difference between 4.1.10 vs. 4.1.11: 4.1.10 and 4.1.11 seem to
overlap and the difference between them is unclear. Were the two supposed to
be combined? First, 4.1.9 applies to UI only, whereas 4.1.10 applies to both
UI and rendered content (e.g. accesskey=). Second, 4.1.9 requires the user
be able to assign new shortcut keys, whereas 4.1.10 does not. (At least not
explicitly; see my other comment on the need to define "override" in these
contexts.) (Priority: 1 High) 

----------------------------------------------------

Old: 

4.1.10 Specify preferred keystrokes: The user can override any keyboard
shortcut including recognized
<http://www.w3.org/WAI/UA/2009/ED-UAAG20-20090506/#def-recognize>  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)

--------------------------------------------------

Propose: 
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 of edits

4.1.10 Removed clause revering to UI...that is covered in 4.1.9
4.1.11 change title, made it inclusive of all overrides
4.1.12 NEW. Needed when author or UA extension provides keybinding not
available on user's device.
4.1.13. New. Should always have to have a reset to default
Received on Wednesday, 27 May 2009 17:35:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:52:13 GMT