Re: aria-keyshortcuts

Hi Jason, 

I wrestled with this as well. The problem with hidden content is that it is not mapped to platform accessibility API services. So, if a menu is in the DOM with display:none no AT will know about it.

Potentially, we could have the handler also triggered from the main document. IOW they both trigger the same function. However, you will not learn about what the keyboard shortcut does until you discover it visibly when it is associated with an element in the accessibility tree.   

Rich

Rich Schwerdtfeger
Round Rock, TX

> On Mar 10, 2016, at 2:35 PM, White, Jason J <jjwhite@ets.org> wrote:
> 
> This is a good draft.
>  
> Suppose the shortcut applies to a command that is only otherwise available from deep within a menu hierarchy. For example, it could be an “insert new footnote” command in a document editor.
>  
> I would interpret the shortcut as applying to the document which is being edited, and therefore the fact that the “add footnote” option is not visible when the shortcut is invoked wouldn’t violate the provision according to which: 
> “Authors
> must ensure that when elements having aria-keyshortcuts are invisible, hidden, or marked disabled those keyboard shortcuts are unavailable.”
>  
> Even though it is true that there is a menu option (not currently visible) that the shortcut invokes.
>  
> Of course, a case could be made for attaching the aria-keyshortcut property to the menu option so that the user is informed of it when they traverse the menu. If the property is placed on the menu option rather than on the widget containing the editable document then we do indeed have a problem with the above wording.
>  
>  
> 
> This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.
> 
> 
> Thank you for your compliance.
>