W3C home > Mailing lists > Public > public-mobile-a11y-tf@w3.org > July 2015

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

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Mon, 27 Jul 2015 22:02:31 +0100
To: public-mobile-a11y-tf@w3.org
Message-ID: <55B69C67.6080501@splintered.co.uk>
Regarding Detlev's suggested

 > 2.5.2 Single Taps and Long Presses Revocable: Interface elements that 
require a single tap or a long press as input will only trigger the 
corresponding event when the finger is lifted inside that element. (Level A)

I like the concept, but the wording that follows (requiring that things 
only trigger if touch point is still wihin the same element) is overly 
specific/limiting in my view. Also, it is partly out of the developer's 
control. For instance, in current iOS and Android, touch events have a 
magic "auto-capture" behavior: you can start a touch sequence on an 
element, move your touch point outside of the element, and release 
it...it will still fire touchmove/touchend events (but not click, 
granted). Pointer Events include an explicit feature to capture pointers 
and to emulate the same behavior as touch events. However, it would be 
possible to make taps/long presses revocable by, for instance, prompting 
the user with a confirmation dialog as a result of a tap/press (if the 
action is significant/destructive in particular). This would still 
fulfill the "revocable" requirement, just in a different way to "must be 
lifted inside the element".

In short: I'd keep the principle of "revocable" actions, but would not 
pin down the "the finger (touch point, whatever...keeping it a bit more 
agnostic) is lifted inside the element".

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, 27 July 2015 21:02:57 UTC

This archive was generated by hypermail 2.3.1 : Monday, 27 July 2015 21:02:57 UTC