How much does accessibility remediation cost?

Accessibility remediation cost depends far less on how many errors a scanner reports than on how many places the same mistake was written. A site with 4,000 flagged issues can be cheap to fix if they come from three shared templates. A site with 40 issues can be expensive if they sit inside a custom date picker, a payment iframe and a drag-and-drop builder. So there is no honest price per page, and I won't invent one here. What you can do is work out the four things that set the bill: how much of your markup is shared versus one-off, how many custom interactive components you own, how many multi-step journeys you need to fix (checkout, signup, account), and how much human testing the result needs, because automated tools find roughly 30 to 57% of issues and the rest needs a person. Get those answers before you ask for a quote and you can read the quote critically. Below: where the effort hides, and what changes the number in the EAA and ADA context.

What does accessibility remediation cost depend on?

Four things, in roughly this order of impact.

1. Shared versus one-off code. A missing label in a form component used on 200 pages is one fix. The same missing label hand-written into 200 CMS pages is 200 fixes.
2. Custom interactive components. Native HTML (<button>, <select>, <dialog>) arrives with most of its keyboard and screen reader behaviour for free. A custom combobox built from <div>s has to have all of it rebuilt: roles, states, focus handling, keyboard support.
3. Journeys, not pages. WCAG says a page in a multi-step process only conforms if every page in that process conforms (W3C). Fixing step one of checkout and leaving step four broken buys you nothing a user can feel.
4. Verification. Somebody has to confirm the fixes work with a keyboard and a screen reader. That is labour, and it does not shrink just because the code change was small.

The raw error count isn't on the list. It matters, but mostly as a symptom of the first two.

Why does fixing a template cost less than fixing a page?

Because most web accessibility failures are the same handful of mistakes repeated.

The WebAIM Million 2026 report tested a million home pages and found detectable WCAG failures on 95.9% of them, with 56.1 errors per page on average. Six categories accounted for 96% of everything detected: low-contrast text (83.9% of home pages), missing alt text (53.1%), missing form labels (51%), empty links (46.3%), empty buttons (30.6%) and missing document language (13.5%) (WebAIM).

Look at that list as a developer and most of it lives in shared code. Contrast lives in your design tokens. Empty buttons are almost always an icon button component with no accessible name, something like <button class="icon-close"><svg>…</svg></button>. A missing lang attribute is one line in one layout file. Fix the source and the count drops across every page that inherits it.

That is why the first useful step in any remediation estimate is grouping. Take the scan output, group findings by the component or template that produces them, and count the groups, not the instances.

The exception is content. Alt text on product photos, link text in blog posts, heading structure in CMS pages: these are written by people, page by page, and every instance costs its own few minutes. If most of your findings are content findings, budget editor time, not developer time.

Which accessibility fixes are cheap and which are expensive?

A rough sorting, by effort rather than by money, since your rates and stack decide the money:

The right-hand column is where estimates go wrong. A third-party payment iframe is a good example: you may not be able to change its code at all, so the "fix" is either a vendor conversation or a documented limitation in your accessibility statement. Neither is developer hours. Both take calendar time.

How much of the work can an automated scan find?

Somewhere between roughly 30% and 57% of issues, depending on how you count.

Deque's analysis of more than 2,000 audits, covering over 13,000 pages and nearly 300,000 issues, found about 57% of issues by volume were covered by automated testing (Deque). Count by WCAG success criteria instead of by volume and the share is much lower, nearer 30%, because the criteria a machine can fully check are the ones that fail most often.

For cost, that means a scan inventories the frequent, mechanical problems quickly, and says nothing about the expensive ones: whether focus lands somewhere sensible after a modal closes, whether your alt text is meaningful, whether a screen reader user can finish checkout. Those need a person, and they are disproportionately the right-hand column of the table above. We break down the human side in what a real accessibility audit includes.

So a quote built only from a scan report is a quote for the easy half. Ask any vendor how they will find the rest.

Is an accessibility overlay a cheaper way to remediate?

It is cheaper to buy. It is not remediation.

An overlay injects a script that tries to patch the page at runtime. The underlying code stays as it was, so the cost you were trying to avoid is still sitting in your codebase. The US Federal Trade Commission ordered accessiBe to pay $1 million in January 2025 over claims that its widget could make any website WCAG compliant; the FTC said the tool "did not make all user websites WCAG-compliant" and called the claims "false, misleading, or unsubstantiated" (FTC).

My view, stated plainly: an overlay subscription is a recurring cost that leaves the original remediation bill untouched, so over any real time horizon it is the more expensive option. We built wcagc to report the exact element and selector that needs to change, because fixing the source is the only spend that keeps paying off. More on the trade-off in overlay vs code-first accessibility.

How do you estimate remediation cost before you get a quote?

You can get most of the way in an afternoon.

1. Pick the journeys that matter. Homepage, one product or content page, search, signup, login, checkout or the main task in your app. Five to eight views is enough to start.
2. Scan them, including the logged-in steps. Then group findings by component and template. Write down the number of root causes, not the number of findings.
3. List your custom widgets. Every interactive thing your team built instead of using a native element goes on the list. Each one needs a keyboard and screen reader check by a person.
4. List your third parties. Payment, chat, booking, video players, cookie banners. For each, find out whether the vendor publishes an accessibility conformance report and whether you can configure the problem away.
5. Do the manual pass on one journey. Tab through checkout with no mouse. Turn on VoiceOver or NVDA and try to complete it. Use the WCAG checklist to track what the scan couldn't decide. This tells you how big the hidden half is on your site specifically.

Hand the result to an internal team or an agency and the estimate you get back will be grounded in your code instead of a per-page guess.

Do the EAA or US tax rules change the cost?

They change how you document it and, for some US businesses, who pays part of it.

Under the European Accessibility Act, Article 14 allows an economic operator to set aside a specific requirement where it would impose a disproportionate burden. The assessment uses the criteria in Annex VI, which include the ratio of the net cost of compliance to the operator's overall costs and to its net turnover, weighed against the estimated benefit to people with disabilities (EUR-Lex). There is no threshold figure in the law, the assessment is per requirement, and you have to document it. In practice that means a cost estimate like the one above is the evidence an Annex VI assessment needs. We cover the details in the disproportionate burden exemption.

In the US, the Disabled Access Credit in 26 U.S.C. § 44 equals 50% of eligible access expenditures above $250 and up to $10,250 in a tax year, so a maximum credit of $5,000. An eligible small business had gross receipts of no more than $1,000,000 or no more than 30 full-time employees in the preceding year, and eligible expenditures include amounts paid to remove "communication" barriers. Whether a given web remediation invoice qualifies is a question for your accountant. It is filed on IRS Form 8826.

How do you stop paying for the same fixes twice?

Catch regressions where they are cheapest: before they ship.

A fixed component stays fixed only if nobody reintroduces the bug. Add automated checks to your pipeline so a pull request that removes a label or breaks contrast fails before review, as described in accessibility testing in CI. Then scan the same journeys on a schedule to catch drift in content and third-party embeds; the trade-offs are in accessibility monitoring vs audit.

The teams that spend least treat the first remediation as the expensive one and every later release as maintenance. The ones that spend most pay for the same fixes every year.

Frequently asked questions

How much does accessibility remediation cost for a website?

There is no reliable per-page or per-site price, because cost depends on how much of your code is shared, how many custom interactive components you have, how many multi-step journeys need fixing, and how much manual testing is required.

Is it cheaper to fix accessibility in templates or page by page?

Templates and shared components are almost always cheaper, because one fix applies to every page that uses them. WebAIM's 2026 data shows six common error types account for 96% of detected errors, and most of them live in shared code like design tokens, form components and icon buttons.

Can an automated scanner tell me the full remediation cost?

No. Automated tools find roughly 30 to 57% of accessibility issues depending on how you count, and the issues they miss, such as focus management and screen reader behaviour in custom widgets, tend to be the most expensive to fix.

Is an accessibility overlay cheaper than remediation?

An overlay is cheaper to buy, but it does not change your underlying code, so the remediation work remains. The FTC ordered accessiBe to pay $1 million in 2025 over claims its widget could make any website WCAG compliant.

Does remediation cost count toward the EAA disproportionate burden exemption?

It is the main input. Annex VI of the EAA weighs the net cost of compliance against your overall costs, your net turnover and the benefit to people with disabilities. The assessment is per requirement, has no fixed threshold, and has to be documented.

Size the work before you buy it

The cheapest first step is knowing how many root causes you actually have. Run a free scan on your checkout or signup journey, group what it finds by component, and you will know within an hour whether you are looking at a template fix or a rebuild. The manual half still needs a person.

Pavel Charkasau, founder, wcagc.com. Last updated 4 October 2026.

Sources

• The WebAIM Million: the 2026 report, WebAIM — February 2026, updated 30 March 2026; detectable WCAG 2 failures on 95.9% of home pages; 56.1 errors per page on average; six categories (low contrast 83.9%, missing alt text 53.1%, missing form labels 51%, empty links 46.3%, empty buttons 30.6%, missing document language 13.5%) account for 96% of all errors detected. Accessed 4 October 2026.
• Automated testing study identifies 57% of digital accessibility issues, Deque — 10 March 2021; more than 2,000 audits, over 13,000 pages, nearly 300,000 issues; about 57% of issues covered by automated testing by volume. Accessed 4 October 2026.
• Understanding Conformance, WCAG 2.2, W3C — Conformance Requirement 3, complete processes: a page in a series that presents a process conforms only if every page in the process conforms. Accessed 4 October 2026.
• FTC order requires online marketer to pay $1 million for deceptive claims that its AI product could make websites compliant, FTC — 3 January 2025; accessiBe; "accessWidget did not make all user websites WCAG-compliant and these claims were therefore false, misleading, or unsubstantiated." Accessed 4 October 2026.
• Directive (EU) 2019/882 (European Accessibility Act), EUR-Lex — Article 14 (disproportionate burden, assessment and documentation) and Annex VI (criteria: net cost of compliance relative to overall costs and to net turnover, weighed against estimated benefits to persons with disabilities). Accessed 4 October 2026.
• 26 U.S. Code § 44, Expenditures to provide access to disabled individuals, Legal Information Institute — credit of 50% of eligible access expenditures exceeding $250 but not exceeding $10,250; eligible small business: gross receipts not over $1,000,000 or not more than 30 full-time employees in the preceding year; expenditures include removing "communication" barriers. Accessed 4 October 2026.
• About Form 8826, Disabled Access Credit, IRS — "Eligible small businesses use Form 8826 to claim the disabled access credit." Accessed 4 October 2026.