Maintenance · 5 min read
Accessibility for small business websites: what the law expects
WCAG compliance isn't just a government-website concern. Here's what the law actually expects from a small business site, and what it costs to close the gaps.
Most small business owners think web accessibility is something only government agencies and big corporations have to worry about. That assumption is wrong, and it has gotten more expensive to hold onto. Web Content Accessibility Guidelines (WCAG) compliance isn't a nice-to-have. It's a legal exposure point, a usability problem, and in most cases, a straightforward fix that gets skipped because nobody explained what the law actually expects.
What the law actually says
In the US, Title III of the Americans with Disabilities Act (ADA) covers "places of public accommodation," and courts have increasingly ruled that a business website counts as one, even without a specific federal web accessibility statute spelling out the technical standard. The UK's Equality Act 2010 works the same way: a website that shuts out disabled users can be treated as unlawful discrimination. Neither law hands you a checklist. Courts, regulators, and plaintiffs' experts point to WCAG 2.1 or 2.2 at the AA level as the de facto benchmark, because that's what gets used to measure compliance in practice.
4,605+
ADA Title III federal lawsuits over website accessibility filed in a single year
Source: UsableNet 2023 Digital Accessibility Lawsuit Report
Most of those lawsuits don't target huge retailers. They target small and mid-sized businesses, because that's where the easy, obvious failures sit: missing alt text, no keyboard navigation, forms nobody can submit without a mouse.
WCAG in plain English
Forget memorising the full WCAG spec table. For a typical small business site, meeting AA level comes down to four things:
- Every image that carries meaning has real alt text, not a filename or "image1.jpg"
- Every interactive element (menus, buttons, forms) works with a keyboard alone, not just a mouse
- Text and background colours have enough contrast to read on a phone in direct sunlight
- Forms have visible labels, not just placeholder text that disappears the moment you click in
That's the 80% that catches most complaints. The remaining 20%, things like video captions, ARIA roles on custom widgets, and focus order on complex layouts, matters, but it's rarely what triggers a demand letter.
96%
of the web's top one million home pages have at least one detectable WCAG 2 failure
Source: WebAIM Million Report
What people assume versus what's true
| What people assume | What's actually true |
|---|---|
| "My site looks fine, so it must be accessible" | Visual polish and WCAG compliance are unrelated. A beautiful site with low-contrast text and no alt tags fails both. |
| "Accessibility is only a legal issue for government and healthcare sites" | Title III lawsuits target retail, restaurants, and local service businesses more than any other sector. |
| "We'll deal with it if someone complains" | Most claims arrive as a demand letter requesting damages and a consent decree, not a friendly warning first. |
| "Fixing this means rebuilding the site" | Most AA-level fixes are CSS, markup, and content changes. A full rebuild is rarely required. |
What it actually costs to fix
On a typical small business site, say 10 to 30 pages with a contact form and maybe a booking widget, closing the common AA gaps runs a few days of focused work: an automated scan to catch the obvious issues, a manual pass for the things scanners miss (keyboard traps, heading order, form labelling), and a round of fixes. That's a fraction of what a lawsuit, settlement, and the rebuild that usually follows one would cost. We fold an accessibility pass into every UI/UX project we run, because retrofitting it later always costs more than building it in the first time.
Where to start this week
- 1Run your homepage and two or three key pages through a free automated scanner like WAVE or axe to catch the obvious failures
- 2Fix every image missing alt text on the pages that actually drive traffic or conversions
- 3Unplug your mouse and tab through the site. If you can't reach the menu, the search box, or the submit button, neither can a keyboard-only or screen-reader user
- 4Check your form labels are real <label> elements, not just placeholder text
- 5Document what you fixed and when. If a complaint ever does land, a documented, ongoing effort is worth more than silence
None of this requires a redesign. It requires someone who knows what to look for actually looking.
Questions people also ask
Do small businesses legally have to meet WCAG standards?
There's no US federal law that names WCAG directly for private businesses, but courts treat WCAG 2.1 AA as the standard used to judge ADA Title III compliance. In the UK, the Equality Act 2010 works the same way. Treat WCAG AA as the practical requirement, not an optional bonus.
Is WCAG AA enough, or do I need AAA?
AA is the level referenced in almost every lawsuit, settlement, and regulation that touches private websites. AAA is a higher bar that even most government sites don't fully meet. Aim for AA first.
What happens if I just ignore this?
Nothing, until it doesn't. Most businesses find out they have a problem through a demand letter, not a warning. By then you're paying a lawyer and a developer at the same time, under a deadline you didn't set.
