Things that are not the problem:
"Inflation"
Unions
Minimum wage
Immigrants
Public spending
Social Services
Welfare
Homeless people
Gay people
Carbon Tax
Bike lanes
Mass transit
Trans healthcare
Women's healthcare
Genderqueer people
Indigenous land rights
Urban greenscaping
Public education
Public healthcare
Public libraries
Vaccines

Devin Prater :blind:
in reply to Devin Prater :blind: • • •Sensitive content
And I'm one of the maybe 5 blind people, on Mastodon even, who use Linux at least once a week. And I use an old fork of Gnome 2 called Mate, as my desktop. Why? Because it's well, as accessible as Gnome 2 was in the day, pretty much. Even other techie blind people would rather not deal with it and stick to Windows where they can get things done. And Orca *is* more reliable these days. Imagine a year ago, your screen just suddenly goes dark for no reason and you have to restart it to see your computer again. Every 30 minutes or so. Even better! You like games? Got a Steamdeck? Imagine you buy it, and it turns on, but your screen is blank. Nothing there, and you can't figure out how to turn the screen on. Well I mean you could install Windows on it, but that's just, so much extra work! That's ableism. That's discrimination. But oh no instead of helping us, instead of fucking using that talent for programming and shit for good, people would rather just go "meh it works for me stupid blink blink" instead.
blind folks, we sure as shit ain't the worst population there is. Believe me. You, reading this, think you're bad? You, general blind population, think the audiogames forum is bad? Nah. There's definitely worse out there. And there just comes a time where we have to just speak our feelings, speak what's true for *us*, about tech, about life, about having a sensory disability, that other communities will *never* face. Honestly, I doubt me ranting about this will do any good in the wider community, but more validation for other blind people will never hurt anything. Just because some smart people on Mastodon makes you feel like hey maybe I'm just too disabled, or too stupid to work Linux, remember, you're not. Linux is just *that* freaking hard.
reshared this
modulux reshared this.
The Cube
in reply to Devin Prater :blind: • • •Sensitive content
Devin Prater :blind:
in reply to The Cube • • •Sensitive content
Jookia
in reply to Devin Prater :blind: • • •Sensitive content
the esoteric programmer
in reply to Jookia • • •About the bios, that's infinitely more complicated. For now, the biggest problem is that there's no standard for a soundcard, no single API all of them would use, like you can now drive absolutely any graphics card using a very rudimentary API, called VGA I believe, yes, even nvidia. And no, the pc speaker isn't a good enough substitute, because who knows if it's universal, I know of at least two computers who don't have it at all, and also you can't really transmit lots of things through it, much less intelligible speech, though as with anything, I'd be glad to be proven wrong. But anyway, basically, firmware has to be small, right? Well, forget small, start thinking how would it fit the current chips flash memory size, because basically you'd have to put in there drivers for all the soundcards linux has access to at least, and even excluding external sound cards, that's a lot. So, to actually answer your question, I dk if it's possible at all to do this, bake something like that into the firmware. You may then be asking, how does apple do it then? Well, first off, you may be familiar with the amount of restrictions mac OS has, if you tryed making a vm or hackintosh before. Well, that's part of the reason, they integrate everything in there. But also, the most important, I'm not aware of a single instance where you actually interact with the UEFI menu of apple hardware and it actually speaks. Instead, you either interact with the bootloader, which could probably be larger on linux as well, to contain all those drivers, but apple has only one hw combination so it's easy for them, or essentially half of mac OS, with voiceover included, just that the graphical part is a fullscreen application, accessible and readable with voiceover. There you go, that's how apple does it. So, in order for an accessible bios to be doable, we have to first solve the sound card problem, because afterwards, things are relatively simple, integrate flite or something similarly lightweight, then wire it up to speak when selection changes, in the same parts where the selection is redrawn. That's all there is to this problem, and it seemns easy kinda, except for the soundcard issue, which would basically need the whole w3c and a lot of soundcard companies to make a standard followed by at least all of the new cards past that point. I know a person who tryed to make a proof of concept audio stack for uefi, as preparation for screenreaders on actual firmware, but not only there's no onboard audio support in the uefi specification, but there's no usb audio either, so that would have to be solved, because it ties in with and is exactly the first problem.
modulux
in reply to the esoteric programmer • • •the esoteric programmer
in reply to modulux • • •modulux
in reply to the esoteric programmer • • •Drew Mochak
in reply to the esoteric programmer • • •There is a similar discussion for recovery managers in Android with a similarly unproductive result. The closest anyone got is TeamWin which lets you use script commands like "install" "format" etc on the commandline from a connected (USB) terminal. I've also seen a few environments that will look for a file to execute a list of instructions from when it launches.
I wonder if either approach would work here: an interface that will except instructions from a properly-credentialed device (SSH, say), or a utility/scripting language that will allow you to change BIOS settings from another OS that the BIOS will load upon boot.
@jookia @pixelate @seedy
Matt Campbell
in reply to Drew Mochak • • •Sensitive content
Jookia
in reply to Matt Campbell • • •Sensitive content
Bren
in reply to Devin Prater :blind: • • •Sensitive content
Partially sighted person here, can definitely confirm. Reinstalled Debian 2 weekends ago and identified at least 15 bugs* during the audio install process, some of which seem completely show-stopping for someone blind. This is on top of the BIOS issues and before first boot.
*Yes, I hope and plan to report the bugs, but Debian's bug search and reporting system has a learning curve and I haven't submitted any yet.
WestphalDenn
in reply to Bren • • •Sensitive content
Devin Prater :blind:
in reply to WestphalDenn • • •Sensitive content
WestphalDenn
in reply to Devin Prater :blind: • • •Sensitive content