- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Tue, 10 Sep 2019 19:22:42 +0100
- To: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
On 10/09/2019 19:04, Jonathan Avila wrote: > I agree with Patrick and this is what I entered into IRC. This is meant to address situations including touch screens or other systems where it's difficult to convert what the user wants to do into a keyboard interface. In theory alt+shift+ something or arrows provide access -- but in practical reality it's difficult to get these commands issued from different types of assistive technology including those mobile devices such as iOS. It's not immediately clear though that this also supposedly covers AT scenarios like VoiceOver on iOS or similar. In my initial reading of the SC text, it didn't seem to be the case (unless you count touch+AT scenario as a "single pointer", which is not quite accurate I'd say / stretches that definition a bit). > Ideally each control would have actions associated with an accessibility API an action menu could be brought up allow the user to choose from the actions -- much like assistive touch or switch control does on iOS. However, the level of support to communicate such actions programmatically is not fully implemented or supported across today's technology. Noting that the drag'n'drop stuff from ARIA 1.0 was dropped (hah) in ARIA 1.1 exactly because of a lack of proper support. P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Tuesday, 10 September 2019 18:23:06 UTC