A startup building a new email client shouldn't be required to implement accessibility, certainly not from the start. There are enough accessible solutions in that space, and while accessibility would be nice, it would make the barriers of entry much higher.
On the other hand, Facebook, a company famous for prosecuting app developers for (mis)using their API, should absolutely be required to do so. If all your friends are on Facebook, you're not even allowed to build a more accessible Facebook client.
I also believe that we should legalize 3rd party apps if the original app is inaccessible, regardless of the TOS or presence of DRM.
Companies with large market share should also be actively required to facilitate interoperability, e.g. with APIs available on FRAND terms.
Having previously worked and taking a great interest in the schematic web last decade, progressive enhancement, accessibility, page size, etc etc the modern web is disappointing when what should be a simple HTML website instead be a blank white screen while it downloads 2mb+ of assets then a SPA bootstrap to show something loading json blobs embedded in the page and leaking information with the insistence of doing everything client side.
I'm not fundamentally opposed to JavaScript frameworks, even when used to make SPAs. I think their downsides can be worth using them anyway and issues like accessibility can be overcome. They are a paradigm that are chosen too often without enough thought about the downsides and are a bad choice as default.
Doesn't the ADA already have some exemption for startup/small businesses where it doesn't apply if you have less than X employees?
For example, one of the links provided elsewhere is to an EEOC website. The EEOC is the Equal Employment Opportunity Commission, which only relates to employment, not to accommodating customers.
1: https://www.accessibility.com/blog/do-small-businesses-with-...
[1] https://en.wikipedia.org/wiki/Voluntary_Product_Accessibilit...
Good to know
There's a lot that automated checkers don't find. They can detect if an image lacks an alt attribute, they can't tell if an alt attribute's value is bad. Many are pretty good at at least flagging where there might be a color contrast problem for a human to double-check. They don't automatically find interactive components that aren't keyboard navigable or operable. They don't know when the DOM order of content doesn't make sense.
For me though, making sure keyboard navigation works properly early on speeds up the develop and test cycle. I also think that in many cases, perfect ends up the enemy of the good. It's a different conversation if a disabled person contacts someone about a site with a suggestion for improvement rather than it doesn't work at a all.
I somewhat question the need, as well—at some of the contrast levels we're talking about, if your vision is that bad, you should really consider enabling a magnifier, color filter, or even a screen reader.
What becomes really problematic, however, are PDFs, which are supposed to be a quick way to offer printed documents digitally, without too much extra work. Making those work with screen readers can take a long time, and there have been some cases where clients decided to just remove them from their websites. I'm not sure what to do about that, but I'm concerned we're creating barriers to sharing information, with anybody.
The contrast issues sometimes make design a bit harder, but it's totally worth it I believe.
EDIT: By analogy, it's very like software portability. If you make your software support Windows and MacOS and assorted Linux distros and the major BSDs and Haiku, you'll get more users. But if you only target Windows you'll get 80% of the market, and Windows+MacOS will get you 90%, and after that you really need to think about whether it's a good investment to target more platforms. By all means, be accessible because it's the right thing to do or legally required, but it's not obvious that it's a sound business move.
But I'd much rather work at a company that was 1% less profitable or live in a society that was 1% less wealthy and accommodated people with disabilities than one that left them in the gutter.
At least with webdev the problem is most people stumble into it and are not formally taught much about webdev specifically if at all. My undergrad never taught me a single thing about webdev practice. It’s not like, say, architecture, where you not complying with accessibility regulations will be taught formally, or later when you actually implement it some code compliance inspector is going to deny you a permit to build. It really is the wild west in webdev still.
In my view, it's about trying to provide more 'equal opportunity' in this world where it's financially feasible. This seems like a case where it is more often that not. Again, for medium+ businesses.
It's important to remember making websites more accessible often benefits everyone in some way. e.g. providing an alt text description for images on your website obviously benefits visually impaired users, but it also benefits people who can't afford high bandwidth or people who are moving through a remote area. In the Microsoft framework these three scenarios are called:
1) Permanent (Visually Impaired)
2) Temporary (Can't afford high bandwidth)
3) Situational (In a remote area)
There's good online resources for understanding these concepts [1,2,3].
Anyway, for companies as big as WinnDixie, with $10B in annual revenue, they should be designing their websites to be accessible by everyone. For small businesses it would be nice if website building providers like SquareSpace and Wix made this as easy as possible for their users.
[1] https://www.iweb.co.uk/2016/10/inclusive-design-why-our-webs...
[2] https://www.youtube.com/watch?v=TAzkrXTGEOM&t=55s
[3] https://www.w3.org/standards/webdesign/accessibility