[BRLTTY] Call for testing: Touch navigation on Handy Tech devices

Mario Lang mlang at delysid.org
Tue Jul 26 06:13:14 EDT 2016


Lars Bjørndal <lars at lamasti.net> writes:

> I'd like to thank you a lot for working on BRLTTY to support ATC
> technology.

You're welcome.  It took me far too long to get this done actually.

> While reading continuously, the scrolling are functioning
> automatically most of the times. When it doesn't work, I'm not sure
> why.

ATC, as I understand it, is all about being fuzzy.  If you do light
reading (not much pressure with your fingers) ATC will eventually miss
some characters being touch.  Cranking the sensitivity up to maximum
does help here.  However, in my experience, you still occasionally
manage to touch a cell which is not reported back to the screen reader.
The algorithm inside BRLTTY which decides when a line has been read
completely keeps track of all fresh cells which do have dots set.
Whenever BRLTTY notices some of these cells have been touched, they are
set to "read".  When a certain treshold of read cells is reached, and
the last touched cell wase at the end of the set cells, auto forward is
executed.  So, if it doesn't work for you, there are three things you/we
can do:
1. Try explicitly touching one of the last letters on the display.
2. Set braille sensivitity to something more sensitive.
3. We can adjust the treshold in the source code to be more tolerant to
missed touched cells.

Since this rather crude approach is totally of my own invention, I'd be
happy to hear some feedback from Felix if this is a workable approach,
or if there are simple, non-proprietary things we could add to it to
make BRLTTY support ATC better on Linux and Android.

-- 
CYa,
  ⡍⠁⠗⠊⠕


More information about the BRLTTY mailing list