W3C home > Mailing lists > Public > public-aria@w3.org > March 2016

Re: kbdshortcut and accessKeyLabel

From: Gunderson, Jon R <jongund@illinois.edu>
Date: Thu, 3 Mar 2016 15:06:15 +0000
To: Chaals McCathie Nevile <chaals@yandex-team.ru>, ARIA Working Group <public-aria@w3.org>
Message-ID: <D2FDAECF.51CBB%jongund@illinois.edu>

Can you check the http://chaals.github.io link, it seems to be broken.


On 3/3/16, 4:54 AM, "Chaals McCathie Nevile" <chaals@yandex-team.ru> wrote:

>the spec should probably explain the relationship between kbdshortcut and
>the HTML DOM attribute accessKeyLabel. Although the latter is only
>implemented in Firefox, and I hope that it will actually change in HTML
>require a microsyntax that matches that of kbdshortcut, it has the useful
>property that instead of being an author aspiration it is normally a true
>indicator of what the shortcut is, and so far more useful to announce to
>accessibility APIs.
>See http://chaals.github.io/testcases/accesskey/index.html for a bunch of
>exceptions and bugs with it - there are various cases where
>doesn't work, mostly to do with the HTML5 definition of accesskeyŠ which
>fixed some things, but being unimplemented means it breaks badly in many
>See also:
>HTML issue 99 <https://github.com/w3c/html/issues/99> Only one
>implementation of accessKeyLabel - and the spec should be improved
>HTML issue 20 <https://github.com/w3c/html/issues/20> Authors should not
>use multiple values for `accesskey`
>Charles McCathie Nevile - web standards - CTO Office, Yandex
>  chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Thursday, 3 March 2016 15:07:03 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:20 UTC