+++ This bug was initially created as a clone of Bug #11140 +++

Section: http://www.whatwg.org/specs/web-apps/current-work/#top

Comment:
Subject: Physical Keys and Gestures for "accesskey" attribute

The use of ASCII/Unicode code points for key binding has numerous well-known
drawbacks. There are vital physical keyboard keys with no Unicode
representation. Even for the main alphabet keys specifying a stabile physical
location based on ergonomic considerations, regardless of keyboard mapping,
may be desirable. Unicode keybinding is useful for mnemonic keys however.

So for "accesskey" there should be a complete set of keywords representing the
physical keyboard keys -- referenced based on the locations on U.S. standard
keyboards, with names like "jKey", "slashKey", "leftArrow", "capsLock". All
keys should be represented including alphabet keys, F-keys, modifier keys, cap
lock, etc., and there should be syntax for indicating simultaneous key presses
(e.g. Control + uparrow).

A set of "media" keys would also be highly desirable (e.g. keyboard
volume/mute keys bindable to controls of an HTML5 video interface) although
this may not be standardizable.

But keys are so 2009. We of course also now need keywords for swipe gestures,
e.g:

[a href="page_2.html" accesskey="rightArrow horizLeftwardSwipe"]Turn Page[/a].

Posted from: 75.36.155.97