WCAG Remediation: Consultant, Agency, In-House or DIY
There are five ways to buy it, and the right one depends on who will write the fixes. An independent consultant suits a team that can implement its own findings. A specialist consultancy suits real legal exposure. A web agency suits a site that needs rebuilding. In house suits a site that changes weekly. DIY suits a small, simple site — and an overlay widget suits nobody.
This page is about which kind of help to buy. If you are still working out how remediation relates to WCAG, an audit and ongoing monitoring, start with WCAG versus remediation — they are sequential stages, not alternatives.
The five routes, and what each one fails at
Every route here works for somebody. The useful question is not which is best but which fails in a way you can live with, so each entry below names that explicitly.
An independent consultant
One credentialed practitioner who tests your site, writes up what fails against which success criterion, and specifies the fix. Your developers write the code. Many of the most experienced people in this field work this way.
Best when
You have engineering capacity but no accessibility knowledge. This is the cheapest route to genuine expertise, because you are buying judgment rather than hands.
How it is priced
A day rate, or a fixed fee for a defined audit. You are buying a bounded number of days, which makes it the easiest route to budget for.
Where it fails
Getting the work done. A consultant produces findings, and findings do not fix anything. If nobody internally has the time or the mandate to act on the report, you have bought a document. One person also has limits — a solo practitioner cannot cover every combination of screen reader, browser and platform that a team can.
Warning sign: the report arrives, gets circulated, and nothing ships for a quarter. Agree who owns implementation before the engagement starts, not after the findings land.
A specialist accessibility consultancy
A firm whose entire practice is accessibility rather than a service line inside a web shop. Usually several certified practitioners, a real assistive-technology lab, and experience producing conformance documentation that survives scrutiny.
Best when
You are under a demand letter, facing a procurement deadline, or your exposure is large enough that the quality of your evidence matters as much as the quality of your fixes. Also the right call for genuinely complex applications.
How it is priced
The highest of the five, and usually quoted as a project with defined deliverables. The premium buys depth of testing and a defensible paper trail.
Where it fails
Building things. Many specialist consultancies advise and test but do not do production development, so you still need someone to implement. Check this early — discovering it after you have signed leaves you managing two vendors you did not plan for.
Warning sign: a proposal that never names the assistive technologies and versions used for testing. Depth of testing is the thing you are paying extra for, so it should be specified.
A web agency with in-house capability
A design-and-build firm that also remediates. The middle of the market, and by far the widest quality range — some have certified practitioners and a documented testing process, others have added "ADA compliant" to a services page.
Best when
The site needs rebuilding anyway. If the audit finds that the defects are structural — a component library built without keyboard support, a checkout flow that cannot be operated without a mouse — then remediation and redesign are the same project, and splitting them across vendors costs more than it saves.
How it is priced
A fixed project fee, often bundled with design or development work, which makes the accessibility portion hard to isolate. Ask for it to be priced as a line item so you can compare it against the other routes.
Where it fails
Consistency. This is the route where verification matters most, because the range between the best and worst vendor is enormous and the sales language is identical across it. The failure mode is not malice — it is an agency learning on your budget and your legal exposure.
Warning sign: nobody named on the team holds a credential, and manual screen-reader testing is described as something they "always consider" rather than a step with a name and an owner.
You build the capability yourself: send existing developers and content authors to real training, budget for certification, and make conformance somebody's named responsibility rather than everybody's good intention.
Best when
Your site changes constantly. Accessibility is a state a site drifts out of, not a certificate it earns — every CMS edit, plugin update and embedded third-party form is a chance to regress. If you publish daily, no external retainer will keep pace with your own authors, and training them is the only thing that scales.
How it is priced
Salary and training rather than fees, which moves the spend from a project budget to an operating one. Slower to show results and cheaper over years.
Where it fails
Measuring itself. A team cannot credibly audit the site it built — not through dishonesty but through familiarity, because you stop seeing the patterns you authored. Self-attestation is also the weakest form of evidence in a dispute or a procurement. Whatever you build internally, buy the assessment externally.
Warning sign: an internal accessibility programme with no external audit in its annual budget. That is the point at which the programme stops being able to tell you whether it is working.
You learn enough to fix your own site. Legitimately viable for a small brochure site on a mainstream CMS with a well-built theme, where most defects are contrast, alt text, heading order, link text and form labels.
Best when
The site is small, the templates are few, and there is no custom JavaScript. Start with the checklist, fix what you can confirm, and you will close a real share of the defects at no cash cost.
How it is priced
Your time. The honest version of this route includes the hours to learn a screen reader well enough to test with one, which is the part most people skip.
Where it fails
Everything a scanner cannot see. Automated tools catch a minority of WCAG issues; the rest need human judgment. Custom widgets, keyboard focus management, dynamic content announcements and a back catalogue of untagged PDFs are all beyond a checklist. You also end up with no independent evidence, which matters the moment anyone asks you to prove it.
Warning sign: a clean automated scan being treated as conformance. A passing scan means no machine-detectable failures, which is a much smaller claim than it sounds.
The fifth thing most organisations are actually sold, usually as a monthly subscription that promises compliance from a single line of JavaScript. It is not a cheaper version of remediation. It is a different product that leaves the underlying defects in place.
Overlays cannot fix the things that most commonly fail — they cannot restructure headings, cannot make a custom widget keyboard-operable, and cannot tag a PDF. Businesses running them have still received demand letters, because the site underneath still does not work. Vendors on this site are expected to have a documented position against them.
In roughly this order. The first one eliminates more options than the other two combined.
1
Can anyone on your team write the fixes?
If yes, buy judgment and keep the hands in-house — an independent consultant or a specialist audit, then your own developers implementing. This is the highest-value combination available and it is not the most expensive one. If no, you need a route that includes implementation: a web agency, or a consultancy that does development.
2
Is there legal or procurement pressure?
A demand letter, a federal or state contract, or an enterprise procurement changes what you are buying. You now need documentation that holds up to a third party reading it adversarially — a real conformance report, not an assurance. That pushes you toward a specialist consultancy and away from DIY entirely, whatever the site size.
3
How often does the site change?
A site that changes yearly can be remediated as a project and re-tested occasionally. A site that changes weekly will regress faster than any external engagement can catch, and the only durable answer is internal capability plus monitoring. Match the shape of the spend to the shape of the change — a one-off project on a fast-moving site buys a snapshot that expires.
What most organisations should actually buy
Not one of the five, but a combination of three of them: an independent audit, implementation by whoever knows the codebase best, and a re-test by the original auditor to confirm the fixes landed.
It is cheaper than handing the whole engagement to a single specialist firm, it keeps the measurement independent at both ends, and it puts the code changes in the hands of people who already understand the system. The re-test is the part most often cut for budget, and it is the part that establishes whether you got what you paid for — a remediation with no verification step is an invoice with a hopeful narrative attached.
The exception is genuine legal pressure. Under a demand letter or a procurement deadline the quality of your documentation matters as much as the quality of your fixes, and that is worth paying a specialist for.
Why these quotes are so hard to compare
Because the five routes are priced in four different shapes — day rate, fixed project, retainer and salary — and because within any of them the cost is driven by templates, custom components and document count rather than by page count. A vendor quoting before anyone has tested the site is pricing an unknown, which means padding it or under-quoting and change-ordering later.
That is the practical argument for auditing first regardless of which route you pick: it converts an unknown into a defect list that every candidate prices the same way, which is the only basis on which quotes are actually comparable.
A WCAG consultant measures your site against the standard and tells you precisely what fails, mapped to individual success criteria, then specifies how each defect should be fixed. Most consultants advise and test rather than write production code — your developers or your agency implement the fixes. That division is the point: you are buying judgment, which is the scarce thing, rather than hands, which you may already have. Expect a prioritised findings report, not a repaired website, unless implementation is explicitly in scope.
Do I need a WCAG remediation consultant or an agency?
It depends on whether anyone on your team can write the fixes. If you have engineering capacity, a consultant is the cheaper and usually better route — you buy expertise and keep implementation in-house. If you do not, you need a vendor who will do the work, which means an agency or a consultancy that also develops. The second question is whether the defects are structural: if the audit finds a component library or a checkout flow that has to be rebuilt, remediation and redesign are one project and an agency is the more sensible buyer.
How do I find ADA website compliance consultants?
Start with the IAAP member and certificant directories, which are tied to actual certification records and let you verify a credential rather than take it on trust. Peers in your own sector who have already run this procurement are often better signal than any listing. Wherever you find candidates, shortlist on things with a document behind them — named certified staff, a redacted findings report, a conformance report you can read, and a written position on overlay widgets.
Are ADA remediation companies and WCAG consultants different things?
In practice the labels are used interchangeably and tell you very little. What actually differs is the deliverable. Ask one question of any vendor regardless of what they call themselves: does this engagement end with a report, with a fixed site, or with both? A firm selling "remediation" that delivers findings, and a "consultant" who also implements, are both common. The word on the website is marketing; the deliverable in the contract is the thing.
Can my in-house team handle WCAG remediation?
Often yes for the implementation, and this is underrated — your developers already know the codebase, which is real value no vendor can match. What an internal team cannot credibly do is audit its own work, partly through familiarity and partly because self-attestation is the weakest evidence available if anyone disputes it. The practical split is an external audit, internal remediation, and an external re-test to confirm the fixes landed.
How much do WCAG remediation consultants cost?
The routes are priced in different shapes, which is what makes quotes hard to compare: consultants bill day rates or fixed audit fees, agencies quote fixed projects, monitoring is a retainer, and in-house is salary. Within any of them the cost driver is templates, custom components and document count — not page count. Two 500-page sites can differ by an order of magnitude if one is six templates and the other is sixty. Commission the audit first so every quote prices the same defect list.
Should the same vendor audit and remediate?
Where budget allows, separate them. An auditor who is also bidding on the remediation has an incentive to find more of it, and a remediator checking their own work has the opposite incentive. Independence at both ends is the cheapest quality control available in this market. If you can only afford one vendor, the more important one to keep independent is whoever signs off at the end.
Next step
Whichever route you pick, the audit comes first — it is what makes the routes comparable on price. The verification checklist is what turns a shortlist into a decision.
