[BRLTTY] Footsteps towards better accessibility in Linux

Samuel Thibault samuel.thibault at ens-lyon.org
Tue May 6 20:31:18 UTC 2025


Aura Kelloniemi, le mar. 06 mai 2025 23:11:47 +0300, a ecrit:
> I think that we could discuss decopuling these activites – i.e. separating
> BrlAPI server out of BRLTTY (possibly together with some additional features).

Currently it can already be decoupled. That's how it works for reading
terminals on X11/wayland.

> BRLTTY would then always communicate with the display(s) through BrlAPI.

What would be the benefit, compared to the additional latency?

> Anyways, my current view is that we should build APIs that are generic and
> screen-reader agnostic. APIs which can be speech or braille specific, or
> useful for both of these technologies. AT-SPI needs fixing in some places, and
> maybe it is not a whole lot of work, I don't know. Maybe Samuel (or somebody
> else, who knows about AT-SPI) could elaborate on whether AT-SPI is worth
> expanding, or do you think it should be replaced by something else?

I believe AT-SPI as it is is roughly the correct abstraction: giving
information on the application, without caring how it will be used.
There are issues with it (common bus rather than p2p connections), and
things can be done differently (pull-based vs push-based), but I don't
think the basic idea needs to be changed.

Samuel


More information about the BRLTTY mailing list