- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Mon, 18 Apr 2016 21:06:14 +0100
- To: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
On 18/04/2016 20:44, David MacDonald wrote: > Guideline 2.5: Touch and Pointer: Make it easier for users to operate > touch and pointer functionality. > > The new language is: > > > 2.5.3 Up-Event Activation: Single touch and/or pointer > activation is triggered on the up-event, or has at least one of > the following is true (Level A): > > 1. confirmation is provided which can dismiss activation; or > 2. the action is reversible; or > 3. a mechanism is available to allow the user to trigger activation on > the up-event; or > 4. timing of the event is essential and waiting for the up-event would > invalidate the activity. > > Note: This is when platform assistive technology that remaps touch > gestures is */not /*turned on. What if I as developer am simply listening to the "click" event in JavaScript (and not specifically to any "up" events). Am I passing this? Whether the browser/platform fires the click on down or up is outside of my direct control. In most cases probably yes (click only fired when finger is lifted again from touchscreen / mouse button released), but not something I can guarantee/control. 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, 18 April 2016 20:06:37 UTC