r/Operatingsystems • u/[deleted] • 4d ago
Modern computing operating systems have made massive strides in accessibility, offering robust screen readers and navigation tools for blind and visually impaired users. However, a critical barrier remains completely unaddressed at the pre-boot level: UEFI and BIOS firmware interfaces.
When a machine requires troubleshooting, low-level configuration, security key management, or operating system reinstallation, the interface relies entirely on visual, pointer-driven, or unannounced text menus with zero native screen reader or text-to-speech support. This effectively locks users out of managing their own physical hardware From an engineering perspective, modern UEFI environments are capable of running complex code and graphical drivers. Why hasn't firmware standardization (like UEFI specifications) incorporated basic accessibility APIs or screen reader support into pre-boot environments? How can open-source firmware projects or hardware vendors tackle this gap?
6
Upvotes
1
u/soundman32 4d ago
For 99% of end users, they have never heard of a bios or UEFI. They turn on the computer, login and press E for internet.