RE: question about aria-keyshortcuts

I made these two points in my response to James's post, but I think they are worth repeating:

1. Focusable/activatable items do not need to be in the tab sequence. They could have tabindex=-1 or be buried in a composite, such as a menu,  that uses activedescendant.

2. Dynamically listing shortcuts in context is another case where relying on assistive technologies instead of web authors limits utility. I'd rather see web authors do this so consistently that AT never see the need. Thus, the functionality is available to everyone. I raised issue 167 to address this in the authoring practices.
https://github.com/w3c/aria-practices/issues/167

I don't think it would be good if keyshortcuts became another one of those features that authors see as important only to screen reader users. 

Matt

-----Original Message-----
From: Rich Schwerdtfeger [mailto:richschwer@gmail.com] 
Sent: Friday, November 25, 2016 4:41 PM
To: Joseph Scheuhammer <clown@alum.mit.edu>
Cc: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>; ARIA Working Group <public-aria@w3.org>
Subject: Re: question about aria-keyshortcuts

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 Tuesday, 29 November 2016 00:44:30 UTC