- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 30 Jun 2016 12:18:42 +0100
- To: gregg@raisingthefloor.org, public-mobile-a11y-tf@w3.org
- Cc: team-wcag-editors@w3.org
On 30/06/2016 11:31, Detlev Fischer wrote: > One difference between sequential navigation via swiping and keyboard > sequential navigation (tabbing, arrowing) is predictability. In > several user tests we have experienced issues of focus loss or > accidental focus jumps even with users who know the swipe gestures > and can in other circumstances apply them correctly. Swiping > (especially with Android / Talkback) often resets the focus to what > happens to be at the position where the finger came down. This is > partly due to problems of touch implementation (especially compared > with the better implemetation under iOS/Voiceover), partly due to > processing speed (test devices were Moto E, Galaxy Note 3, Nexus 4, > etc, so not the latest and fastest hardware). > > This may still not be a general reason to keep keyboard and touch > sequential navigation apart - just saying... To me, that's bad/buggy user agent/AT implementation of the navigation mechanism. Nothing that an author can account for. 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, 30 June 2016 11:19:10 UTC