11140 2010-10-25 17:24:22 +0000 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 sp 2014-05-01 15:48:57 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other CLOSED MOVED http://www.whatwg.org/specs/web-apps/current-work/#top a11y, a11ytf, a11y_focus P3 normal --- 10888 23613 23615 1 contributor chaals ayg chaals cooper hans.hillen ian laura.lee.carlson lwatson mark.sadecki+w3c mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 41733 0 contributor 2010-10-25 17:24:22 +0000 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 42727 1 cooper 2010-11-23 16:49:20 +0000 Bug triage sub-team thinks this issue has accessibility implications and wants the HTML A11Y TF to review in context of the keyboard access work. Indicating that this bug blocks 10888 as we think resolution of this bug is important to the accessibility work. 43730 2 ian 2011-01-01 08:14:36 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: Support for keywords to reference specific things, e.g. gestures or special keys (like F1), is something that is intentionally left open for a future version, but before we go there we really need more experience with the changes we've done so far. 52521 3 mike 2011-08-04 05:02:14 +0000 mass-moved component to LC1 78558 4 chaals 2012-11-20 23:53:14 +0000 I agree with Hixie. I certainly don't think that mapping a US keyboard in words is a particularly good approach - it gets us closer to the problems seen in the use of javascript to create keyboard interfaces, and that strikes me as a net loss. As for gestures, etc, the world is probably ready to research using them in the context of accesskeys - Opera and others have had ways of associating page actions to gestures for many years - but I don't think we are ready to try and standardise something for HTML. 95235 5 mark.sadecki+w3c 2013-10-23 20:07:38 +0000 a11ytf decision to move to HTML.next: http://www.w3.org/2013/10/17-html-a11y-minutes.html#item04 New bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=23615