comment #55

#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)
---------------------
Right. This is confusing. Seems to artifact of many 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. Always have to have a reset to default

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.

Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964

Received on Thursday, 7 May 2009 16:36:13 UTC