W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2013

[Bug 23615] New: 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

From: <bugzilla@jessica.w3.org>
Date: Wed, 23 Oct 2013 20:06:58 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-23615-2486@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23615

            Bug ID: 23615
           Summary: 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
           Product: HTML.next
           Version: unspecified
          Hardware: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
                OS: other
            Status: NEW
          Keywords: a11y, a11ytf, a11y_focus
          Severity: normal
          Priority: P3
         Component: default
          Assignee: chaals@yandex-team.ru
          Reporter: mark@w3.org
        QA Contact: public-html-bugzilla@w3.org
                CC: ayg@aryeh.name, chaals@yandex-team.ru,
                    contributor@whatwg.org, cooper@w3.org,
                    hans.hillen@gmail.com, ian@hixie.ch,
                    laura.lee.carlson@gmail.com, mike@w3.org,
                    public-html-a11y@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org, robin@w3.org
        Depends on: 11140
            Blocks: 23613, 10888

+++ 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

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 23 October 2013 20:07:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:45 UTC