Delay at beginning of explore-by-touch

[GoogleCodeExporter]

Hi,

when touching the screen, there is a ~0.3 sec delay before anything is spoken.
This delay does not occur, when sliding the finger to the next item.
Hence, it does not seam to be caused by the speech engine but rather by 
talkback or the os.

It would be very useful to reduce this delay, as it significantly slows down 
the user interaction with the phone. This is especially true, when typing on 
the on-screen keyboard, as you have to wait 0.3 sec per letter before talkback 
announces, whether you have hit the right key.
If you have to write a 180 character sms, the delay adds up.

I tried to lower various delay values in the talkback source code, but did not 
find the one responsible for this delay.

Regards, Rudolf

Original issue reported on code.google.com by rudolfwe...@gmail.com on 29 Sep 2013 at 1:29

[GoogleCodeExporter]

I've noticed this too.  It's really, really bad.  It takes longer to register 
that I'm exploring by touch than to actually say whatever I'm touching.  Typing 
is a chore beyond all description, and general exploration is inconvenient.

Original comment by camlor...@gmail.com on 20 Oct 2013 at 6:11

[GoogleCodeExporter]

I believe there is a bit of delay introduced by the framework when assessing 
the nature of the finger movement on the screen, but I think it is necessary.  
Essentially our explore by touch state machine needs to capture several touch 
events to calculate the velocity of the touch point.  This is used to determine 
if the user is exploring or moving their finger quickly to perform an 
accessibility gesture.

We've made some changes in 4.4 that ensures these first several points are 
redelivered to the underlying application, which may marginally improve things.

Original comment by caseybur...@google.com on 5 Dec 2013 at 6:58

• Changed state: WontFix