RE: kbdshortcut and accessKeyLabel

Jon,

s/.io/.com

https://github.com/chaals/accesskey 

JF

> -----Original Message-----
> From: Gunderson, Jon R [mailto:jongund@illinois.edu]
> Sent: Thursday, March 3, 2016 9:06 AM
> To: Chaals McCathie Nevile <chaals@yandex-team.ru>; ARIA Working Group
> <public-aria@w3.org>
> Subject: Re: kbdshortcut and accessKeyLabel
> 
> Charles,
> 
> Can you check the http://chaals.github.io link, it seems to be broken.
> 
> Jon
> 
> 
> On 3/3/16, 4:54 AM, "Chaals McCathie Nevile" <chaals@yandex-team.ru>
> wrote:
> 
> >Hi,
> >
> >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
> >to 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
> >accessKeyLabel 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 places.
> >
> >See also:
> >
> >HTML issue 99 <https://github.com/w3c/html/issues/99> Only one
> >implementation of accessKeyLabel - and the spec should be improved
> >
> >and
> >HTML issue 20 <https://github.com/w3c/html/issues/20> Authors should
> >not use multiple values for `accesskey`
> >
> >cheers
> >
> >--
> >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:34:53 UTC