W3C home > Mailing lists > Public > public-aria@w3.org > March 2016

Re: aria-keyshortcuts

From: null) (null <schwer@yahoo.com>
Date: Fri, 11 Mar 2016 21:14:15 -0600
Cc: Dominic Mazzoni <dmazzoni@google.com>, ARIA Working Group <public-aria@w3.org>, James Craig <jcraig@apple.com>
Message-Id: <BC56160D-85B0-4558-8A8B-877EF9B28FC1@yahoo.com>
To: "White, Jason J" <jjwhite@ets.org>
I think we are covered until more comments come in :-)

I sent it off to the tech lead for i18n at IBM yesterday.

Rich

Sent from my iPhone

> On Mar 11, 2016, at 6:23 PM, White, Jason J <jjwhite@ets.org> wrote:
> 
> Thank you, Rich. Your revised draft addresses all of my concerns (and, I hope, yours too).
>  
> From: Rich Schwerdtfeger [mailto:schwer@yahoo.com] 
> Sent: Friday, March 11, 2016 6:03 PM
> To: White, Jason J
> Cc: Dominic Mazzoni; ARIA Working Group; James Craig
> Subject: Re: aria-keyshortcuts
>  
> Hi Jason, 
>  
> Here is a revised draft for aria-keyshortcuts:
> https://rawgit.com/w3c/aria/action2036/aria/aria.html#aria-keyshortcuts
>  
> Does this address your issues? The revised text is in the last paragraph preceding the editor’s note.
>  
> Rich
>  
> Rich Schwerdtfeger
> Round Rock, TX
>  
> On Mar 11, 2016, at 8:14 AM, White, Jason J <jjwhite@ets.org> wrote:
>  
> Hi Rich,
>  
> I think it’s reasonable to attach the aria-keyshortcut property to the (usually hidden) menu item. If the user digs into the menu, the shortcut will be discoverable (and discovered), as it will then be revealed to the platform accessibility API.
>  
> I think the author should be permitted (as is required under these circumstances) to allow the shortcut to operate globally.
>  
> Maybe loosen the requirement and say that there must be some sequence of UI operations that will reveal the shortcut to the user by making the element visible and hence available to accessibility APIs.
>  
> I agree this is not a straightforward problem and that the requirements for authors need to be clarified. It’s probably a combination of ensuring that the text in the spec is appropriate and handling the issue properly in the authoring practices.
>  
>  
> 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.
>  
> 
> 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.
> 

Received on Saturday, 12 March 2016 03:14:48 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:20 UTC