Path-based gestures update

Hi David & everyone,

I’ve made some updates after the call yesterday, the paragraph you found difficult has been updated to:

Browsers on a touch screen device generally provide some default gestures that impact whether a path-based gesture is needed. For example, a web browser on a touch-screen devices might detect a vertical gesture and scroll the page. If a user places their finger on a slider thumb and moves up (to scroll down) that might not activate the slider (depending on implementation). If the user moves horizontally first then the slider could capture that gesture and ignore vertical movement, resulting in a path-based gesture. If you include touch-screen devices as accessibility supported then these types of interaction need testing with a touch screen as using a mouse in a similar way would not the same browser behaviour.

I’ve also added another diagram to differentiate free-form from path-based gestures, you might need to hard-refresh to see it:
https://raw.githack.com/w3c/wcag/PointerGesturesUnderstandingDragChanges/understanding/21/pointer-gestures.html


Is that better?

Kind regards,

-Alastair

--

www.nomensa.com<http://www.nomensa.com/>
tel: +44 (0)117 929 7333 / 07970 879 653
follow us: @we_are_nomensa or me: @alastc
Nomensa Ltd. King William House, 13 Queen Square, Bristol BS1 4NT

Company number: 4214477 | UK VAT registration: GB 771727411