You asked two or three providers what it would take to fix your site’s accessibility, and the answers did not line up. One sent a figure the next morning. Another sent back a list of questions about your forms, your PDFs and your booking plugin. A third offered a monthly widget subscription. If website accessibility cost seems impossible to compare, that is usually because each of them was pricing a different job.
This post does not give prices. It explains what actually drives the amount of work, so you can describe your site clearly, compare proposals fairly and spot the ones that were written without looking.
Why an honest estimate starts with questions
Accessibility work on an existing site is closer to a building inspection than to buying a product. Until someone has looked at the templates, the plugins and the content, nobody knows whether the main barriers are a few color values in the theme or a checkout that has to be rebuilt.
So a fast, confident number deserves the same suspicion as a contractor who quotes a renovation over the phone. Either it assumes the best case, or it covers something narrower than you think, such as an automated scan and nothing else. The questions a careful provider asks are a good sign, not a delay.
What affects ADA compliance cost the most: templates, not page count
People often describe their site by the number of pages. That number matters much less than the number of distinct layouts.
A WordPress site with two hundred blog posts may use only one post template. Fix the heading structure, the focus styles and the comment form in that template once, and every post benefits. A thirty-page site where each page was hand-built in a page builder with different sections, tabs, accordions and sliders can be far more work, because each page is its own case.
When you describe your site to a provider, list the types of page instead: home, service page, location page, blog post, product page, cart, checkout, contact, booking, account area. That list is the real scope.
How much the theme is working against you
The theme decides a lot before any content is added: how menus open, whether focus is visible, how headings are styled, whether the layout reflows when someone zooms in, what the skip link does.
- A well-built theme with sensible markup leaves mostly content and plugin issues.
- A heavily customized commercial theme may have problems in code you cannot edit directly, so fixes go into a child theme or custom code that has to survive updates.
- Page-builder output varies. Elementor and Divi both have accessibility-related options, but what they produce still needs checking, and some widgets need replacing rather than adjusting.
- An abandoned or very old theme sometimes means the fix list is long enough that a rebuild is the more sensible route.
That last case is worth taking seriously. If the audit shows that the menu, layout, forms and focus handling all need rewriting, our page on accessible website redesign explains how to tell when fixing stops being worth it.
Plugins and third-party pieces
Every plugin that outputs something visitors interact with is a possible source of barriers: sliders, pop-ups, cookie banners, chat buttons, galleries, booking calendars, review widgets, maps, payment fields.
Three questions shape the effort for each one. Can its output be fixed through settings or small code changes? Is there a better-built alternative that does the same job? Or is it a third-party service, often in an iframe, that you cannot change at all and can only pressure the vendor about or replace?
A site with a handful of well-chosen plugins is a lighter job than one with forty, half of them doing one small visual thing each. Running a repeatable plugin audit first often clears away several problems for free, simply by retiring plugins nobody needs.
Forms and anything people have to complete
Forms are where barriers turn into lost customers, and they take more care than static pages. The work includes visible labels, grouped options, instructions, error messages that are announced and described in words, required fields marked properly, and CAPTCHA alternatives.
A single contact form built with a mainstream form plugin is a modest piece of work. A multi-step quote request, a booking flow with a date picker, or a WooCommerce checkout with custom fields and a payment plugin is a much bigger one, because each step and each error state has to be tested with a keyboard and a screen reader.
Documents, video and audio
These are easy to forget when describing a site, and on some sites they take up most of the effort.
- PDFs. How many are linked, and how many are current? A scanned menu or a fillable application form needs real work. Often the best answer is to move the content onto a web page; our post on when a PDF should become a page goes into that choice.
- Video. Each published video needs accurate captions. Auto-generated captions are a start, but someone has to correct names, numbers and technical terms.
- Audio. Podcasts and recorded webinars need transcripts.
An archive of old documents and recordings that nobody uses can sometimes be removed or clearly marked as archived, which shrinks the job considerably. That is a decision to make with whoever advises you on legal duties, not something to do quietly.
Content volume, and who does that part
Years of images without alt text, headings chosen for size and links that say “read more” are not hard to fix one at a time. They are just numerous. The effort here depends on how much content there is and who does it.
Many owners split it: a developer fixes templates, plugins and code, and the in-house team handles alt text and content edits after a short walkthrough of what good looks like. That split is often the biggest lever you have on the overall effort.
Website accessibility cost factors at a glance
| Factor | Lighter job | Heavier job |
|---|---|---|
| Page types | A few shared templates | Many hand-built layouts |
| Theme | Clean, maintained, sensible markup | Old, abandoned or heavily modified |
| Plugins | Few, mainstream, maintained | Many, with sliders, pop-ups and third-party iframes |
| Forms | One contact form | Multi-step booking, quotes or checkout |
| Documents | Few, or already web pages | Many current PDFs, scanned or fillable |
| Media | Little video, already captioned | A video library with no captions or transcripts |
| Content team | Willing to handle alt text and headings | Everything left to the developer |
How to scope your site before asking anyone
You can save everyone time, and get proposals you can actually compare, by preparing a short brief.
- List each page type and give one example URL for each.
- Write down the tasks that matter most: contact, booking, buying, applying, paying, logging in.
- Note the theme, the page builder if any, and the plugins that show anything to visitors.
- Count the current PDFs and videos, and say which are still in use.
- Say whether anyone in-house can edit content.
- Mention any outside requirement, such as a contract that names a WCAG version or a demand letter your lawyer is handling.
- Ask each provider to state exactly what is included: automated scan only, or manual keyboard and screen reader testing too; fixes or just a report; a retest; documentation.
That last point is what makes proposals comparable. The detail of a proper audit, including what it tests and how findings are reported, is on our WCAG audit service page.
Ways to keep the effort down
Most of what lowers website accessibility cost is unglamorous. Fix templates before individual pages. Drop the homepage slider if nobody clicks it. Move current PDFs onto pages. Retire plugins that do little. Train whoever publishes content. And once the site is in good shape, check it a little every month, because regressions caught early are small, while two years of drift is a project.
For the background on why businesses take this on, read ADA compliance for websites explained, which is general information and not legal advice. Audits, forms, media and the rest are mapped on our website accessibility hub, where each service has its own page.
Frequently asked questions
Why do providers give such different estimates for the same site?
Usually because they are describing different work. One may mean an automated scan and a report, another a manual audit with keyboard and screen reader testing, another full fixes with a retest and documentation. Ask each one exactly what is included and which pages and tasks are covered before comparing anything.
Does an automated scan tell me how big the job is?
Only partly. Automated tools catch only part of the problems, and their error counts can mislead, since one template issue may show up hundreds of times. A scan is a useful first look, but the size of the job depends on templates, plugins, forms and documents that a person needs to review.
Is a redesign ever less work than fixing the current site?
Sometimes. If the theme is old or abandoned and the menu, layout, forms and focus handling all need rewriting, building accessibility into a new design can be the more sensible route. If the problems are mostly content, contrast and a few plugins, fixing the existing site is usually the better choice.
Do I have to fix every old blog post and PDF too?
Start with what people use now: key templates, important tasks and current documents. Old content can be scheduled after that, removed if nobody needs it, or clearly marked as archived. How your legal duties treat archived material is a question for a lawyer, so make that decision with their input.
If you would like your site scoped this way, our ADA website compliance services start from the brief above: your page types, your key tasks and the plugins in play. The audit, the repairs and the change log all follow from that scope. Legal advice stays with your lawyer.
Next in this series: Website Accessibility Myths Owners Still Believe
