FW: ACTION-1642: New aria-kbdshortcuts property (for Issue 711)

Specifically copying the HTML-a11y TF, who may not always see PF-bound
emails.

Related to the @accesskey discussion underway. Coordination will be critical
here, as the same open questions exist for both efforts (discoverability,
alternate mapping options, etc.) .

JF


> -----Original Message-----
> From: Joseph Scheuhammer [mailto:clown@alum.mit.edu]
> Sent: Wednesday, June 10, 2015 8:24 AM
> To: public-pfwg@w3.org
> Subject: Re: ACTION-1642: New aria-kbdshortcuts property (for Issue 711)
> 
> > Please review this proposal based on a proposal from Dominic Mazzoni
> > for the Thursday ARIA call. We may come up for another name for this
> > ... like aria-shortcuts, aria-key, or aria-keygboardshortcuts:
> 
> Some thoughts and questions:
> 
> 1. Name: I suggest aria-hotkey.
> 
> 2. Discoverability -- how do users find out what the key combinations are?
> 
> 3.  The spec text says that if the control is invisible, then its keyboard
shortcut
> does not trigger the action.  This will exclude menu items within a menu
that is
> not popped open.  That is different from how menuitems work on the
desktop;
> for example, cmd+s on a Mac activates the "File" menu's "Save" menuitem
even
> when the menu and menuitem are invisible.
> 
> 4. How do aria-kbdshortcuts apply in the case of touch interfaces?
> 
> 5.  How does this differ from accesskey [1], i.e. what problem does it
solve that
> accesskey doesn't?  I think part of the answer is that aria-kbdshortcuts
includes
> the modifier keys, whereas acceskey doesn't, which is clearer.
> 
> 6.  How does aria-kbdshortcuts interact with accesskey?  Which one wins if
an
> element has both?
> 
> [1]
> http://www.w3.org/html/wg/drafts/html/master/editing.html#assigned-
> access-key
> 
> --
> ;;;;joseph.
> 
> 'Array(16).join("wat" - 1) + " Batman!"'
>             - G. Bernhardt -
>

Received on Wednesday, 10 June 2015 16:03:22 UTC