archinstall
archinstall copied to clipboard
archlinux
Add Orca screen-reader when installing desktop profiles with accessibility enabled.
I wanted to do this my self, but I'm not sure where the global configs are in the code. My idea was to add the Orca screen-reader to every desktop profile when installing with accessibility enabled, as well as adding the following to /etc/profile to make the screen-reader work properly: export ACCESSIBILITY_ENABLED=1 export GTK_MODULES=gail:atk-bridge export GNOME_ACCESSIBILITY=1 export QT_ACCESSIBILITY=1 export QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
I can do these things my self after installing Arch, but it'd be nice just to have it done for me automatically like Debian / Ubuntu does it.
We can look in to it, but I have a few questions:
- Would Orca screen-reader interfere with any other accessibility functions?
- Why isn't Orca used in the ISO?
Espeakup might interfere with Orca, but I'm not sure if that's been fixed. There was an issue I've encountered a while back where if I had Espeakup running and then ran 'startx' to start my desktop Orca wouldn't speak, and I had to disable the Espeakup service for it to work again. Orca isn't used in the ISO because it's a screen-reader specifically made for desktops, not CLI, so it wouldn't work in the image.
Orca isn't used in the ISO because it's a screen-reader specifically made for desktops
Ah, I thought that might be it. But the few minutes I spent looking I couldn't find information about being desktop specific. Since we use Espeakup we have to be careful here then.
Other than that, I see no issues integrating this.
Related comment: https://github.com/archlinux/archinstall/issues/774#issuecomment-1031746863
I've installed Arch Linux on my laptop, and turns out that Gnome ships Orca by default. The only thing I had to do after installation is enable the speech-dispatcherd service, so I'd simply add that to the Gnome profiles when installing with accessibility as well as making sure the lines I mentioned in my first comment are exported. I used Pipewire and it seems as though Espeakup isn't talking with that configuration. Someone would have to try with Pulseaudio though.