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

RE: aria-keyshortcuts

From: Schnabel, Stefan <stefan.schnabel@sap.com>
Date: Mon, 14 Mar 2016 08:40:22 +0000
To: Rich Schwerdtfeger <schwer@yahoo.com>, "White, Jason J" <jjwhite@ets.org>
CC: Dominic Mazzoni <dmazzoni@google.com>, ARIA Working Group <public-aria@w3.org>, James Craig <jcraig@apple.com>
Message-ID: <20eaff915ede4d689058bbe52605514a@DEWDFE13DE04.global.corp.sap>
Hi Rich,

Will the question how UA‘ s *may* (not should, not must) expose the keyshortcuts definitions to non-blind end users as part of their UI be handled in the APG later on? Because https://www.w3.org/TR/accname-aam-1.1/ isn’t a place for it since it is about API mapping.

Shouldn’t there be in the spec draft at least one sentence like “UA’s are free to render the keyshortcuts info as part of their UI or leave that to the page author”?

Regards
Stefan

From: Rich Schwerdtfeger [mailto:schwer@yahoo.com]
Sent: Samstag, 12. März 2016 00:03
To: White, Jason J <jjwhite@ets.org>
Cc: Dominic Mazzoni <dmazzoni@google.com>; ARIA Working Group <public-aria@w3.org>; James Craig <jcraig@apple.com>
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<mailto: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.

Received on Monday, 14 March 2016 08:40:54 UTC

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