An accessibility report is not the same thing as an accessible website. If your business has been told its website needs fixing, the next purchase should be a scoped remediation project with testable outcomes, not a promise that one widget or score makes the whole site compliant.
For a small service-business website, I would start with the forms, navigation and booking or enquiry journey. A complicated checkout, membership portal or custom interface needs a wider engineering and testing scope. Sometimes a few shared components can be repaired; sometimes an inaccessible theme or third-party booking tool makes replacement more sensible.
How much should you budget for accessibility remediation?
These are illustrative US-dollar planning allowances for professional engineering and verification, not surveyed market averages, fixed Elvis Onunwa prices or guarantees of legal compliance. Your actual quote depends on the audit findings, access to source code and how many distinct customer journeys must be tested.
| Scope | Initial planning allowance | Typical purchase |
|---|---|---|
| Focused fixes on an otherwise sound small site | $1,000–$3,000 | Correct a limited set of confirmed issues in shared navigation, forms or templates; retest the affected journeys |
| Broader small-business remediation | $3,000–$10,000 | Repair several templates, keyboard behavior, forms and content issues, with manual verification |
| Ecommerce, booking or interactive web application | $10,000–$30,000+ | Repair complex states, third-party integrations, checkout or account journeys and run regression tests |
| Formal independent conformance assessment or legal response | Separately quoted | Specialist evaluation, reporting and any legal advice required |
A small number of simple content fixes may cost less. A large document library, bespoke application or inaccessible third-party platform can cost substantially more. An audit, code remediation, independent retesting and ongoing monitoring are separate purchases unless your contract explicitly bundles them.
If you are still identifying the problems, begin with my small-business accessibility audit guide. This page addresses what to commission after you know the barriers.
Why the number of pages is a poor way to price the job
Imagine a 60-page consultancy website built from four shared templates. If the same menu traps keyboard users on every page, one carefully implemented component fix may solve the recurring defect.
Now imagine a ten-page booking website with a custom calendar, pop-up account dialog and embedded payment flow. Each interactive state may need its own investigation, correction and retest. Ten pages could be the harder project.
I would scope work by unique templates, interactive components, content backlog and critical journeys, not by page count alone.
The W3C explains why automated tools cannot evaluate every accessibility issue: some checks require human judgment. The 2026 WebAIM Million study also documents widespread machine-detectable barriers on homepages, but a scan cannot tell you whether a real customer can complete your checkout or enquiry.
What should be included in a remediation quotation?
Ask the developer or accessibility specialist to show you the findings they will address and the evidence they will produce afterwards.
| Deliverable | What to ask for |
|---|---|
| Baseline findings | Affected URLs or components, reproducible steps, severity and relevant WCAG criteria |
| Repair scope | Which templates, controls, forms, media and third-party tools will change |
| Acceptance tests | Keyboard, focus, zoom, screen-reader and form-error checks on named user journeys |
| Regression checks | Evidence that fixing one component did not break mobile navigation, bookings or checkout |
| Ownership and handover | Source changes in your repository, documented limitations and a maintenance plan |
| Independent review, if required | Who performs it, their qualifications and whether it is included in the fee |
Be wary of a proposal that lists hundreds of scanner errors but does not say who will fix them, which journeys are affected or how success will be verified.
Fix the existing site or rebuild it?
Repair when the site has a maintainable codebase, usable content structure and a limited set of defects. For example, replacing a keyboard-inaccessible menu and improving form labels and errors may be enough without touching the rest of the website.
Replace a component or third-party service when the problem is concentrated in a booking widget, calendar or theme module that you cannot meaningfully change. Check the replacement’s accessibility before purchasing it; a new vendor logo is not evidence.
Consider a controlled rebuild when accessibility problems are built into many repeated components, the theme is abandoned, you lack the source code or the website also needs substantial functional changes. Preserve URLs, content, analytics and working enquiry flows during any rebuild. My website redesign versus rebuild guide explains that broader decision.
Do not rebuild merely because an automated report has a high error count. Equally, do not keep patching a fundamentally unmaintainable interface because the first repair quote looks cheaper.
A practical example: a clinic enquiry form
Suppose a clinic’s site looks polished on mobile, but its appointment request form has unlabeled fields, unclear validation errors and a calendar that cannot be operated using a keyboard.
I would not begin by redesigning the homepage. I would reproduce the failed journey, identify whether the calendar is owned code or an external embed, and specify what must work after the fix:
- A visitor can reach and operate every required control using a keyboard.
- Labels and instructions identify what information each field needs.
- An invalid submission explains the problem and allows correction without losing all entered data.
- The calendar and confirmation states remain understandable to assistive-technology users.
- The form delivers the enquiry reliably and the clinic can respond.
- The same journey is retested on narrow screens and after deployment.
This is why accessibility remediation is also a product and conversion problem: a form that excludes some customers or loses enquiries is not doing its job. It does not follow that every accessibility repair will measurably increase sales; measure outcomes rather than promise them.
For form-specific delivery issues, see why contact forms say sent but email never arrives.
What about ADA or WCAG compliance claims?
WCAG is a technical standard, not a certification badge that any developer can grant by installing a script. The W3C’s accessibility planning guidance recommends assigning responsibilities, prioritizing issues and monitoring the website as it changes.
For US businesses open to the public, the Department of Justice’s web accessibility guidance describes accessibility obligations under ADA Title III. It does not impose one universal private-business WCAG deadline identical to the separate government rule. Laws and requirements differ across countries and contexts.
I can discuss website engineering, repair scope and testing. A formal conformance assessment, legal interpretation or response to a demand letter may require an independent accessibility specialist and qualified lawyer. Do not treat an engineering quotation as legal clearance.
How to compare two quotes without buying the same problem twice
Give both suppliers the same information: website URL, platform, audit findings, critical journeys, known third-party services, access constraints and the expected handover. Ask them to separate diagnosis, remediation, testing, specialist review and maintenance.
A cheap quote that fixes only visible color contrast while leaving the booking flow inaccessible is not comparable with one that tests the whole customer journey. A costly quote to replace the entire site should explain why targeted fixes cannot deliver a maintainable result.
Keep the domain, hosting, repository and analytics under accounts your business controls. For a broader ownership checklist, read who should own your domain, hosting and website code.
What should you do next?
If you already have an audit, start with the barriers that prevent customers from completing important actions, then decide whether a focused repair, component replacement or controlled rebuild is justified.
If you need help scoping the engineering work, contact me with your website URL, platform, the key customer journey and a summary of the findings (please remove personal customer information). I can help evaluate the website-side work, explain what should be tested and identify when an independent accessibility specialist is needed. You can also review my web design services if the right solution is a broader website improvement.
