- From: Rich Schwerdtfeger <richschwer@gmail.com>
- Date: Fri, 25 Nov 2016 18:40:50 -0600
- To: Joseph Scheuhammer <clown@alum.mit.edu>
- Cc: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>, ARIA Working Group <public-aria@w3.org>
Well stated Sent from my iPhone > On Nov 25, 2016, at 4:04 PM, Joseph Scheuhammer <clown@alum.mit.edu> wrote: > >> On 2016-11-18 7:50 PM, Bryan Garaventa wrote: >> Is aria-keyshortcuts supposed to only be used on focusable elements, or on any element? The spec is not clear on this. > >> From the spec: > "Indicates keyboard shortcuts that an author has implemented to activate > or give focus to an element." > > The second case, where the shortcut gives focus to an element, entails > that the element is focusable. An element cannot be focused if it is > not focusable. > > The first case regarding activation is less clear. Your concern is, I > believe, discoverability: if the element with the key shortcut is not > focusable, users cannot navigate to it to find out what the short cut > is. But, there should be a better way than a tedious tab-navigation of > elements to find the keyboard shortcuts. As James N. proposed elsewhere > in this thread, since the shortcuts are exposed in the accessibiilty > tree, it can be searched to find and list them. It will take a while > for ATs to start doing that. > > In the short term, it's good practice to make elements with > aria-keyshortcuts focusable for discoverability. In the long run, that > may not be necessary. > > -- > ;;;;joseph. > > 'Die Wahrheit ist Irgendwo da Draußen. Wieder.' > - C. Carter - > >
Received on Saturday, 26 November 2016 00:41:25 UTC