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

Re: aria-keyshortcuts

From: Rich Schwerdtfeger <richschwer@gmail.com>
Date: Sat, 12 Mar 2016 07:38:43 -0600
Cc: public-aria@w3.org
Message-Id: <8260AC2F-9659-4783-A7DE-456B2A60219B@gmail.com>
To: James Nurthen <james.nurthen@oracle.com>
James, if you activate a text box it gets focus. 

I am just trying to get the text right before expanding the roles it applies to. I believe I have said that.

I don't want an access key replacement.

Rich

Sent from my iPhone

> On Mar 11, 2016, at 5:13 PM, James Nurthen <james.nurthen@oracle.com> wrote:
> 
> Rich,
> I still don't understand your resistance to allowing a keyboard shortcut to focus something within the page. It seems that by requiring activation you are limiting the ability of twitter (for example) to provide "/"as the shortcut to move to the search box or facebook to provide "p"to move focus to the "post a new status"field.
> 
> Why can this property not also allow focus to be moved to a field? I really don't understand why this is an issue.
> 
> Regards,
> James
> 
> 
>> On 3/11/2016 3:02 PM, Rich Schwerdtfeger wrote:
>> 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.
>>> 
> 
> -- 
> Regards, James
> <oracle_sig_logo.gif>
> James Nurthen | Principal Engineer, Accessibility
> Phone: +1 650 506 6781 | Mobile: +1 415 987 1918 | Video: james.nurthen@oracle.com 
> Oracle Corporate Architecture
> 500 Oracle Parkway | Redwood Cty, CA 94065 
> <green-for-email-sig_0.gif> Oracle is committed to developing practices and products that help protect the environment

Received on Saturday, 12 March 2016 13:39:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:58:22 UTC