- From: Matt King <a11ythinker@gmail.com>
- Date: Sat, 19 Nov 2016 08:49:41 -0800
- To: "'Bryan Garaventa'" <bryan.garaventa@ssbbartgroup.com>, "'ARIA Working Group'" <public-aria@w3.org>
The intent is focusable only. Where the spec says: > Indicates keyboard shortcuts that an author has implemented to activate or give focus to an element. It would probably be more clear if it said "the element" instead of "an element". But, it means that you put aria-keyshortcuts on the element that will get activated or focused. You can only activate or focus an element if it is focusable. Compare this to the definition of other properties that use the term "an element". For example, haspopup: > Indicates the availability and type of interactive popup element, such as menu or dialog, > that can be triggered by an element. Matt -----Original Message----- From: Bryan Garaventa [mailto:bryan.garaventa@ssbbartgroup.com] Sent: Friday, November 18, 2016 4:50 PM To: ARIA Working Group <public-aria@w3.org> Subject: question about aria-keyshortcuts Hi, Is aria-keyshortcuts supposed to only be used on focusable elements, or on any element? The spec is not clear on this. Also, if it is acceptable on non-focusable elements, how is this to be conveyed to AT users? Thanks, Bryan Bryan Garaventa Accessibility Fellow SSB BART Group, Inc. bryan.garaventa@ssbbartgroup.com 415.624.2709 (o) www.SSBBartGroup.com
Received on Saturday, 19 November 2016 16:50:15 UTC