Website Accessibility: The Real Cost of Ignoring It

According to the Seyfarth ADA Title III Report, more than 8,000 ADA Title III website accessibility lawsuits get filed in federal court every year, and settlements run from low five figures to well past $100,000. Per CDC data, 1 in 4 US adults has a disability, roughly 61 million people. If your site excludes them, that is 25 percent of the customers you already paid to reach, gone before they ever bought anything.

Fixing an existing site typically costs $5,000 to $15,000 and takes 4 to 8 weeks. Building a new site accessible from day one costs 10 to 15 percent more upfront and saves 3 to 5 times that later. Doing nothing does not freeze the risk in place. It grows every month your traffic grows, because more visitors means more chances someone hits the barrier, or files the complaint.

This guide explains what accessibility actually means for your business, what a fix costs, and what to do first.

TL;DR

An inaccessible site excludes 1 in 4 US adults, roughly 61 million people, and settlements for ADA website lawsuits run from low five figures past $100,000.
WCAG 2.2 Level AA is the baseline US courts and most regulators reference. Aim there, not for perfection.
Fixing an existing site: $5,000 to $15,000, 4 to 8 weeks. Building accessible from day one costs 10 to 15 percent more and saves 3 to 5 times later.
Skip accessibility overlays. Courts have already pushed back on them. The fix has to touch the actual code.
Alt text, color contrast, keyboard navigation, and form labels handle roughly 70 percent of real issues, and are the cheapest place to start.

What this is actually costing you
The legal exposure: ADA and WCAG
What a fix costs
Building accessible from day one
Accessibility myths
Reflecting on what this is really about
For your engineer
FAQ
Next steps

What this is actually costing you

A quarter of your market. Per CDC data, 1 in 4 US adults has a disability, roughly 61 million people. If your site excludes them, you already paid to reach a customer who could not complete the purchase.

Legal exposure that grows with your traffic. Retailers, nonprofits, software companies, law firms, and medical practices all get sued. The theory that a small business is "too small to get sued" has not held up well in practice.

Search visibility you are leaving on the table. Alt text helps image search, captions help video search, semantic markup helps crawlers, and faster, cleaner pages tend to rank better. Accessibility and SEO overlap more than most teams expect.

A worse experience for everyone, not only disabled visitors. High contrast helps anyone reading on a bright screen. Keyboard navigation helps anyone whose trackpad is misbehaving. Plain language helps a non-native English speaker. Captions help anyone watching without sound.

A reputational tell. Customers, partners, and journalists notice. An inaccessible site increasingly reads as a sign the business cuts corners elsewhere, whether or not that is fair.

Documented accessibility effort, an audit, real fixes, ongoing maintenance, is also the strongest defense if a complaint shows up. You cannot promise zero risk. You can stop being the easy target.

The legal exposure: ADA and WCAG

The Americans with Disabilities Act, passed in 1990, requires businesses to provide equal access to goods and services, and courts have applied it to the internet for years. If you operate in the US, your site is in scope. The Department of Justice can sue directly, and private plaintiffs file under Title III. Settlements run roughly $15,000 to $50,000, with some exceeding $100,000, per the Seyfarth Title III Report.

WCAG, the Web Content Accessibility Guidelines from the W3C, is not a US law on its own, but courts and federal procurement reference it as the standard for "reasonable" accessibility. It has three levels: A is a floor, not a goal. AA is the industry baseline, and where you should aim. AAA is for specialized cases like government and education, and most commercial sites do not need it.

What a fix costs

A real fix runs in four stages. An automated scan, about a day, catches the obvious issues: on a first pass, I typically find missing alt text on 30 to 50 percent of images, poor color contrast on 20 to 40 percent of pages, and missing form labels on 15 to 30 percent of forms. Manual testing, one to two weeks, catches what automated tools miss, since tools alone only catch 60 to 70 percent of real issues. Optional user testing with five people who have disabilities, $1,000 to $3,000, catches the remaining issues that would otherwise surface as a complaint after launch.

The remediation itself, 4 to 8 weeks for a typical 50 to 100-page site, breaks down roughly like this:

Fix	Effort	Cost
Add alt text	1 to 2 weeks	$1,000 to $3,000
Fix color contrast	1 week	$500 to $1,000
Fix keyboard navigation	2 to 3 weeks	$2,000 to $4,000
Add form labels	1 week	$500 to $1,000
Add captions to videos	1 to 2 weeks	$1,000 to $3,000
Add ARIA labels	1 to 2 weeks	$1,000 to $2,000

Total for a typical site: $5,000 to $15,000. After the fix, ongoing maintenance, code review with accessibility checks, quarterly audits, a way for visitors to report issues, runs 5 to 10 percent of the original remediation cost per year.

Building accessible from day one

If you are building a new site, accessibility costs about 10 to 15 percent more upfront and saves 3 to 5 times that in remediation later. That premium buys semantic structure from the first sketch, high contrast and predictable layouts by default, and testing with a keyboard and a screen reader before anything ships, instead of retrofitting all of it after a complaint.

Accessibility myths

"Accessibility makes sites ugly." Good accessibility is good design. High contrast, clear labels, and simple navigation help everyone. The "ugly accessible site" is almost always an ugly site.

"We can use an accessibility overlay." Overlays paste a widget on top of the same broken code. They move a few automated metrics and do not fix the underlying issues. Courts have already pushed back on overlay-only fixes. The fix has to touch the code.

"Accessibility is only for legal compliance." Compliance is the floor. The ceiling is a 25 percent larger addressable market, better search visibility, and a better experience for every visitor.

"Blind users don't visit websites." According to WHO data, at least 2.2 billion people globally have some form of vision impairment, and they use the internet every day.

"Accessibility requires perfect code." WCAG 2.2 Level AA is the realistic target, not perfection. Some advanced widgets only reach Level A, and that is fine. Progress beats perfection.

Reflecting on what this is really about

After 17 years of building sites, the accessibility projects that paid off were never the ones driven by fear of a lawsuit. They were the ones where the team treated accessibility like quality, full stop.

A site that is keyboard-navigable, fast, contrast-correct, and clearly labeled is a site that was built carefully. A site that fails accessibility checks usually fails performance and mobile checks at a similar rate. The accessibility audit is a stand-in for one question: did anyone actually look at this with a critical eye. Teams that cared, not only complied, almost always saw better conversion and lower support volume as a side effect, not the goal.

If you take one thing from this guide, take this: run a quality project, and let the accessibility score be a side effect of it.

For your engineer

The rest of this section is written for the person doing the technical work: your developer, or whoever you bring in for the project.

WCAG 2.2 Level AA, the four pillars. Perceivable: alt text on every meaningful image (<img src="hero.jpg" alt="Sunlit beach with palm trees and calm blue water">, never a bare <img src="hero.jpg">); color contrast of at least 4.5 to 1 for body text and 3 to 1 for large text, checked with the WebAIM Contrast Checker; captions and transcripts on video (<track kind="captions" src="captions.vtt" srclang="en" label="English">). Operable: full keyboard reachability with standard form markup (<label for="email">Email</label><input id="email" type="email">), a visible focus indicator (button:focus-visible { outline: 2px solid #0066cc; outline-offset: 2px; }), and no content flashing more than 3 times per second. Understandable: plain language over jargon, consistent navigation across pages, and every input carrying a real <label>, since a placeholder is not a label. Robust: semantic HTML over generic containers (<a href="/">Home</a> and <button type="button">Menu</button> instead of a clickable <div>), with ARIA labels only where semantic markup runs out (<button aria-label="Close menu">).

The issues that show up most. Missing alt text is the single highest-impact fix, since it is the most common gap and affects the largest assistive-tech population; write what the image actually shows, not "photo" or "icon." Poor color contrast needs a pass with the WebAIM checker on every text and background pairing. No keyboard navigation gets caught by tabbing through every page yourself; if you cannot reach something, neither can a keyboard user. Unlabeled form fields make a screen reader announce "edit, blank" instead of the field's purpose. Missing video captions mean deaf users miss the content entirely; auto-captions work as a first draft, then need a human edit pass. Inaccessible PDFs, usually scanned images with no text layer, need OCR or a conversion to HTML, which is almost always more accessible than a PDF. Auto-playing media and leftover Flash startle users and break screen reader output; replace with HTML5 video, no autoplay, visible controls.

Testing stack. WAVE and axe DevTools for automated scanning, Google Lighthouse for a baseline score, and manual passes with NVDA or JAWS for screen reader testing, a full keyboard pass, a color blindness simulation, and testing at 200 percent zoom on a real mobile device, not only the browser emulator. In CI, axe-core or pa11y catch regressions before they ship.

Building it into a design system. Buttons keyboard-reachable with visible focus by default. Forms with mandatory labels and clear error states. Cards with a real heading hierarchy and descriptive link text. Modals with focus trapped inside and restored on close. Icons hidden from screen readers when decorative, labeled when functional. A solid design system prevents most accessibility issues before they are written; a weak one forces every developer to relearn the same lessons independently.

FAQ

Is accessibility a legal requirement in the US?

Yes, under the ADA. US courts have read it to require WCAG-level "reasonable" accessibility for public-facing websites. Per the Seyfarth Title III Report, thousands of website lawsuits land in federal court each year. Even if you have not been targeted, the exposure is real.

What's the difference between ADA and WCAG?

ADA is the law. WCAG is the standard that defines what "accessible" looks like. Courts use WCAG 2.1 or 2.2 Level AA as the practical baseline.

Do I need WCAG AAA?

No. AA is the industry standard and enough for ADA exposure on most commercial sites. AAA is for specialized contexts like government, education, or certain healthcare settings.

How much does accessibility cost?

Audit and fix on an existing site: $5,000 to $15,000, 4 to 8 weeks. Building accessible from day one: a 10 to 15 percent premium on development. Annual maintenance: 5 to 10 percent of the original remediation cost.

What's the single highest-impact fix?

Alt text. It is the most common missing element, on 30 to 50 percent of sites, and it directly affects the largest assistive-tech population. Fix alt text and you have handled roughly a third of all accessibility issues.

Do I have to caption every video?

Ideally yes. Practically, prioritize the videos on your homepage, landing pages, and core product pages. The more you caption, the better the experience, and the better the search visibility, since captions get indexed.

Next steps

Accessibility means anyone can use your site. WCAG 2.2 Level AA is the line. An existing site typically needs a $5,000 to $15,000 audit-and-fix pass. A new site is 10 to 15 percent more expensive to build right and 3 to 5 times cheaper to maintain over time. Skip overlays. Start with alt text, contrast, keyboard access, and labels.

Get a quote in 60 seconds. I will review your site, point at the accessibility issues that matter most, estimate remediation cost, and explain your real legal exposure. Honest feedback, not a sales pitch.

Your Website Is Turning Away a Quarter of Your Customers

If a blind, deaf, or motor-impaired visitor cannot use your site, you are turning away a quarter of your potential customers, and you may be one complaint away from a five-figure settlement.