RE: introduction and testing console screen reader

Hi all,
There is another screen reader in the ports collection called Yasr that may help you.
Install this along with eflite and give it a try to see what it can do for you.

At this point I have yet to seriously use FreeBSD natively with a console screen reader.
For the time being I just ssh from a Linux system and access the system this way.
I intend to take away the crutch and use a screen reader designed for that system soon to go along with NetBSD as well.



-----Original Message-----
From: owner-freebsd-accessibility@freebsd.org <owner-freebsd-accessibility@freebsd.org> On Behalf Of Hans Petter Selasky
Sent: Tuesday, March 28, 2023 2:48 PM
To: Chris Brannon <chris@the-brannons.com>; freebsd-accessibility@freebsd.org
Subject: Re: introduction and testing console screen reader

Hi Chris!

I'm glad to hear you got things working.

Yes, there is some room for improvement, and all comments and patches are welcome!

There should be more blind computer programmers, because one day some terribly bright light may appear in the sky and loads of people may become blind in a second. I've already made a deal with another blind person to commit the VT screen reader patches to FreeBSD in case of such a devestating event ;-)

--HPS

On 3/28/23 18:47, Chris Brannon wrote:
> Hi,
> I'm a blind person who has used Unix in some form or other since the 
> 90s, when I got my first shell account.  In 2000, I started running 
> Linux on my own hardware and I've used it exclusively since then.
> I've talked about trying FreeBSD on real hardware for a while now.  I 
> recently learned that there is a console screen reader in development, 
> and that was the encouragement I needed to install it on some bare metal.
> 
> I've installed FreeBSD and rebuilt the kernel with the vt patch that I 
> found on review.freebsd.org.  I've also compiled vtspeakd.
> It works!  I was able to log in at my console and mess around, with 
> spoken feedback.
> I'm not able to review the screen, so there's plenty of possibility 
> for improvement, but this looks like a promising first step.