Why accessibility is not an add-on
Some website quotes list accessibility as its own line, something you can take or leave. We don't sell it that way. Accessibility is part of the test gate every site passes before it goes live, next to speed on a phone and forms proven end to end. If a page fails, the launch waits until it passes.
The reasoning is plain. A site that a customer cannot get through with a keyboard, or cannot read, is a broken site for that customer. You would not pay extra for a front door that opens.
This post covers only the accessibility part of the gate. It says what gets checked, the public standard behind the checks, and why a small business in California should care.
The standard the checks follow
The checks follow the Web Content Accessibility Guidelines, WCAG for short, the W3C's shared public standard for web accessibility. The current version, WCAG 2.2, was published on October 5, 2023, and updated on December 12, 2024.
The Justice Department's web guidance says Title III of the ADA covers businesses open to the public. The same page names WCAG as one of the existing standards that give helpful guidance. That is guidance, not a rule written line by line for your shop, and this post is not legal advice. Still, it is the public standard the Justice Department points to, so it is the one we hold every page to.
What gets checked before launch
A person checks each of these on the real pages of every site, before launch.
Keyboard
Everything on the page has to work from a keyboard alone. People who cannot use a mouse or trackpad are shut out of any site they cannot move through with keys. So we put the mouse away and go through each page with Tab and Enter: the menu, the booking button, the contact form, the send button. If the highlight gets stuck or vanishes, that gets fixed before anything else.
Contrast
At WCAG level AA, normal text needs a contrast ratio of at least 4.5 to 1 against its background. People with limited vision or color blindness cannot read text that does not stand out enough from what sits behind it. We check body text, button text and link text against their backgrounds, and if a brand color fails, we find a shade of it that passes.
Form labels and errors
Every form field needs a label or an instruction that tells the visitor what to enter. We don't count a gray hint inside the box as a label. Then we send each form with mistakes in it on purpose, a blank phone field or an email with no @ sign, and check that the error says in words what went wrong and that a screen reader reads it out.
Headings
Headings have to describe what each section is about. For someone moving through a page with a screen reader, the headings work like a table of contents. A heading that only says Welcome tells that person nothing, so headings get rewritten until they say what is underneath them.
Why a person checks, not only a scanner
Automated checkers are useful, and they are not the whole of a check. The Justice Department says pairing a manual check with automated checkers can give a better sense of how accessible a site is. The W3C warns that a page can seem to pass quick checks and still have serious barriers. A scanner can't tell you whether booking a haircut makes sense with only a keyboard. A person going through it can.
Why a small shop gets the letter
It is easy to assume these lawsuits go after big national brands. UsableNet, an accessibility vendor, reviewed 2025 filings in a post dated January 8, 2026, and counted more than 5,000 digital accessibility lawsuits that year. By UsableNet's count, 64% of the companies sued had less than $25 million in annual revenue. Most of the businesses on the receiving end were not big brands.
California adds its own weight. The California Civil Rights Department says the Unruh Civil Rights Act requires businesses to comply with the ADA. The same page lists no less than $4,000 in statutory damages. California courts have applied the Unruh Act's access rules to the websites of businesses with a physical location, such as a shop, a restaurant or a barber shop. If you have a storefront in California and a website to go with it, that description fits you.
If a demand letter arrives, don't ignore it, and don't answer it on your own. Call a lawyer.
What to do
- Put the mouse away and go through your home page and contact form with only Tab and Enter. Write down every spot where you get stuck or lose track of where you are.
- Check your body text and button text against their backgrounds. WCAG level AA asks for at least 4.5 to 1 for normal text.
- Open your contact form and make sure every field has a label that says what to enter.
- Send the form with a mistake in it and read the error. If it does not say in words what went wrong, ask whoever built the site to fix it.
- Read your headings alone, top to bottom. If they don't tell a stranger what is on the page, rewrite them.
- If you use an automated checker, pair it with a manual check.
- If a demand letter comes, call a lawyer the same week.
Accessibility checks are part of the gate on every site we build, never a line on the quote, and you can see what a build includes on the websites page.