Speakup Text Mode or Orca Graphical Mode for Rocky Linux Installs on Uncertain Hardware

Rocky Linux offers two documented accessibility paths in its Anaconda installer, and a deployment plan for blind and low-vision users has to commit to one before the capabilities of every target machine are known. The goal is to standardize a single installation procedure that stays dependable across mixed hardware.

The text-mode console can be made accessible with the Speakup screen reader, but Speakup is not active by default; it must be requested through a kernel parameter such as speakup.synth=soft at the boot menu, or built into a custom kickstart file. The graphical GTK installer exposes Orca and high-contrast themes, yet Orca only becomes available once the graphical session starts, so the path depends on working video drivers and more memory. Documentation also frames Speakup partly as a legacy option, and synthesizer detection can fail silently on some USB keyboards and virtualized consoles.

That leaves the choice unresolved when RAM, video support, and console type vary:

• Which installer mode is the safer default for screen-reader users when hardware capabilities are uncertain?
• Is there a supported way to make Speakup available during installation without editing boot entries on every run?
• At what practical minimum of memory and console support does the graphical Orca path stop being viable?