RE: Rough draft of some success criteria for a extension guideline "Touch accessible"

> does this imply that interfaces need to be made to also work just with an activation/double-tap ? i.e., does double-tap count in this context as a "gesture"?

In theory I think this would benefit people from prosthetics too.  For example, many apps support zoom by double tapping without requiring a pinch.  You should be able to control all actions from touch (e.g. through an API) and also through the keyboard.  But I think it would be too constrictive to require on tap, double tap, long tap, etc.  Since screen readers and the API support actions through rotors and other gestures it would seem that API based and keyboard access would be sufficient.  But you bring up a good point that while this might make sense on native -- but mobile web apps don't have a good way without Indie UI to expose actions to the native assistive technologies.  This is a key area that needs to be addressed by other groups and perhaps may be addressed by other options such as WAPA -- but we do need to be careful and perform some research as the abilities we need may not be yet supported or part of a mature enough specification.

Jonathan

-- 
Jonathan Avila
Chief Accessibility Officer
SSB BART Group 
jon.avila@ssbbartgroup.com

703-637-8957 (o) 
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter

-----Original Message-----
From: Patrick H. Lauke [mailto:redux@splintered.co.uk] 
Sent: Thursday, August 13, 2015 2:13 PM
To: public-mobile-a11y-tf@w3.org
Subject: Re: Rough draft of some success criteria for a extension guideline "Touch accessible"

On 13/08/2015 19:06, David MacDonald wrote:
>  >2.5.1 Touch: All functionality of the content is operable through 
> touch gestures. (Level A)
>
> Suggested friendly amendment:
>
> 2.5.1 Touch: All functionality of the content is operable through 
> touch gestures with and without system assistive technology activated. 
> (Level A)
>
> I think this will address my concern that often touch gestures don't 
> work when VoiceOver is activated.

As it's not possible to recognise gestures when VoiceOver is enabled, as VO intercepts gestures for its own purposes (similar to how desktop AT intercept key presses) unless the user explicitly uses a pass-through gesture, does this imply that interfaces need to be made to also work just with an activation/double-tap ? i.e., does double-tap count in this context as a "gesture"? If not, it's not technically possible for web pages to force pass-through (no equivalent to role="application" for desktop/keyboard handling)...

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, 17 August 2015 01:36:25 UTC