Casey Reeves: "Linux GUI So, this morning, a…" - LGBTQIA+ Tech Mastod...
source link: https://tech.lgbt/@xogium/110507457689374019
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Casey Reeves: "Linux GUI So, this morning, a…"
@devinprater @jookia @xogium Or the ones that would would all do so differently, requiring the users to learn every program as if it were an entirely different AT stack, like switching between JAWS and NVDA and VoiceOver and different browsers and... Perhaps the mainstream understandable Linux equivalent would be being required to know how to totally use both emacs and vim without any adaptation scripts to make one feel like the other.
@devinprater @jookia @xogium And to switch constantly between those each hour depending on what you need to do
@x0 @devinprater @jookia Yes, exactly. I went through this w/ chromevox for years. I am never doing that again. I didn't mind orca vs speakup. But learning a screen reader for each and every app? Nop, thanks.
@xogium @devinprater @jookia From my outside perspective, I think along with a fair few developers not caring, there are just too many choices. The reason marginally more Windows apps are accessible is because unless you use something like tkinter which just draws the entire UI, you're eventually using win32, and win32 talks to the accessibility APIs *by default*. Unsure what QT is doing but I know the so-called accessible UI it exposes to screen readers is unnecessarily verbose, all buttons say enter for instance, and edit fields and tables just don't behave like the corresponding native controls. But while AtSpy or whatever it's called exists, the fact of FOSS means that all these UI toolkits and window managers and everything else are so fragmented as to require the NVDA app module/JAWS script style workarounds for every framework just as well as every app's idiosyncratic use of said framework. Of course centralization into one dominent framework for everything is not the answer, as the odds are said thing would be inaccessible by default and be staffed with people who don't care. I personally just don't think it possible without some fundamental change, beyond devs caring about accessibility. Something about the entire ecosystem has to change or it will always be a hopeless tangle of barely working this and that.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK