- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 31 Mar 2016 23:17:46 +0100
- To: public-mobile-a11y-tf@w3.org
On 31/03/2016 21:13, Chris McMeeking wrote: > I would propose making this a Triple or Double A requirement, and having > the success criterion read very similar to what it does now. However, > say something about: Users should have the ability to define whether > selection (onClick events in web speak) occurs on touch down, or on > touch up. This would satisfy both users. It certainly satisfies Type 1 > users better than the current requirement. Should that not be something left up to the user agent (so UAAG)? Otherwise you're essentially requiring every site/app to provide some settings dialog/screen. Activation should happen on click (to satisfy situations where a user is not using touchscreen, but a keyboard or keyboard-like interface which may not necessarily fire fake touch events - see some of the cases in http://patrickhlauke.github.io/touch/tests/results/#mobile-tablet-touchscreen-assistive-technology-events and http://patrickhlauke.github.io/touch/tests/results/#mobile-tablet-keyboard-mouse-events) as a general approach. 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 Thursday, 31 March 2016 22:18:12 UTC