- From: James Teh <jamie@nvaccess.org>
- Date: Wed, 24 Feb 2016 08:44:59 +1000
- To: Joanmarie Diggs <jdiggs@igalia.com>, IA2 List <Accessibility-ia2@lists.linux-foundation.org>
- Cc: ARIA Working Group <public-aria@w3.org>
- Message-ID: <56CCE0EB.6040003@nvaccess.org>
Hi Joanie, This is one of those cases where IA2 and ATK are going to differ. This time, it's because MSAA (on which IA2 is based) already has an accKeyboardShortcut property <https://msdn.microsoft.com/en-us/library/windows/desktop/dd318482%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396> which just exposes a keyboard shortcut. I think this lends itself well to exposing aria-kbdshortcuts. Thanks, Jamie On 24/02/2016 6:02 AM, Joanmarie Diggs wrote: > Hey all. > > We need to come up with mappings for aria-kbdshortcuts for ATK/AT-SPI2 > and IA2. And, unlike aria-errormessage, I got nothing (or almost nothing). > > When the feature and question of mappings was first raised, I was > thinking it could be mapped via the Action interface. At least in the > case of my platform, that's where keyboard shortcuts are exposed. But > those shortcuts are associated with an action which can be performed by > the Action interface. And that's not the case with aria-kbdshortcuts. As > the spec states: > > <quote> > Adding the aria-kbdshortcuts attribute to an element does not change the > behavior of the user agent by mapping the specified keyboard shortcuts > to the triggering of the element's activation function. It is still up > to the application to implement support for the keyboard shortcuts. The > aria-kbdshortcuts attribute exposes the fact that these shortcuts exist > so that assistive technologies can communicate this information to users. > </quote> > > So if it's exposed via the action interface, we'd have the shortcut and > a name, but we'd have to know (and user agents would have to expose) > that the action might not be something we could actually perform. With > respect to the latter, on the surface it seems easy because, at least on > my platform, atk_action_do_action() returns a boolean reflecting > success. However, in practice, at least some implementors always return > true because they don't want performing an action to be blocking. In > other words, the return value is useless. > > So.... Do we map this property via the Action attribute and just deal > with the fact that we cannot perform actions, or.... Something else? > > --joanie > _______________________________________________ > Accessibility-ia2 mailing list > Accessibility-ia2@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 -- James Teh Executive Director, NV Access Limited Ph +61 7 3149 3306 www.nvaccess.org Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess SIP: jamie@nvaccess.org
Received on Tuesday, 23 February 2016 22:45:23 UTC