Follow

The state of linux screen reader support seems to b3 totally absent at the lowest levels and embarrasing in userspace.

I need some simple low level interfaces for creating a framebuffer-like device for audio, plus a decent TTS engine.

I was hopping for something in coreboot. But there's nothing useful there and, to rub more salt into the wound, coreboot exposes a complex audio interface for platform independent drivers with a full specification costs a fortune in OSS money

1/2

To recap:

1) no screenreader support at startup

2) nothing inside the firmware settings (≈BIOS)

3) in GRUB, from what I've read, you get some beeps in one distro and you could maybe add something extra on top, but forget about encryption passwords, there's nothing hide here.

4) in most cases you get the screen reader after login, resolvable.

5) everything else is painful to use, even CLI tools, because they work exactly like those controlled by telegraph typewritters.

2/3

6) the developer tools are practically nonexistent.

All these extra issues might sound irrelevent in the short term, because apps need to be accessible, but without a solid foundation you can't build anything.

So, new POSIX proposal for extra file descriptors, and a way to process the structured data and send it to other hardware or software for improved accessibility and also to the current stdout, if needed.

What have I gotten myself into?

Sign in to participate in the conversation
XXX

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!