Imagine if every Linux developer just said, "I'm never going to put out something that isn't accessible again." https://tweesecake.social/@pixelate/117185934166581275
I'm not a developer, but even I can safely guess that it is easier to put accessibility in as you do every step of the process, rather than trying to shoehorn it in after the whole (inaccessible) app is finished. The impression I get is that 98% of Linux developers, when they think about accessibility at all, just think of it as something they might some day get around to doing.
Do better, please.
@RachelThornSub the crucial issue here is that most FOSS development is paid by and aimed at corporations. As such developers will rarely devote time to accessibility unless there's a specific product demand for that (which is almost never the case). So you can find a well-funded project and yet the accessibility work will be largely done by a lone volunteer.
@gabrielesvelto @RachelThornSub Thing is, very few developers seem to understand that accessibility is a part of the spec even when they understand that a GUI is better than the command line for the majority of users.
Kinda like the difference between spaghetti code and actually structuring it so the next dev (or yourself six months on) can understand what you did -- it's not a bonus thing, it's basic coding hygiene :)