A WordPress accessibility audit runs $1,500 to $4,000 for a small business site, and the remediation work that follows runs $2,000 to $8,000 depending on how much is broken. Ongoing monitoring adds $200 to $800 a month. Those are the numbers. Everything below explains what you get for them, who sells the work, and how to tell a real remediation engagement from an overlay subscription wearing the word “compliance” on its landing page.
The reason this page exists at all: most searches for WordPress accessibility help land on plugin roundups, and a plugin cannot fix a WordPress site. It can scan it. It can add a widget. It cannot rewrite your theme’s navigation to work with a keyboard, and it cannot add alt text to the 4,000 images in your media library. Knowing which problem you have is the whole decision, so start there.
Plugin, Scanner, or Remediation: Three Different Purchases
These get sold as if they’re the same thing. They are not, and confusing them is the most expensive mistake in this category.
A scanner finds problems. Equalize Digital Accessibility Checker, WAVE, axe, and Lighthouse all do this. They read your rendered HTML and report violations they can detect programmatically. That is roughly 30% of accessibility failures. The other 70% need a person: whether your alt text describes the image, whether focus order makes sense, whether your form errors are understandable to a screen reader user. Scanners are cheap, useful, and necessary. They are not remediation.
An overlay is a JavaScript widget bolted onto your site that rewrites the page at runtime: it injects alt text, raises contrast, adds keyboard shortcuts, and shows an accessibility toolbar. Vendors price these annually, usually $490 to $4,000 a year per site. The selling point is that you do not touch your code. The problem is that the code is where the failures live, and no runtime layer can restructure a heading hierarchy or replace a div-based dropdown with a real button element. Overlay vendors have been the target of sustained litigation and regulatory criticism for exactly this reason, and the structural problems with overlay widgets deserve their own reading before you buy one.
Remediation is source-level work. Someone edits the theme templates, the block markup, the plugin output, the forms, and the CSS, then re-tests every flow with a keyboard and a screen reader. It is skilled labour. It is the only category that changes what a screen reader actually encounters.
If a vendor cannot tell you which of the three they are selling, that is your answer.

What a WordPress Accessibility Audit Actually Covers
An audit is a measurement, not a fix. A proper one on a WordPress site has five parts.
Automated baseline. Run the whole site, not just the homepage, through an automated engine to catch the machine-detectable failures: missing alt attributes, form fields without labels, contrast ratios under 4.5:1, empty links, duplicate IDs, missing language declarations. On a typical small business WordPress site this surfaces 200 to 900 issues, and it takes an afternoon.
Manual conformance testing against WCAG 2.2 Level AA. WCAG 2.2 contains 87 success criteria in total, 55 of them at Levels A and AA, which are the levels laws and contracts actually point at. The nine criteria new in WCAG 2.2 are the ones most sites have never been tested against. Manual testing walks your key page templates against those criteria by hand, because the pass/fail judgement for most of them requires a human.
Assistive technology passes. Screen reader testing with NVDA on Windows and VoiceOver on macOS and iOS. Keyboard-only navigation with focus visible at all times. Zoom to 200% and 400% to check reflow. Text spacing overrides. These are the tests that find what scanners structurally cannot.
Template inventory. This is the part that makes WordPress audits different from general web audits, and the part most audits get wrong. A WordPress site is not 200 pages. It is maybe 12 templates: homepage, blog index, single post, page, archive, search, 404, WooCommerce product, cart, checkout, account, and whatever your page builder invented. Those templates multiply by content. Testing templates tells you the real cost of remediation, because fixing single.php once fixes every post. An audit that prices per-page is either padding the bill or does not understand WordPress.
A written report with reproducible evidence. Every finding needs the URL, the WCAG criterion it violates, a screenshot or recording of the failure, the assistive technology used, severity, and the specific fix. A report that says “improve colour contrast site-wide” is not an audit. A report that says “/services/, 1.4.3 Contrast Minimum: footer links #8a8a8a on #111111 measure 3.9:1, need 4.5:1, change to #9a9a9a or darken the background” is.
Ask for two sample findings before you sign. Any auditor who will not show you what their report looks like is selling a PDF with your logo on it.

What It Costs
Pricing in this market is not standardised, which is why the ranges are wide. What follows is what accessibility engagements typically transact at for small and mid-market WordPress sites in the US. Treat the ranges as bands, not quotes: the floor moves with the market, the spread between them does not.
Audit only: $1,500 to $4,000. A 10 to 50 page WordPress site sits at the bottom; 100 pages across WooCommerce templates at the top. You are buying 8 to 25 hours of skilled manual testing. Anything quoted under $800 is automated scanning with a human signature on it.
Audit plus remediation: $4,000 to $12,000 combined. The remediation half depends almost entirely on template count and how much custom code your theme carries. A clean block-theme site with 12 templates and no page builder is a two-week job. A site built on a heavily customised commercial theme with a page builder layered on top is a six-week job, because every fix has to fight whatever the builder renders.
Remediation only, from an existing audit: $2,000 to $8,000. Cheaper per unit of work than buying the audit bundled, but only as good as the audit you are handing over. If the audit is a scanner export, expect the developer to re-test everything and price accordingly.
Ongoing monitoring and support: $200 to $800 a month. Covers re-scanning after content or plugin changes, regression testing when WordPress or a plugin updates, and a monthly report. Sites that publish weekly need this. A five-page brochure site that changes twice a year can buy a re-audit every 18 months instead.
Accessibility conformance report (ACR/VPAT): $2,500 to $10,000. Only relevant if you sell to government, education, or enterprise procurement, where an ACR is a bid requirement rather than a legal defence. Do not buy one because a blog post told you it protects you.
Three things drive cost more than page count: number of distinct templates, presence of a page builder, and how much of your content is authored rather than generated. A site with 300 PDFs is a document remediation project wearing a website costume, and sending those to a dedicated provider like RemediatePDF is usually cheaper than having web developers remediate them by hand.
Who Actually Does the Work
There are three provider types and they are not interchangeable.
Specialist accessibility consultancies. They do only this. Expect a formal audit methodology, testing against WCAG 2.2 AA by hand, named assistive technology coverage, and remediation delivered either by their own developers or through a developer they work with. Most expensive, most defensible, and the right choice if you have an active demand letter or a procurement deadline. The trade-off is that many of them do not do WordPress itself. They audit, then hand you a report your developer has to interpret, which is where fixes get lost in translation.
WordPress development agencies with accessibility capability. They audit and then fix, in the same codebase, with people who understand themes, blocks, and plugin output. The quality range here is enormous, and the differentiator is whether the audit is done by someone who tests with a screen reader or someone who runs a scanner and calls it a day. Ask directly.
Freelance developers. $60 to $150 an hour, genuinely variable quality. Can be excellent value for pure remediation from an existing audit. Can also produce a site that passes automated checks and remains unusable, because passing axe is not the same as being accessible.
What you should not buy: an overlay subscription marketed as ADA compliance. It is the cheapest option on the page and it is the one that most reliably ends in a lawsuit, because the widget changes nothing about the underlying code.

How to Vet a Provider in Fifteen Minutes
Five questions. The answers separate the field fast.
“What assistive technology will you test with, and who on your team runs it?” The correct answer names NVDA, JAWS, VoiceOver, TalkBack, and a keyboard. If the answer is only a tool name, you are talking to a scanner reseller.
“How many templates does my site have, and how did you count?” A real WordPress auditor will answer in templates and explain how they identified them. A per-page quote at this stage means they have not looked.
“Show me a redacted finding from a previous report.” This is the single most predictive question. Good reports are specific, cite criteria, and include evidence. Bad ones are category headings.
“Will you re-test after remediation, and is that included?” Remediation without verification is unfinished work. Re-testing should be a line item, not an afterthought.
“What happens when WordPress updates and something regresses?” There is no permanent pass. Accessibility is maintained, not achieved. A provider with no answer to this is selling you a one-time event.
Red flags: a guarantee of “full ADA compliance” (no one can offer that, since the law has no technical standard and the guidelines have no finish line), pricing quoted per page without a template count, a report promised in under 48 hours for a site over 50 pages, and any proposal where the word “overlay” appears without the word “no.”

The Remediation Work, In the Order It Actually Happens
This sequence is specific to WordPress because the failure modes are.
1. Theme templates and navigation. Fix the structural layer first: landmark regions, heading order, skip links, the primary navigation’s keyboard behaviour and focus management, mobile menu focus trapping. Everything downstream inherits these fixes, which is why this comes first and why doing it last doubles the work.
2. Block and page-builder output. Gutenberg blocks, and especially third-party page builders, emit markup you did not write. Audit what each block actually renders and either fix it with block styles and filters or replace the offending blocks. This is usually the largest single chunk of remediation time on a modern WordPress site, and the part that estimates most often miss.
3. Forms. The highest-risk component on any business site and the most common subject of complaints. Labels tied to inputs, error messages announced and programmatically associated, no reliance on colour alone, logical focus order, and success confirmation that a screen reader announces. Our guide to accessible form error messaging covers the patterns in depth.
4. Content. Alt text that describes rather than repeats, link text that makes sense out of context, heading structure in the editor rather than bold text that looks like a heading, tables with real header cells, and transcripts for audio and captions for video. This is the part that never finishes, because new content arrives every week.
5. Interactive components. Accordions, tabs, carousels, modals, mega menus, date pickers. Each needs correct roles, states, and keyboard behaviour. Third-party plugins are frequently the culprit here, and the honest answer is sometimes “replace this plugin” rather than “patch its output.” Our guide to accessible modal dialog patterns covers the single most common failure in this group.
6. PDFs and documents. Separate workstream, separate cost. A site with a document library has two remediation projects.
7. Verification. Re-run the automated baseline, re-test manually against WCAG 2.2 AA, repeat the assistive technology passes on the templates you changed, and record what was tested and what passed. Produce the conformance statement or ACR if you need one.
When a Plugin Is Genuinely Enough
Not every site needs a $6,000 engagement, and telling you otherwise would be a sales pitch rather than a guide.
A plugin is sufficient when you need to monitor rather than fix. That covers a clean site that wants a scanner running in the dashboard to catch new violations from content edits, and a maintained site where someone with accessibility knowledge handles the fixes as they appear.
A plugin is not sufficient when the underlying code is broken, when you have received a demand letter, when you are bidding on a public sector contract, or when the previous attempt was an overlay and it did not work.
For the specific comparison of what each WordPress accessibility plugin does, where the free ones stop, and which ones are overlays in disguise, the guide to WordPress accessibility plugins covers them individually. Read that first if you are still deciding whether you need a product or a service. Read this one if you have decided you need the work done.
The Legal Context, Briefly
ADA Title III applies to public accommodations, and the Department of Justice’s web accessibility guidance confirms it reaches goods and services offered online. There is no technical standard written into the statute. Courts and settlement agreements consistently reference WCAG 2.1 or 2.2 Level AA as the benchmark, which is why every audit you buy will be framed against it.
Federal filings have climbed every year for the better part of a decade, and the composition has shifted toward small businesses and toward industries that were not previously targeted. Our ADA website lawsuit trend analysis tracks the pattern by sector and by state.
The practical takeaway: the risk is not evenly distributed. It concentrates on sites with forms, e-commerce checkout, booking flows, and content that a plaintiff firm’s scanner can find from a search engine. If you have any of those, remediation is a business expense before it is a legal one.
What the Engagement Should Look Like
A properly scoped project has five deliverables and a fixed timeline.
- Audit report: findings by template, each with URL, criterion, evidence, severity, and fix. Two to four weeks for a small site.
- Remediation plan: sequenced by impact and dependency, with effort estimates. One week after the report.
- Fixed code: delivered as commits you own, in your repository, not silently applied through a plugin.
- Verification report: what was re-tested, with what, and what passed. Same two to four weeks as remediation.
- Handover: documentation of what was changed and why, plus a content authoring guide so your team does not reintroduce the same failures next Tuesday.
Total elapsed time on a 10 to 50 page business site: six to ten weeks. Anything promising a week is automated scanning plus hope.
Get the timeline in writing with the deliverables, and put a clause in the contract that fixes ship as code you can read. That clause alone filters out most of the market.
If You Are Starting From Zero
The sequence that works, cheapest first:
Run a free scanner now. If the count is under about 50 issues across templates, a plugin and disciplined content authoring may genuinely be the whole answer. If it is in the hundreds, you have a remediation project and no amount of scanning will change that.
Then get one real audit rather than three cheap ones. A single thorough report that your developer can execute against is worth more than three scanner exports and a proposal.
Then fix the templates, not the pages. Then verify. Then monitor, because the site will change and the guidelines will keep moving.
Veduis runs ADA and WCAG compliance engagements built exactly this way: audit, remediation in your codebase, verification, and handover. We also build [compliance tooling] (https://veduis.com/compliance-solutions/) for teams who want to run the ongoing checks themselves.
FAQ
How much does a WordPress accessibility audit cost? $1,500 to $4,000 for a small to mid-size business site. The range is driven by template count, page builder complexity, and whether the audit includes assistive technology testing rather than automated scanning only.
Can a WordPress plugin make my site ADA compliant? No. A plugin can scan for violations and can improve some presentation issues, but it cannot restructure your theme’s markup, fix heading hierarchy, or replace non-semantic components. Compliance claims attached to plugins and overlays should be treated as marketing.
How long does remediation take? Two to six weeks of work for a 10 to 50 page site, spread over six to ten weeks including audit and verification. Sites with heavy page builder customisation or large document libraries take longer.
Is WCAG 2.2 required, or is 2.1 enough? WCAG 2.2 is the current recommendation and is backward compatible, so meeting 2.2 means meeting 2.1. Most legal settlements reference 2.1 AA, but new engagements should target 2.2 AA because the nine criteria WCAG 2.2 introduced address real failures that 2.1 does not test.
Do I need an overlay as well as remediation? No. Remediation addresses the underlying code, which is what assistive technology reads. An overlay on top of a remediated site at best does nothing and at worst interferes with the fixes.
What if I have already been sued? Get a source-level audit immediately, prioritise the specific pages and flows named in the complaint, and have the remediation documented and verified. A settlement generally requires demonstrable remediation, and a report proving it is what you will be asked for.
How often does a WordPress site need re-auditing? Re-test after any theme change, major plugin update, or redesign. Full audits every 12 to 18 months for actively maintained sites, or after any significant content migration. Automated scanning should run continuously.



