I'm not disagreeing with you, BTW... just saying that for the decision to be good business sense you need to look at the full potential impact on the business.
It just kind of feels like a joke, when almost any webapp in existence is not compliant and there is no enforcement.
It also goes against the hacker ethos that we should be free to build and share without credentialing or licensing.
Imagine if you couldn't Show HN without thinking about accessibility and actually taking on serious legal risk.
No, because real people with problems (not lawsuit trolls) don't want your money, they want you to fix your product. Most will reach out before bringing a suit. If a suit is brought, they almost always settle if the company A) fixes the problem and commits to keeping the product accessible and B) pays the costs of the suit.
It's cheaper to fix the problems than to fight the suit, especially for a new business that doesn't have a lot of technical debt or a large corpus of inaccessible content.
> Imagine if you couldn't Show HN without thinking about accessibility and actually taking on serious legal risk.
U.S. accessibility requirements for private entities (vs. government ones) apply to "places of public accommodation." Lawsuit results have been mixed about whether an online operation, especially if it has no corresponding physical operation, count as a "place" (I think they do). Personal sites, projects will not require meeting accessibility requirements any more than your house will be legally required to have a ramp for wheelchair users.
If you're going to worry about legal risks for Show HN projects, worry more about creating privacy and security problems for users.
It seems like it would be a good way for a company to suppress competitors to a field, they could trigger these kinds of laws in up-and-coming companies.
And yes, you certainly could audit your competitors products and force them down this path. I'm not sure that is a winning move, though, as all you are doing is forcing them to build a stronger product.
But there are many physical products that can only be used by people without certain disabilities. For instance, cameras, mirrors, light bulbs and paintings require you to be sighted to get any utility from them. Headphones require you to be able to hear. Those might be extreme examples, but there are a huge number of things that you basically get zero utility out of if you don't have typical abilities in relevant areas. Should I not be allowed to sell a bicycle if I can't figure out a way to make it work for people who don't have 4 functioning limbs?
Most web sites can be made accessible simply by making them work normally and reasonably... it's generally the browser's job (and various other things like screenreaders) to make them accessible, assuming the web developer isn't doing something particularly weirdly. Isn't it?
It seems highly inefficient use of resources to have each site have to do a lot of work to support accessibility, especially if the sites are doing basic things like presenting documents. But if I make a web based paint program or charting app, what am I supposed to do for people who don't have sight? Does that even make sense?
> Most web sites can be made accessible simply by making them work normally and reasonably... it's generally the browser's job (and various other things like screenreaders) to make them accessible, assuming the web developer isn't doing something particularly weirdly. Isn't it?
It's not the browsers legal responsibility to do so, no. It's the responsibility of the business to do that.
It makes sense to address it universally, if possible, rather than case by case. Surely you agree that someone who simply puts a document on the web should not have to develop their own screen reader. Or should it just be businesses that are required to do so? That has obvious problems.
Also, when you have financial access issues, it implies that you have access issues for everything in life, including the basics like medical care.
The general point is that "I don't use a particular OS" is wildly different to "my body does not work that way".
Right after security.
After all, if you're in the business of shipping half-finished software and rushing from one feature to the next in a mountain of tech debt, how on earth are you going to find the time to think about accessibility?
Internet shaming aside, ignoring accessibility for a while seems like good business sense.