RE: Action-2036 aria-keyshortcuts

Jason, you wrote:
>Some screen readers, on the other hand, 
>aren't good at avoiding key combinations likely to be used by applications, 
>which is a reason for using role="application" where necessary 
>and for users to be aware of "pass-through" commands. 
>I think this issue deserves a cautionary note in the spec.

Could you please provide some specific examples? I don't know that I have seen this type of conflict persist for long. Typically, screen reader developers regard them as screen reader bugs.

BTW, We have re-written the application role in a way that removes any language that would encourage authors to use it in the way you describe. Instead of attempting to manipulate the keyboard behavior of screen readers, the new language encourages authors to develop widgets that comply with the ARIA specification. Then, screen readers that support the specification will behave in a way that they believe is most suitable for interoperability given that particular screen reader's UX paradigm. It is not up to the author to force the screen reader into a specific model of interoperability. So, I would not support adding language back into the spec that would continue to promote inappropriate use of the application role.

Matt King

-----Original Message-----
From: White, Jason J [mailto:jjwhite@ets.org] 
Sent: Thursday, April 7, 2016 1:03 PM
To: Matt King <a11ythinker@gmail.com>; 'Joseph Scheuhammer' <clown@alum.mit.edu>; 'Richard Schwerdtfeger' <richschwer@gmail.com>; 'ARIA' <public-aria@w3.org>
Subject: RE: Action-2036 aria-keyshortcuts



>-----Original Message-----

>WRT user agent conflicts, most browsers use ctrl+s for saving the page, 
>but lots of online editors use ctrl+s to save the online document in 
>the cloud. This does not create any loss of user agent functionality 
>because it is very easy and efficient to use a browser menu to navigate to the user agent function.

If you handle a key event in a script and prevent the default action, is this guaranteed to override whatever the user agent assigns to that key combination? If so, then I would agree with Matt that it's a question of author guidance.

Some screen readers, on the other hand, aren't good at avoiding key combinations likely to be used by applications, which is a reason for using role="application" where necessary and for users to be aware of "pass-through" commands. I think this issue deserves a cautionary note in the spec.

VoiceOver under OS X and ChromeVox are particularly good at assigning commands to key combinations that applications are unlikely to use.


________________________________

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 Thursday, 7 April 2016 20:26:54 UTC