In the Web context, accessible websites also work better for search indexing, and for semantic processing, and for manipulating with Javascript (ie: addons). Text annotations for images are a huge help to all sorts of people and software, not just folks who can't see the image.
The main reason to support accessibility work is that it is the right thing to do for disabled people. But if that doesn't motivate you, there are selfish reasons for people without disabilities too.
In general not enough attention is paid to just flat out whether an entire business process is accessible. Or perhaps more - how you can adjust your business, your offering, or your process in order to make it possible for more people to access it, or to be employed by you in delivering it.
If you treat accessibility as a box checking exercise done by web and app devs you can end up worrying about making the driver portal of your ride sharing app work for a blind user, rather than thinking about what features are needed to make it possible for a person in a wheelchair to hire a rideshare that can accommodate them.
Accessibility doesn’t begin and end at screenreader support and text contrast levels. But if you leave it up to developers to do then that may be all you’re going to be able to get.
> We are well-paid professionals being asked to make our tools usable by the entire public
“Asked” is wrong here. I can “ask” someone to do something. The government can “force” someone to do something, ultimately at gunpoint. That’s what I don’t like about this.
I don't think somebody should honestly call themselves an "engineer" if they can't be bothered to make their systems usable by the masses. It is an utter lack of professionalism.
I think the rhetorical difference between "ask" and "force" is ripe for abuse in discussions regarding contentious government roles.
[0] If this seems implausible, consider this thought experiment (U.S.-based). A police officer gives you a ticket jaywalking. If you don't pay it, you're at risk of being the target of an arrest warrant. If the police find you, they will attempt to put you in cuffs. It goes downhill from there. For jaywalking.
I'm not arguing for or against things working this way, but I do think it's reality.
I agree. But you are being arrested for the consequences of fully refusing to accept the jaywalking rule.
I'm looking for the day when someone has a gun held to their head for not making their website accessible. More likely, you'll just be fired for not doing your job.
What am I missing? What’s the magic way to avoid complying with this new government edict without escalating to violence?
Move to the mountains and farm turnips.
If you mean "how do I avoid complying with laws while still participating in polite society," you're right, that one you can't do.
If someone “asks” me to do something, they usually don’t mean “otherwise I will take your money and/or jail you”. But all laws have that threat, otherwise they wouldn’t mean anything. Hence why I take issue with saying the govt is “asking” us to do something - even though that thing is good and honorable, it’s still not an “ask”.
*well, I mean, there’s probably mountain turnip preservation zones or something, where it would prohibit me from farming mountain turnips.
Using the force of government is, or should be, a serious affair, and I think we water it down by using language like “they’re just asking”, etc. The force of government never “just asks” - when Trump was deporting people, no one (reputable) said they were “asked to leave”.
That sense of seriousness about government force would help us see clearly what is, and is not, worth bringing government into.
Note: I have around 160k images on the net, all marked as CC-BY. Thought I was doing something good by sharing but now I'm told if I don't make them all blind accessible then I'm a criminal.
I also have ~200 open source projects, 10 or so are fairly popular. Volunteered lots of time to make them, don't believe I should be forced under threat of fines and jail to have to put more time into them.
Find that hard to believe purely on common experience + if not, likely not "disabled" in the sense of being affected to a degree of not being able to use a standard website. in the same vein, counterargument here is a lot of disabled people _can_ indeed use a standard website.
Irregardless of what kind of of business I'm running, I'm targeting only tiny sliver of population. I'm easily ignoring 90%, sometimes 99.9% of population, as long as it allows me to make a better product for the remaining few.
1. Disability is a spectrum, not a condition, and a temporal, not a terminal state. Ever get your eyes dilated? Ever break your foot? Ever try using most common devices with a baby in your hands? Ever needed to watch a video in a loud room, or a place in which you cannot use headphones? Ever try using a laptop outside on a sunny day? Ever try getting old?
2. 26% of all adults in the US have some form of disability. 10% of these are sensory (hearing/sight). Are you really telling me you're just ignoring 26% of the population?
3. We are well-paid professionals being asked to make our tools usable by the entire public, not just a subset of it - we're making an average of 2-5x the median income, presumably based on our professionalism, knowledge of our craft, and ability to do hard things.
4. It's the right thing to do, both morally and practically. It allows every person to participate in society, allows us to leverage the full skills and abilities of every available human, and doesn't give us an "out" to start excluding people because we're too lazy to consider their needs.
5. If none of that sways you: some day you too will need this, if for no other reason than you've gotten old. It'll be nice to live in a world in which the people we are today are willing to take care of the people we'll be some day.