Re: Update on the accessibility status for UEFI
It's nice someone is finally tackling this issue. Here are my thoughts in no particular order. Also keep in mind I'm not a developer, so I don't know how hard some of this would be, and I don't understand most of the jargon thrown around.
I assume this is only for new systems released in the future? Would existing manufacturers have to release updates if they used UEFI in their machines? I think all options should be spoken and the navigation to those items should always be possible using the keyboard. As far as speeech goes, I don't care what is used, because any speech in those screens would be better than nothing at all. Would eSpeak work?
Regarding audio, perhaps including the generic USB drivers would help? Even if sound couldn't beh eard from the built-in card, it should be possible to connect a USB headset or other audio device and get audio. Then again, wouldn't the manufacturer be required to properly support audio anyway? I always thought the firmware was specific to its machine, so this shouldn't be an issue unless there's something I'm missing.
That's about all I can say on the subject. Good luck. This has the potential to open more employment opportunities for blind IT professionals. Oh, please get Microsoft involved. If a company like Microsoft is mandating something like this, maybe people will take it seriously. I don't know who you would contact specifically, but maybe try @msftenable on Twitter.
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
