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

kbdshortcut and accessKeyLabel

From: Chaals McCathie Nevile <chaals@yandex-team.ru>
Date: Thu, 03 Mar 2016 11:54:18 +0100
To: "ARIA Working Group" <public-aria@w3.org>
Message-ID: <op.ydqwksmrs7agh9@widsith.local>
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 10:54:53 UTC

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