The cost to make a WordPress site ADA compliant is decided mainly by the theme and page builder, not by how many pages you have. A site on a clean, accessible theme often needs a few days of fixes to contrast, alt text, form labels, headings and link text. A site whose markup is generated by a heavy page builder usually needs its templates rebuilt, which costs roughly what a redesign costs. At WPBuildAI we price accessibility work only after an audit, because the split between template problems and content problems is the whole estimate. Below: what “ADA compliant” means for a website in 2026, what the work involves, what drives the cost up or down, why overlays are not the shortcut they claim to be, and when a rebuild is the cheaper route.
What does “ADA compliant” mean for a WordPress website?
The Americans with Disabilities Act was written before websites, and for private businesses there is still no federal regulation listing technical web requirements. The Department of Justice’s guidance on web accessibility says the ADA applies to goods and services businesses offer on the web, and names the Web Content Accessibility Guidelines and the Section 508 standards as helpful guidance rather than mandatory rules.
In practice, the target everyone works to is WCAG at level AA, version 2.1 or the newer 2.2. That is what accessibility audits test against, what settlements in demand-letter cases usually reference, and what the government uses for its own rule.
That government rule is the one formal standard. The DOJ’s 2024 rule for state and local governments requires WCAG 2.1 level AA for their websites and mobile apps. According to the ADA.gov summary of the rule, an interim final rule published in April 2026 extended the compliance dates: April 26, 2027 for governments serving 50,000 people or more, and April 26, 2028 for smaller ones and special districts. If you build sites for public bodies, those dates are your deadline. If you run a business, they are a strong signal of which standard a court will reach for.
Businesses selling into Europe have a second reason to care: the European Accessibility Act covers e-commerce services and has applied since June 2025, with an exemption for service-providing microenterprises.
What are the most common accessibility problems on WordPress sites?
The same few failures account for most of what an audit finds, and they are not specific to WordPress. The WebAIM Million analysis of the top million home pages found detectable WCAG failures on 95.9 percent of them in its 2026 report, with an average of 56.1 errors per page.
| Problem | Share of home pages (WebAIM 2026) | Where it lives on WordPress | Typical fix |
|---|---|---|---|
| Low contrast text | 83.9% | Theme colours, builder presets | Adjust the palette once in the theme |
| Missing image alt text | 53.1% | Content, media library | Write alt text per image; train editors |
| Missing form labels | 51% | Form plugin settings, theme search box | Enable visible labels, fix templates |
| Empty links | 46.3% | Icon links, social icons, logo links | Add accessible names in templates |
| Empty buttons | 30.6% | Menu toggles, sliders, builder widgets | Add labels in the component code |
| Missing page language | 13.5% | Theme header | One line in the theme |
Those six failures explain most of the cost spread. Contrast, page language, icon links and menu buttons live in the theme, so they are fixed once for the whole site. Alt text lives in content, so it scales with the number of images. Custom widgets built by a page builder live in the builder’s output, which you often cannot edit cleanly at all.
What does the work actually involve?
A proper job has four stages, and skipping the first is how projects go over budget.
- Audit. Automated tools catch perhaps a third of WCAG issues; the W3C’s list of evaluation tools is a good starting point. The rest needs a person: keyboard-only navigation through every template, a screen reader pass on key flows such as checkout and contact, and checks of zoom and reflow. The W3C’s easy checks are a reasonable first pass you can do yourself.
- Template fixes. Header, navigation, footer, forms, product and post templates, and any reusable blocks. Fix these once and every page improves.
- Content fixes. Alt text, heading order inside posts, descriptive link text instead of “click here”, captions or transcripts for video, and accessible PDFs if you publish them.
- Process. Editor guidance, an automated check on new content, and periodic manual review, so the site stays fixed.
What drives the cost up or down?
| Cost driver | Pushes cost down when | Pushes cost up when |
|---|---|---|
| Theme | Modern block theme, semantic markup | Old theme or heavy builder with nested divs |
| Interactive widgets | Few, standard components | Sliders, tabs, mega menus, popups from plugins |
| Forms | One form plugin with label support | Many forms, custom multi-step flows |
| Media | Few images, no video | Large image library, video without captions |
| Documents | No PDFs | Many PDFs that must be made accessible |
| Ecommerce | Simple shop | Custom checkout steps, filters, variant pickers |
| Ownership | Clear admin access, documented setup | Unknown plugins, no developer contact |
Rough patterns we see in practice, not published rates: a small brochure site on a clean theme lands in the range of a few days’ work. A larger site with a page builder and many interactive widgets can run to weeks, mostly spent fighting generated markup. PDFs and video are frequently the largest surprise, because each document or video is its own small project.
WordPress core itself is not the obstacle. The project has an accessibility team and themes tagged as accessibility-ready must meet published requirements, as described in the theme accessibility handbook. The cost comes from what has been added on top.
Do accessibility overlay plugins work?
Overlays are scripts that add a toolbar or attempt automatic fixes in the browser. They are cheap and quick, and they are not a substitute for fixing the code.
An overlay cannot reliably invent a meaningful label for an unlabeled form field, fix a heading structure that skips levels, or make a custom JavaScript slider keyboard operable. Many disabled users report that overlays interfere with the assistive technology they already use, and the Overlay Fact Sheet, signed by hundreds of accessibility practitioners, advises against relying on them.
There is also regulatory history. In January 2025 the FTC ordered overlay vendor accessiBe to pay one million dollars over claims that its AI tool could make any website compliant, as TechCrunch reported. If a product promises instant compliance, treat that as a warning.
Should you fix, rebuild or buy an overlay?
Most owners end up choosing between four routes, and the audit result points to one of them fairly clearly.
| Route | Best for | Why it works | Main limit | Verdict |
|---|---|---|---|---|
| Accessible rebuild (the WPBuildAI route) | Builder-heavy sites that also need speed or maintenance work | Fixes templates at the source and removes builder markup | A bigger project than targeted fixes | Best when most issues sit in templates |
| Targeted fixes on the current theme | Clean themes with content-level issues | Cheapest route to real conformance | Depends on the theme staying maintained | Best when the theme is sound |
| Swap the theme, keep WordPress | Old themes, few custom widgets | New accessible theme fixes many template issues at once | Pages need re-checking after the switch | Good middle path |
| Overlay plugin only | Nothing on its own | Fast to install | Does not fix the underlying code | Not a compliance strategy |
The deciding number is simple: take the audit’s issue list and mark each issue as template or content. If most are template issues on a theme you can edit, fix them. If most are template issues inside a page builder, compare the fix estimate with a rebuild estimate before committing to either. If most are content issues, the work is mainly editorial, and training your editors is part of the fix rather than an extra.
When is fixing the existing site the wrong approach?
Fixing is usually right. It stops being right in three situations.
When most issues live in builder-generated templates. If every menu, tab set and slider comes from a page builder that outputs inaccessible markup, each fix is a workaround layered on generated code, and the next builder update can undo it. Rebuilding those templates cleanly costs about the same and removes the class of problem. Our guide to leaving Elementor without losing your design covers that route.
When the site already needs a rebuild for other reasons. Speed, security and maintenance trouble on an ageing install make accessibility the third reason for the same project, and building accessibly from the start is far cheaper than retrofitting. A rebuild is the cheapest moment to meet WCAG, and we treat it as a requirement on every WPBuildAI build rather than an add-on.
When nobody can safely change the theme. If the original developer is gone and every edit risks breaking the site, the accessibility project turns into a recovery project first. What to do if your developer disappears covers getting control back.
How do you keep a site accessible after the fixes?
Most of the drift comes from new content, so most of the prevention is editorial.
Give editors a one-page guide: write alt text that says what the image shows and why it matters, use real heading levels rather than bold text, write link text that makes sense out of context, and never put important information only inside an image. Run an automated checker on new pages before publishing. Schedule a manual keyboard and screen reader pass on key flows twice a year, and after any redesign or new plugin. If you publish PDFs, make an accessible HTML version the default.
This ongoing work is small when the templates are sound, which is the strongest argument for fixing templates properly rather than patching pages. The broader maintenance picture is in what a WordPress site really costs per year.
Key takeaways: the cost of making a WordPress site ADA compliant
There is no detailed federal web standard for private businesses, but WCAG 2.1 or 2.2 level AA is the practical target, the DOJ requires 2.1 AA from state and local governments by 2027 or 2028, and the European Accessibility Act has covered e-commerce since June 2025. The cost depends on where the problems live: theme-level fixes are cheap and site-wide, content fixes scale with images and documents, and builder-generated widgets are the expensive part. Audit before pricing, fix templates before pages, skip overlays that promise instant compliance, and build editor habits so the site stays fixed. When most problems sit in page-builder output, rebuilding accessibly is often the same price as patching, which is the comparison WPBuildAI runs for clients before quoting either.
Common questions about this move
How much does it cost to make a WordPress site ADA compliant?
It depends far more on the theme and page builder than on page count. A small site on a clean, accessible theme often needs only fixes to contrast, alt text, form labels and headings. A site built with a heavy page builder may need its templates rebuilt, which is the same work as a redesign. WPBuildAI scopes it from an audit first, because quoting before testing is guessing.
Is there a legal standard for ADA website compliance for businesses?
For private businesses, the Department of Justice says the ADA applies to goods and services offered on the web, but it has no regulation with detailed technical standards for them, and points to WCAG and Section 508 as helpful guidance. WCAG 2.1 or 2.2 at level AA is the practical target. State and local governments have a formal rule requiring WCAG 2.1 AA, with deadlines in 2027 and 2028.
Will an accessibility overlay plugin make my site compliant?
No overlay can fix the underlying code on its own. Missing labels, unclear link text, broken heading order and inaccessible custom widgets have to be fixed in the theme and content. The FTC ordered one overlay vendor to pay one million dollars in 2025 over claims that its tool could make any site compliant. Treat overlays as, at most, a supplement to real fixes.
Is it cheaper to fix my WordPress site or rebuild it accessibly?
If the theme is clean and the problems are content level, fixing is cheaper. If a page builder generates deeply nested markup, custom sliders, tabs and menus without keyboard support, every fix fights the builder, and rebuilding the templates often costs about the same while also fixing speed. The audit answers this: count how many issues live in templates versus in individual pages.
Do I need ongoing accessibility work after the fixes?
Yes, but not much if the templates are sound. Every new page, image and form can reintroduce problems, so the ongoing cost is training editors to write alt text and use real headings, plus an automated check on new content and a manual review a couple of times a year. Without that habit, a site fixed once usually drifts back within a year.
