Image description: A small-business owner’s desk with a laptop showing a website, a calculator, and a printed invoice, photographed top-down on warm wood, signalling the budget-and-decision framing of an accessibility cost guide.

Reading Time: 12 minutes

If you have landed here, you are probably a business owner, a marketing lead, or an office manager who got a forwarded email — maybe a demand letter, maybe a nervous note from legal — and you are trying to answer four questions at once. Do I really have to do this? What happens if I do not? What will it cost? And can I just fix it myself? These are the most-asked questions about website accessibility on the open web, and they are usually answered with either a scare tactic or a sales pitch. This guide answers all four plainly, with 2026 numbers, and routes you to the next concrete step.

The short version: yes, the law almost certainly applies to you; the most likely consequence of ignoring it is a demand letter that costs more than getting compliant would have; the cost ranges from free to five figures depending entirely on your site’s size and how it was built; and you can do a meaningful chunk yourself but not all of it. Now the detail.

Do you actually need an accessible website?

For almost every organisation that serves the public online, the answer is yes — and not as a nice-to-have. A disability-rights law already covers your website in every major market:

  • United States — the Americans with Disabilities Act (ADA). Courts and the Department of Justice treat a public-facing website as a “place of public accommodation” under Title III, and there is no small-business exemption. Our ADA Title III web accessibility guide walks through exactly who is covered.
  • European Union — the European Accessibility Act (EAA) has applied to most consumer-facing digital products and services since June 2025, and it reaches non-EU companies that sell into the EU.
  • United Kingdom — the Equality Act 2010, plus the Public Sector Bodies regulations for government services.
  • Canada, Australia, and 50-plus other jurisdictions — each with its own statute and a working enforcement record.

The benchmark every one of these regimes points to is the same technical standard: WCAG 2.2 Level AA. So the real question is not “does this apply to me” — it almost certainly does — but “how exposed am I right now, and what does closing that gap cost?” For the full picture of what “compliance” even means across these layers, see our accessibility compliance explainer.

What happens if your website isn’t accessible?

The risk is not theoretical, and it usually arrives by email before it arrives by lawsuit.

Demand letters. The most common first contact in the US is a letter from a plaintiff’s firm alleging that a disabled user could not use your site, and offering to settle. These settle quietly, typically for $5,000 to $25,000, before any court filing. Many businesses receive several over a few years.

Lawsuits. If you ignore the letter, a Title III suit can follow. Roughly 4,000 federal web-accessibility cases are filed in the US each year, concentrated among a small number of firms — our firm-by-firm field guide tracks who. Litigated cases cost far more than demand-letter settlements once you add legal fees; the largest resolved matters reach seven figures, as our survey of the 25 largest settlements documents.

Regulatory action abroad. In the EU, market-surveillance authorities under the EAA can issue corrective orders and administrative fines that vary by member state. There is no demand-letter cottage industry there — the enforcement comes from the state.

Lost customers. The quietest cost is the largest. Around one in six people lives with a disability. An inaccessible checkout, an unlabelled form, or a video with no captions turns those visitors away silently — no letter, no lawsuit, just a lower conversion rate you never attribute to the real cause.

How much does website accessibility cost?

There is no single number, because cost scales with two things: how big and complex your site is, and how it was built. A five-page brochure site on a mainstream template is a different problem from a custom single-page application with a checkout, a dashboard, and a media library. Here is the realistic 2026 range, broken into the layers most organisations actually buy.

What you’re buyingTypical 2026 costWhat it gets you
Automated scan (DIY)FreeA baseline. Free tools — axe DevTools, Lighthouse, WAVE, and our own free WCAG 2.2 scanner — catch roughly 30–40% of issues: contrast, alt text, form labels, structure.
One-time manual audit$1,500–$5,000 (small)
$5,000–$15,000 (mid)
$15,000–$50,000+ (large/app)
A professional review, ideally including testers who use assistive technology, that finds what scanners cannot — broken screen-reader flows, keyboard traps, mislabelled custom widgets.
Remediation (the fixes)$2,000–$10,000 (small)
$25,000–$150,000+ (complex app)
Developer time to fix what the audit found. Usually the largest line item, and the one that varies most with how the site was built.
Ongoing monitoring$1,000–$30,000+ / yearA platform that re-scans on a schedule and flags regressions on every deploy, so a fixed site stays fixed.
Overlay widget$490–$3,500 / yearAvoid. Does not make you compliant and does not reduce lawsuit risk — see below.

A useful way to read the table: a small business can reach a defensible posture for a low four-figure sum — a one-time audit, a modest remediation sprint, and an entry-level monitoring subscription. A large organisation with a custom application should budget for an annual programme in the tens of thousands. Either way, the all-in cost of getting compliant is, for the overwhelming majority of businesses, less than the cost of a single litigated lawsuit.

Can you fix it yourself?

Partly — and the DIY part is genuinely worth doing first, because it is free and it removes the most common, most-cited failures.

A technically confident team can run a free scanner, work through the findings, and close a real share of the gap without spending a dollar: add alternative text to images, fix colour-contrast failures, label every form field, restore a logical heading order, and make sure everything works with the keyboard alone. Our step-by-step WCAG 2.2 guide is built for exactly this. That work handles the 30–40% of issues automation can see.

What you cannot reliably do yourself is the other 60%. No scanner — and no non-disabled developer guessing — can tell you whether a screen-reader user can actually complete your checkout, whether your custom date-picker announces itself correctly to NVDA, or whether your modal traps focus the way it should. That judgement comes from manual audits by people who use assistive technology daily. DIY gets you a strong start and a smaller invoice; it does not get you all the way.

One thing not to buy as a shortcut: the accessibility overlay widget. These are third-party scripts that drop an accessibility toolbar onto your site for a few hundred to a few thousand dollars a year, marketed as instant compliance. They are not. Sites running overlays have been sued at least as often as sites without them, and plaintiffs increasingly name the overlay in the complaint. We tracked the vendors’ retreat in our report on the end of the overlay era. Spend the money on an audit and real fixes instead.

When to hire a professional

Hire help when any of these are true: you run a checkout, a login, or any transaction that a customer must complete; your site is a custom application rather than a templated marketing site; you have already received a demand letter; or you sell into the public sector or the EU, where the conformance bar is contractual and explicit. In those situations the cost of getting it wrong dwarfs the cost of an audit.

For the ongoing layer, do not rely on a one-time audit alone — a site that passes today breaks on the next deploy. A continuous monitoring platform re-scans on a schedule and flags regressions before they reach production. Compare two or three vendors on what they actually test and how they surface regressions — axe Monitor, Siteimprove, Level Access, and Qualibooth are the usual shortlist — and weigh whether the platform pairs automated monitoring with periodic manual auditing, since neither alone is sufficient.

Your next step, by situation

”I just want to know where I stand.” Run a baseline today. Our free WCAG 2.2 scanner gives you a first read on any public URL in minutes — no cost, no commitment.

”I got a demand letter.” Do not ignore it, and do not buy an overlay in a panic. Commission a manual audit so you can show a good-faith remediation plan, and read the ADA Title III guide for what the obligation actually is.

”I want to fix this properly, long-term.” Budget for the three layers — audit, remediation, monitoring — and stand up continuous monitoring so the fix holds. That is what a durable compliance posture looks like.

Frequently asked questions

Do I really need to make my website accessible?

In almost every case, yes. If you sell to or serve the public in the US, the EU, the UK, Canada, or Australia, a disability-rights law already applies to your website — the ADA in the US, the European Accessibility Act in the EU, the Equality Act in the UK. The obligation does not depend on your company’s size for most regimes, and there is no exemption for small businesses under ADA Title III. The practical question is not whether the rule applies but how much risk you are carrying by ignoring it.

What happens if my website isn’t ADA compliant?

The most common consequence in the US is a demand letter from a plaintiff’s firm, followed by a Title III lawsuit if you do not respond. Roughly 4,000 federal web-accessibility cases are filed each year, plus a much larger volume of pre-suit demand letters that settle quietly for $5,000 to $25,000 each. In the EU, market-surveillance authorities under the European Accessibility Act can issue corrective orders and fines. Beyond the legal exposure, an inaccessible site simply loses the roughly one-in-six customers who have a disability.

How much does ADA website compliance cost?

There is no single figure because cost scales with site size and complexity. A baseline automated scan is free. A one-time professional manual audit runs roughly $1,500 to $5,000 for a small marketing site, $5,000 to $15,000 for a mid-size site, and $15,000 to $50,000 or more for a large or complex web application. Remediation — the developer time to fix what the audit finds — is usually the largest line item and varies with how the site was built. Ongoing monitoring runs roughly $1,000 to $30,000 a year. Most organisations should budget for an audit plus remediation plus continuous monitoring, not a one-off fix.

Can I fix my website’s ADA compliance myself?

Partly. A technically confident team can run free scanners, fix the obvious failures — missing alt text, low colour contrast, unlabelled form fields, broken heading structure — and remove a meaningful share of risk at near-zero cash cost. What you cannot do yourself reliably is judge whether a screen-reader user can actually complete a checkout, or whether a custom widget exposes the right roles and states. Those require manual testing by people who use assistive technology daily. DIY handles the first 30 to 40 percent; the rest needs expertise.

Are accessibility overlay widgets a cheap way to become compliant?

No. Overlay widgets — the third-party scripts that add an accessibility toolbar for roughly $490 to $3,500 a year — do not make a site compliant, and sites running them have been sued just as often as sites without them. Plaintiffs increasingly name the overlay itself in the complaint. Treat an overlay as marketing, not remediation; the money is better spent on an audit and real code fixes.

How much does ongoing accessibility monitoring cost?

Continuous monitoring platforms that re-scan your site on a schedule and flag regressions typically run from roughly $1,000 a year for a small site to $30,000 or more a year for a large estate, depending on page volume and features. Compare two or three vendors — axe Monitor, Siteimprove, Level Access, and Qualibooth — on what they actually scan, how they surface regressions, and whether they pair with manual auditing, rather than on the dashboard alone.

Accessibility is rarely as expensive as the fear around it suggests, and almost always cheaper than the alternative. Start with a free baseline, fix what you can, and buy expertise where it counts.