Good news: We have started working on accessibility of Anaconda! For start, the braille terminals now somewhat work in text mode.
On the Workstation images, accessibility already was at the same level as a finished system would offer. Workstation media run a full Gnome session, with Orca available. The installer does not have to do anything. However, for the Server images the situation is different. The environment is heavily reduced: no sound, no Gnome, no Orca. That also means, no accessibility. Let’s change that!
The latest Fedora 35 beta nightly builds now have the brltty screen reader on Server images. Thus far, brltty is enabled only for the console, which requires Anaconda to be started in text mode. There is also no means to configure the brltty session, so autodetection must work for your braille terminal device.
If you have a braille terminal, you can already try this out!
- Grab an “Everything boot” or “Server boot” image from the Fedora nightly compose finder page.
- Prepare a flash drive or DVD to boot from. Start the computer with the flash drive inserted.
- In the machine’s settings, choose to boot this time from the flash drive.
- Press e to edit the boot options. Unfortunately the boot menu itself is not read by brltty, so you will have to guess the timing.
- Type space and then inst.text to start Anaconda in text mode
- Confirm with Enter or Ctrl+X (the former for BIOS, latter for UEFI) and wait for Anaconda to start.
Once Anaconda starts, you should be able to read the screen using your device… or not. Tell us!
Admittedly, entering the text mode is near impossible for a sighted person, but treat this as only the first step.
In the future, hopefully the Xorg driver for brltty could be added, so that GUI becomes somewhat accessible this way, too. That is definitely the preferred option: The text mode is heavily simplified in some areas, and getting there through the “silent” boot menu is not easy.
It is not clear yet if there needs to be some way to configure brltty. The method of doing so would involve boot options: Either directly by adding a new option – perhaps inst.brltty – or indirectly by adding a kickstart command which would require using the inst.ks boot option. However, given the inaccessibility of the boot menu, it is doubtful if this would help anything. Statistics on how many daily used braille terminals need special brltty configuration would be useful.
In the long run, it would be probably best if sound and Orca could be present on the Server images, too. That comes with its own set of problems, though. Right now the combined size of all the missing parts is a very tough proposition. The server images have been traditionally small, lean and trimmed down to fit a CD. While that is no longer strictly true, keeping the images small is still a goal.
Ultimately, neither the Anaconda developers nor Fedora maintainers and relengs are the target audience for this. If you have a stake in this matter, we would love to hear from you! You can find the Anaconda mailing list at firstname.lastname@example.org. Or just comment on this blog post.
Last but not least, let’s not forget Jaroslav Škarvada and Vojtěch Polášek who helped with this effort. Thank you!