Can the openSUSE installer expose screen-reader support before the graphical YaST frontend loads?
0 reputation · 06 Aug 2025, 23:42 UTC
0 reputation · 06 Aug 2025, 23:42 UTC
openSUSE's YaST installer can run in a text-mode (ncurses) interface, which works better with assistive tooling than the Qt frontend, and the installed GNOME desktop ships Orca with toggles in Settings > Accessibility. What seems missing is a documented, discoverable way to get screen-reader support during installation itself, before any desktop exists.
Assume a current Leap or Tumbleweed installation ISO booted in a VM. The practical constraint is that a blind user should be able to reach an accessible installation path without sighted help or prior knowledge of the textmode boot parameter. Orca and AT-SPI2 versions differ between Leap and Tumbleweed snapshots, so any answer should note which stack it applies to and be verified against the current media.
Is there a boot-menu or kernel command-line option on current openSUSE media that starts a screen reader or forces an accessible installer path early in boot? If not, does the ncurses YaST interface work reliably with a console screen reader such as those available in the initrd environment, and is that combination documented anywhere? Finally, would an early accessibility toggle in the boot menu be feasible given how YaST starts, or does the installer architecture rule that out?
31775 reputation · 07 Aug 2025, 05:55 UTC
Yes – current openSUSE Leap and Tumbleweed installation media can provide audible output before the graphical YaST frontend starts. The feature is enabled by adding kernel parameters at boot; there is no dedicated boot‑menu toggle that turns it on automatically.
textmode forces the ncurses YaST installer, which runs in the console before any graphical environment is loaded.speakup kernel module and the espeakup user‑space daemon. When the module is loaded and the daemon started, it can speak any text that appears on the kernel console.textmode speakup.synth=soft
textmode forces the ncurses YaST UI. speakup.synth=soft loads the software synthesizer (espeak) via the speakup module. In practice this combination produces audible prompts from the installer’s screens.
textmode speakup.synth=soft to the existing line and press Enter to boot.speakup.synth=soft; no speech should occur.lsinitrd | grep espeakup to verify that the daemon is present.espeakup from the initrd, leaving the module loaded but no speech output.The installer architecture does not preclude an early accessibility toggle. Adding a menu entry that injects textmode speakup.synth=soft would be a straightforward packaging change. The speakup module loads early in the kernel, and espeakup starts from the initrd’s systemd units, so speech is available by the time YaST’s ncurses frontend initializes.
Which specific ISO image (Leap version, Tumbleweed snapshot date, full DVD vs. net‑install) are you testing? The presence of espeakup in the initrd varies by image type and age, and that single fact changes whether the parameter combination will work out of the box.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.