Well, honestly a lot of FOSS software has been lacking in usability in general, not even accessibility. It’s to be expected, as lots of software has basically been born from hobby projects and there is no unifying entity creating everything or defining human interface guidelines, besides perhaps GNOME and KDE.
The thing is that there is a big emphasis in FOSS software to “implement yourself” the features needed because most work is volunteer driven. So unless someone or some organization were to fund a developer or two to implement accessibility features, they don’t magically come into being.
Yeah, I think, it’s also underestimated how difficult accessibility is, because e.g. as a seeing programmer you’re pretty much blind to the way a blind person perceives the world.
I try to make my software accessible, but beyond basic keyboard accessibility and fixing the warnings that for example Firefox tells me, it becomes really hard to know what I’m doing. I have no idea what a good UI in a screen reader feels like.
I presume, companies can bring in outside experts or send their developers on trainings. I have none of that and get 0 feedback on how good it is what I tried to do.
Human Interface Guidelines should solve that. GNOME has their own ones, for example.
Edited: In GNOME, accesibility guidelines seems to be separated in https://developer.gnome.org/accessibility-devel-guide/stable/
Right, yeah, if you’re working with a mature UI framework, a lot of things may already have a solution.
Unfortunately, that very quickly becomes a luxury when you want to work with new, interesting technologies, as tends to happen when it’s your hobby.
I was also specifically thinking of:
- a webpage that I’m maintaining. I use semantic, simple HTML and try to fix all the accessibility warnings, but for all I know, it could be completely unusable for blind people.
- a game that I’m dabbling with. This one is really hard. It feels like I’d have to build a different game to make it playable with a screen reader or with e.g. just a pointing device.
I am studying WebDev right now.
Next year I have a subject for design guidelines and accesibility is a topic.
Don’t all GTK interfaces get screen-reader compatibility automatically from the built-in features of GTK? At least I thought they did based on what I read while I was working with it.
I heard this “implement yourself” argument way too often. I really can’t understand such a thinking. It’s like selling a car and say, that everyone could change tires, including the mounting on new rims. 🤦 As if everybody is a software developer.
But here the car is free…
Doesn’t matter it’s still a product at the end of the day. Just because it doesn’t costs anything doesn’t means you shouldn’t get much/anything in return beyond the software.
Additionally think of it as a developer, don’t you want to keep the lights on? Food on the table and etc? Well how you gonna dope the donations? By becoming committed to your “consumers” and having them return the favors.
You know what they says, what goes around comes back around. :)
product
“something (such as a service) that is marketed or sold as a commodity” (Merriam Webster)
“object or system made available for consumer use; it is anything that can be offered to a market to satisfy the desire or need of a customer” (Wikipedia)
In short: paid software is a product. A volunteering effort is not a product, it’s a gift.
Complaining about a gift not being good enough is quite entitled.
The vast majority of open-source devs don’t get donations or paid for it. We keep the lights on by having a day job, with the open-source work being only a hobby…
deleted by creator
probably not, imagine how it feels to just hear the output of “ls”. where every special character like underscores and such are spelled out. it probably works, but: a) i think its harder to grasp the bigger picture b) it is harder to for instance “jump” around. imagine visually jumping to the first directory that starts with “h” and then jumping to the word “heart” or something.
when you can see with your eyes you can see both in a precise and not-so-precise mode basically. The not so precise reading is for instance looking for specific patterns or something. but listening to some output is always precise. it is harder to ignore stuff which you don’t need
deleted by creator
There are many kinds of blind. You could have 95% reduced eyesight and make out windows and maybe blobs of colour but not be able to read anything. If you’re 100% blind, you can still rely on mouse movements instead of doing everything with a keyboard.
deleted by creator
But I obviously don’t know :)
Here’s a small report by a blind person using a MBP: How A Blind Person Uses A Computer – The Tommy Edison Experience
Tommy Edison, who has been blind since birth, shows how he uses the computer to send an email. The MacBookPro has an Accessibility preference called Voice Over which reads the screen to him.
Just mentioning for FYI reasons, for installation there is : https://wiki.parabola.nu/Installation_Guide#Blind_and_visually_impaired_users
I think the problem is somewhat comparable with what one can see with LineageOS. If you have or buy a phone which is not so popular and there is only one developer of LOS for your device it can happen that one day the developer will buy a new phone or start a different life and drops development. With Linux and related software project it is still pretty often hobby or community projects (See the development of Thunderbird going from Mozilla umbrella to community, and Ubuntu Touch being dropped by Canonical but picked up by ubports community). For example, if you are an open source developer and you live with housemates who are into Matrix and Signal for communication, it would be no surprise that you would want to work on that as well. Of course there are bigger projects like KDE (Gnome looks big but seems to suffer lately with a few projects, e.g. Evolution and Geary seem currently basically one person driven projects) which are not so much “hobby projects” anymore and could focus on this.
A possibly solution ? Reach out to blind people and work with them. For example : Start a new house community project with a few KDE projects living with a few blind people and a few motivated open source contributors for say one year. I am sure that things can be accomplished.
