Website accessibility in 2026: the lawsuit risk most small businesses miss

Picture the email. It arrives on a Tuesday from a law firm you have never heard of, and it says your website has barriers that prevent people with disabilities from using it. It lists a few pages. It suggests a settlement figure. And your first thought is the same one almost every owner has: my web designer must have handled that.

Usually, they did not. Nobody was being careless. Accessibility simply isn't part of what most template-based sites, page builders and budget agencies deliver, and it rarely appears in a quote. That gap is now one of the most predictable risks on the small business web, and it is growing.

What the numbers say

Law firm Seyfarth Shaw, which tracks federal filings, counted 3,117 website accessibility lawsuits under Title III of the Americans with Disabilities Act in 2025. That is up 27% from 2,452 the year before, and it means roughly one in three Title III federal cases was about a website. Those are only the cases that reached federal court. Many more demand letters are settled quietly, so the true volume is higher.

There is no law that spells out a technical rulebook for private business websites. In practice, courts and plaintiffs' lawyers measure sites against the Web Content Accessibility Guidelines, usually WCAG 2.1 Level AA. If your site fails that benchmark, it is easy to document.

And most sites do fail. The 2026 WebAIM Million report, which scans the home pages of the top million websites, found detectable WCAG failures on 95.9% of them, averaging 56 errors per page. The most common problem, found on 83.9% of pages, is text that doesn't have enough contrast against its background.

If nearly every site fails, why would yours be the one that gets picked? Because the ones that get picked are the ones that are easy to prove.

Why most sites fail

The failures that show up in audits are rarely exotic. The same handful of problems account for almost everything:

• Low contrast. Light grey text on white looks elegant in a design file and is unreadable for people with low vision, or anyone outdoors on a phone.
• Missing alternative text. Images with no description are invisible to screen reader users. A photo-heavy site with no alt text is effectively blank to them.
• Unlabelled form fields. A contact form where the labels are placeholder text that vanishes as you type is a barrier for screen readers and for plenty of sighted users too.
• Keyboard traps. If you can't reach the menu, the booking widget or the checkout using only the Tab key, a whole group of users can't buy from you.
• Missing or invisible focus. When there is no visible outline showing where you are on the page, keyboard navigation turns into guesswork.
• Broken heading structure. Headings chosen for their size rather than their meaning make the page impossible to scan by ear.

Templates and page builders tend to produce all six. The theme was designed for how it looks in a demo, and each plugin you add brings its own markup, its own contrast choices and its own keyboard behaviour.

Why a widget won't save you

This is where many owners get sold the wrong fix. A one-line script, usually a small accessibility icon in the corner of the page, promises to make a site compliant automatically. It sounds ideal: no rebuild, a small monthly fee, and the problem goes away.

It doesn't work that way. A widget can adjust font size or contrast on request, but it can't repair a form with no labels, rebuild a menu that keyboards can't open, or write meaningful descriptions for your images. In January 2025, the US Federal Trade Commission ordered one of the best-known overlay vendors to pay $1 million over claims that its AI tool could make any website WCAG compliant. That order applies to one company's marketing, not to every product like it, but the lesson is clear: accessibility lives in the code, and a layer on top can't replace it.

It's also a growth story

Framing accessibility only as a legal threat misses the bigger point. According to the CDC, about one in four US adults lives with some kind of disability. That is a very large group of potential customers, and a site that can't be used by them is quietly turning business away, with no angry email to tell you it happened.

The overlap with everything else you want from a website is also considerable:

• Search visibility. Clear headings, descriptive alt text, labelled links and semantic markup are exactly what search engines and AI assistants use to understand a page.
• Conversions. Readable contrast, large tap targets and forms that are easy to complete help every visitor, including the person squinting at their phone on a train.
• Speed and stability. Accessible sites are usually cleaner and lighter, because they are built with simple, standard markup instead of layers of scripts.

In a market where almost every competitor's site fails the basics, one that works for everyone is a real advantage, and one most competitors can't easily copy.

A ten-minute self-check

You don't need to be technical to get a first read on your own site. Try these five checks:

1. Put your mouse away. Use only Tab, Shift+Tab, Enter and Space. Can you reach every link, open the menu and submit your contact form? Can you always see where you are?
2. Zoom to 200%. Press Ctrl and + (or Cmd and +) until the page is twice the size. Does the text stay readable, or does content overlap and disappear?
3. Check your contrast. Paste your main text and background colours into a free contrast checker. Normal text needs a ratio of at least 4.5:1.
4. Read your forms. Does every field have a visible label that stays on screen while you type? Do error messages say what went wrong and how to fix it?
5. Run a free scanner. Tools such as Lighthouse (built into Chrome) or axe will flag common failures. Treat them as a starting point: automated tools only catch part of the problems, so a clean score doesn't mean a compliant site.

If you find yourself stuck on the first check, you have found the kind of barrier a real customer would hit.

Accessible by construction

Retrofitting accessibility onto a finished site is slow and expensive, because the problems are baked into the structure. Building it in from the first day is far cheaper, and it is the reason a custom build has a built-in edge over a template stack.

When we build a site, WCAG AA is the baseline, not an upgrade. That means checked contrast ratios, real headings and landmarks, properly labelled forms, visible keyboard focus, descriptive alt text and respect for reduced-motion settings, all written into the code rather than added afterwards. There is also no pile of third-party plugins quietly introducing their own problems.

No one can honestly promise that a site will never receive a complaint, and we won't. What we can do is remove the failures that are easy to find, easy to prove and easy to prevent, and give you a site that works for more of your customers from day one.

Common questions