Whenever a major accessibility case makes headlines, the reactions are predictable. Business cries foul and keyboard warriors spout silly fallacies. The recent Dominos case in America is no different - it feels like we haven't really progressed since the Target case in 2006.

But in the middle of the disingenuous outrage, there will also be some people who are genuinely jolted into action. Just as there were people who got a rude shock the first time they measured their website's loading time.

Taking things at face value, it's worth providing a few answers.

If you find anyone trying to "understand who the Dominos case applies to" it's pretty simple:

If you use a website to take money from people, you should make that site accessible.

There are various legal nuances; and of course it's the right thing to do; but ultimately it's just good business. In the US alone, people with disabilities spend more than $200 billion per year.

For those who think the law is new, it's not. It's been the law in many places for many years - including the US. Lawsuits are not new either, there have been hundreds in the US alone.

For those who think a11y is obscure or hard to build, it's not. There's plenty of documentation and tooling out there; and particularly compared with modern JavaScript it's incredibly stable and easy to learn.

The web industry has embraced frameworks, transpiled languages, dependencies, testing, performance and security (just to name a few). Each of them a massive topic, many of them changing on a cycle measured in months. Yet each of them attracts thousands of blog posts, conference talks and training courses. People have invested the time to master them.

Accessibility and HTML fundamentals have been stable for 20 years, yet people still can't make an accessible form?

People aren't making mistakes on obscure accessibility edge cases, they're failing to meet the basics: using colours with enough contrast, adding usable ALT text, making your content readable with assistive technology, making forms work with a keyboard. Some things are legitimately difficult to make in an accessible way, but a web form simply isn't one of them.

The industry certainly can't hope this will be fixed by someone else. I have hired enough university and coding bootcamp graduates to confidently say most still do not adequately teach HTML, CSS and Accessibility. You need to train your junior staff on this yourself.

For the older heads if you still aren't confident enough on accessibility to train juniors, add it to your learning plan like you would for any new technique. Spend the hours like you would for any other part of the technology puzzle.

This is our job.

Let's get on with it.