u/obaida2026
hp
" May the sales of HP burn just like they burned our nerves, and may every customer who buys their laptop wake up to find the BIOS dead and the accessibility screaming! Oh Allah, open a door of losses for the blue-badged HP that no tech update can fix, and leave their engineers staring at the wall until they go completely bankrupt!"
hp
" The HP team decided to achieve a historic feat... They bought a laptop for thousands of shekels, thinking they were geniuses when they programmed something for accessibility, and it ended up looking like it was designed for people from another planet! Imagine paying money and getting nothing because the screen reader in the BIOS doesn**'t work! They'**re masters of deception, and honestly, they deserve an award for being the most philosophizing for nothing! 🤣🤣 "
hp
HP doesn**'**t respect blind and visually impaired people; if you told a dog to program a screen reader in the BIOS, it would do it.
hp
HP doesn**'**t respect blind and visually impaired people; if you told a dog to program a screen reader in the BIOS, it would do it.
An Open Letter to AMI Firmware Engineers: It’s Time to Bring Screen Reader Accessibility to Aptio UEFI BIOS
To the firmware engineering teams at American Megatrends (AMI) and other major UEFI developers:Millions of computers worldwide rely on AMI**'s Aptio firmware to boot and manage hardware. Yet, entering the pre-OS environment remains a complete blackout for blind and visually impaired users who rely on screen readers like NVDA.We are fully capable of managing our devices, configuring systems, and performing maintenance. What we lack is not technical skill, but basic accessibility engineering in the BIOS. Relying exclusively on graphical, visual-only interfaces creates an unnecessary barrier and locks blind users out of fundamental hardware controlWith modern UEFI frameworks, it is entirely feasible to integrate lightweight text-to-speech or basic audio/screen-reader hooks into the pre-boot environment. We urge AMI engineers and firmware developers to prioritize accessibility in future Aptio releases. Technology should empower everyone equally, starting from the moment the power button is pressed."**
Why are blind people denied independence?
With the rapid pace of technological development worldwide, the evolution of BIOS interfaces to UEFI systems, and their subsequent development, blind individuals are being deprived of full control over their devices. I urge companies to take action and develop a BIOS that meets the needs of the blind. The deliberate neglect by these companies has reached a point where it is unjust for blind people to remain trapped in a prison of independence.
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 hardwareFrom 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?