StartupQuickstart
Hands typing on a white keyboard at a bright desk

September 17, 2026 · StartupQuickstart

Website accessibility is a sales issue and a legal one

WCAG 2.2 in plain terms, what the WebAIM Million says is broken on almost every site, the lawsuit numbers behind the demand letters, and the fixes to make first.

Most small-business owners hear about website accessibility in one of two ways: a demand letter from a law firm, or a sales email for a plugin that promises to make the problem go away. Neither is a good introduction. Accessibility is mostly a list of ordinary web quality fixes, the same ones that make a site easier for everyone to use, and the most common failures are cheap to repair. This post covers why it matters for revenue and for legal risk, what the current standard asks for, and the fixes to make first.

This is practical guidance from people who build websites, not legal advice. If you have received a demand letter, talk to a lawyer before you change anything.

The sales case comes first

According to the CDC, more than one in four U.S. adults has some type of disability, with cognition (13.9%), mobility (12.2%), hearing (6.2%) and vision (5.5%) among the most common. Not all of those affect how someone uses a website, but many do: a person with low vision who zooms to 200%, someone with a tremor who cannot hit a tiny button, an older customer who struggles with light gray text on white.

Those are your buyers. When the quote form cannot be completed with a keyboard or a screen reader, the lead never arrives, and nothing in your analytics tells you it was lost. Accessibility problems are conversion problems that you cannot see in a dashboard.

The legal case, with real numbers

The Department of Justice's guidance says Title III of the ADA prohibits discrimination by businesses open to the public, and that its requirements apply to the goods and services businesses offer online. The same guidance lists the barriers it has in mind: poor color contrast, using color alone to convey information, missing alt text, videos without captions, forms without labels or error messages, and navigation that only works with a mouse. DOJ leaves businesses flexibility in how they comply, but the direction is clear.

Plaintiffs are using it. Seyfarth Shaw, a law firm that has tracked these filings for years, counted 3,117 website accessibility lawsuits in federal court in 2025, up 27% from 2,452 in 2024 and close to the 2022 peak of 3,255. New York (1,021), Florida (961) and Illinois (585) led. Those numbers exclude state courts and demand letters, which the same analysis says remain significant, so the real volume is higher. Seyfarth attributes part of the 2025 increase to new plaintiffs' firms entering the space.

You do not need to panic about this. You do need to understand that a small business with an inaccessible checkout or contact form is a plausible target, and in our view fixing the key pages now is cheaper and calmer than fixing them on a lawyer's deadline.

What WCAG 2.2 asks for, briefly

The Web Content Accessibility Guidelines are the W3C standard that courts, regulators and auditors point to. Success criteria are graded A, AA and AAA, and Level AA is the usual target. WCAG 2.2 became a W3C Recommendation on 5 October 2023 and added nine success criteria, removing the old 4.1.1 Parsing criterion. The new AA and A items that most often affect small-business sites are:

  • Target Size (Minimum), AA: buttons and links need to be large enough, or spaced far enough apart, to tap reliably.
  • Focus Not Obscured (Minimum), AA: when someone tabs through the page, the focused element cannot be hidden behind a sticky header or cookie banner.
  • Dragging Movements, AA: anything that requires dragging, like a slider, needs a non-drag alternative.
  • Accessible Authentication (Minimum), AA: logins cannot depend on a cognitive test such as remembering or transcribing a code without help like paste or a password manager.
  • Redundant Entry, A, and Consistent Help, A: do not make people retype information they already gave you, and keep help links in the same place across pages.

What is actually broken on most sites

WebAIM runs automated tests on the home pages of the top one million websites every year. The 2026 report found detectable WCAG failures on 95.9% of home pages, with an average of 56.1 errors per page. More useful than the headline is the breakdown. Six categories account for 96% of all detected errors:

  • Low contrast text, on 83.9% of home pages
  • Missing alternative text for images, 53.1%
  • Missing form input labels, 51%
  • Empty links, 46.3%
  • Empty buttons, 30.6%
  • Missing document language, 13.5%

Automated tests cannot judge everything (a tool can see that alt text exists, not whether it is accurate), so a clean scan is not proof of compliance. But this list is an excellent place to start, because every item on it is mechanical to fix.

Skip the overlay widget

Overlay plugins that add a toolbar and claim to fix accessibility automatically are heavily marketed to small businesses. Be skeptical. In April 2025 the FTC approved a final order requiring accessiBe to pay $1 million after alleging that its AI widget did not make all customer websites WCAG compliant, and the order bars the company from claiming its automated products can do so without evidence. A widget does not relabel your forms or rewrite your alt text in a way you can rely on. Fix the source.

The fixes, in the order we would do them

  1. Your money pages first. Do not try to fix the whole site at once. Start with the pages where revenue happens: the contact or quote form, booking or checkout, and the home page. A fully accessible contact form beats a partly accessible 200-page site.
  2. Form labels and error messages. Every input needs a real label tied to it, not just placeholder text that disappears when someone types. Errors should say what went wrong in words, not only by turning the field red. This is the fix most directly tied to leads.
  3. Color contrast. WCAG AA asks for a contrast ratio of at least 4.5:1 for normal-size text. Light gray text, white text on bright brand colors, and text over photos are the usual offenders. Fix it in your design tokens or theme so it fixes everywhere.
  4. Buttons and links with names. Icon-only buttons (the hamburger menu, social icons, a search magnifier) need an accessible name. Linked logos and images need alt text that says where the link goes. This clears the empty links and empty buttons categories.
  5. Alt text that describes. Meaningful images get a short, literal description. Purely decorative images get an empty alt attribute so screen readers skip them.
  6. Keyboard and focus. Unplug your mouse and try to complete your contact form with Tab, Shift+Tab, Enter and Space. You should always see where focus is, nothing should trap you, and no sticky element should hide the focused field.
  7. Page language and headings. Set the language attribute on the page, and use headings in order so screen reader users can navigate by structure.
  8. Captions and target sizes. Caption any video with spoken content, and make sure tap targets on mobile are not crammed together.

For a typical small-business site built on a modern theme or framework, items 2 through 7 on the key pages are days of work, not months. The time goes into the components: fix the shared form field, button and color tokens once and every page that uses them improves.

How to keep it fixed

  • Run a free automated checker on your key pages after every significant change, and treat new errors like broken links.
  • Do a five-minute keyboard test of the contact form before every launch.
  • Write the rules into your content process: every uploaded image gets alt text, every new form uses the shared field component.
  • Publish an accessibility statement with a way to report problems, and answer those reports quickly.

When it is not worth a big project: if your site is a single page with a phone number and no forms, fix contrast, alt text and the page language, and move on. When it is worth outside help: if you take payments or bookings online, sell to government or enterprise buyers who ask for conformance reports, or have already received a letter. In those cases a manual audit by someone who tests with assistive technology is money well spent.

A good first step this week is to run your contact page through an automated checker and the unplugged-mouse test. If the results are longer than you expected, that list is the plan.

Sources

Want systems like this built for you?

We build and run data pipelines, websites, and AI automation for startups.

Book an intro call
Website accessibility is a sales issue and a legal one · StartupQuickstart