Re: Orca question

["Pawel L." <pltechmail@gmail.com>]

Hello,

David is right about lynx working in more blind-friendly way in Debian 
than in Slint since Debian comes with lynx.cfg preconfigured differently 
from Slint version.

In Slint it is necessary to turn cursor on and tune up few more settings 
to make it better with Speakup for instance.

I believe Didier mentioned in one of his email that Slint respects 
lynx's developer configuration or so and it should be up to a user to 
make any needed changes.

Best,

Pawel

On 2020-06-04 3:09 p.m., Didier Spaier wrote:
> Hi David,
>
> currently we ship lynx-2.9.0dev.4 in Slint, but I hardly understand why
> lynx itself would behave differently between Debian (which version?) and
> Slint on this regard, but maybe if your config file makes a difference.
>
> Anyway we need more information to investigate.
>
> Please attach your config file to your next message and tell with which
> console screen reader you observe this behavior: espeakup, speechd-up,
> fenrir?
>
> Also, please provide a link to a web page on which this issue appears,
> and post to or at least CC the Slint mailing list so we know if other
> Slint users encounter the same issue.
>
> Cheers,
> Didier
>
> Le 04/06/2020 à 19:29, David Hoff Jr a écrit :
> > You are correct, Lynx does work better when used from the command line, but in Slint, when using a screen reader, Lynx is not very usable. The Tab and Up/Down cursor keys are suppose to read only the link but instead the link and a lot of other information is spoken by the screen reader making it extremely difficult to determine where you are and what is being spoken. David Ring did send me a revised config file which I appreciated. I
> > currently use Lynx and Debian on an older netbook and it is very easy to
> > configure and use. Is it possible that Slint could reconfigure Lynx to
> > work in a similar fashion?