Of course it's a good thing to be mindful of from a humanist perspective, but if fear of lawsuit is driving the change, it's not a very "love thy neighbour" kind of thing, but more of a fascist dictation, no? Especially if you are not in the US.
I'll be doubling down on my efforts to ensure better compliance nevertheless.
I presume the web standards you mention are part of some US legislation, yes? :S The web is becoming a crazy place, it seems that every country is writing laws that affects the whole web... and we as developers are assumed to know them all, from UI requirements (US) to security implications (Australia), to privacy concerns (GRPR)...
> The WCAG 1.0 was published and became a W3C recommendation on 5 May 1999. They have since been superseded by WCAG 2.0.
That said, the current is 2.1:
> WCAG 2.1 became a W3C Recommendation on 5 June 2018
[0] https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guid...
3 November 2008, though it had been available long before in as draft going back to 25 January 2001.
Lots of European companies have similar requirements if they want to sell to the public sector (which is probably even bigger as a market over here, I would expect).
Imagine using this for a new B2B app and then losing sales because prospective customers have ADA requirements or blind employees who use other web apps just fine. It’s extra engineering work sure, but it’s hardly a crazy ask, and it’s the right thing to do for large to medium size companies who can afford it IMO.
Implementing good a11y apis allows the variety of vendors to make assistive technology that can navigate your page for all sorts of user categories.
So the real question is always whether the technology to make something accessible exists and whether it can be deployed reasonably in the particular instance involved.
But if you do want to press on with sprinting events, note that they have been using start signals with both an audible and a visible component for a while, to accommodate people who may not be able to perceive one or the other. Back until we had electronically-triggered lights, you "couldn't" have a deaf competitor compete, modulo smoke from the starting gun. Now you can.
Plus years of stupendously painful physical therapy and Herculean will.
BS, we can and already have. here's a paraplegic person dropping in on one of the steepest in-bounds runs in the US.
quit being so dismissive.
I was not implying people with disabilities should stop doing things, rather, that it shouldn't stop a non-disabled person to do a thing just because a disabled person can't do the same thing.
There are actually accomplished quadriplegic pool players. They use a bridge and learn a grip that works. Disabled people are extremely adaptable out of necessity.
This is not correct and may result in very costly class action lawsuits.
There is a public domain within which most disabilities should be catered for but you can't expect that every non-private thing is made public so it's usable by all.
Just because something is 'in the web' doesn't mean it's a public service, access to which is a basic right.
It's good to be reminded to take into account disabilities, of course, since those are not obvious to people who do not have disabled people nearby.