- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Tue, 15 Dec 2015 14:18:17 +0000
- To: Jonathan Avila <jon.avila@ssbbartgroup.com>, "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
On 15/12/2015 13:36, Jonathan Avila wrote: [...] > Your examples of the sliders are good -- but > that IMO is not a single tap gestures but a tap and slide. So > perhaps just keeping this single or long tap gestures is safest. Agree. > I do run into this issue often on certain mobile apps and certain > sites where I'll put my finger down to perform to do something and > the action is triggered right away on the thing I wasn't trying to > affect. > > Have you looked at the iOS settings for touch accommodations? They > seem to mirror what we are trying to say. I shamefully admit that I hadn't looked into those. But now that I have, this makes me wonder: since there are two conflicting scenarios here - a user who WANTS to activate a control but may lack the dexterity to keep their finger over the control, and a user who accidentally tapped down on a control and DOESN'T want to activate it - is it right for an SC to prefer one scenario over another and make the other one non-conformant? Or is the whole problem (depending on which scenario you're in) one that is best left to UAs to address (so a UAAG one)? 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, 15 December 2015 14:18:44 UTC