- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Mon, 4 Jul 2016 20:14:34 +0100
- To: public-mobile-a11y-tf@w3.org
On 04/07/2016 18:49, Jonathan Avila wrote: >> ### 2.1.1 Non-pointer: All functionality of the content is operable >> through accessibility supported non-pointer input interfaces (such >> as keyboards), without requiring specific timings for individual >> interactions, except where the underlying function requires input >> that depends on the path of the user's movement and not just the >> endpoints. > (Level A) > > Would this allow one non-pointer method to work such as speech input? > Or does this require all non-pointer input methods to work? The term > accessibility supported non-pointer input is not clear enough. I > think what you are saying is an accessibility API and keyboard > input. To clarify: I'm meaning ALL (not just "one will do"). And yes, an accessibility API and keyboard input, but also inputs which are not exactly keyboard-like (they don't emulate a keyboard as such, don't actually fire "fake" keyboard events, but interact directly - via the accessibility API? - with the UA to move focus, activate controls, etc). 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 Monday, 4 July 2016 19:15:04 UTC