I’ve sat in this meeting more times than I can count. A product manager pulls up an audit report full of red flags. An engineering lead asks how many sprints it will eat. Someone from legal wants a date they can put in writing. Everyone in the room agrees accessibility matters, but no one agrees on whether to build internal capability or hire third-party accessibility remediation services.
That question sits at the center of this guide. Should you build accessibility remediation capability inside your own team, or should you bring in accessibility remediation services from a specialized agency? It’s one of the most consequential calls a product or engineering leader will make this year. Get it right and you fix real barriers for real users while keeping your roadmap intact. Get it wrong and you burn out your best engineers on work they weren’t hired to do. Or you write a check to a vendor who hands back a PDF and disappears.
I’ve advised teams on both sides of this decision for close to a decade. I’ve worked inside scrappy startups and inside organizations with compliance departments the size of a small startup. There is no universal answer. But there is a way to think through it that removes most of the guesswork, and that’s what I want to walk you through here.
What Accessibility Remediation Actually Requires
Before you can decide between an internal team and accessibility remediation services, it helps to be honest about what the work actually is.
Remediation is not the same thing as an audit. An audit tells you what’s broken. Remediation is the process of actually fixing it. That means rewriting markup so screen readers announce form fields correctly. It means adjusting color values so text meets contrast thresholds, and rebuilding a custom dropdown so it behaves like a real one for someone navigating by keyboard. Then comes retesting every single fix against assistive technology, to confirm the fix didn’t quietly introduce a new problem.
The work touches design, front end code, sometimes back end logic, content, and QA all at once. A single flagged issue, “button has no accessible name,” can trace back to a design system component used on 40 different pages. Fixing it properly means fixing the component, not just the instance someone happened to flag.
Teams who’ve only ever run an automated scan tend to underestimate this work badly. The scan finds the symptom. Curing it requires someone who understands WCAG success criteria deeply enough to know why a fix works, not just that a rule passed.
Why This Decision Carries More Weight Than It Used To
The pressure behind this decision has changed in the last few years, and it’s worth naming plainly.
Start with the WebAIM Million report, which evaluates the home pages of the one million most visited websites. It found that 95.9 percent of those pages had detectable WCAG 2 conformance failures. The average home page carried 56 distinct accessibility errors. Six categories accounted for 96 percent of everything the researchers found. Low contrast text, missing alt text, missing form labels, empty links, empty buttons, and missing document language topped that list. These aren’t obscure edge cases. They’re the basics, and most sites still get them wrong.
Legal exposure keeps climbing too, rather than leveling off. Website accessibility lawsuits under the ADA hit 1,037 in the first quarter of 2026 alone. That’s a year over year increase from the 983 filed during the same period the year before. The shape of the litigation has shifted as well. A small group of roughly 27 plaintiffs filed more than half of all cases. Just 10 law firms accounted for over 82 percent of filings. This isn’t scattered opportunism anymore. It’s an organized, repeat driven pattern. It increasingly targets sites that already installed an accessibility widget and assumed that settled the matter.
Layer in the European Accessibility Act deadlines, state level procurement requirements, and enterprise customers who now ask for a VPAT before signing a contract. You can see why “get to compliance” stopped being a nice to have. It became a business requirement with a calendar attached to it.
None of that tells you whether to fix things yourself or bring in accessibility remediation services. But it explains why the choice deserves more rigor than a quick gut call in a planning meeting.
The Real Cost of Keeping It In-House
Every engineering lead’s first instinct is to keep the work internal. Your team already knows the codebase. Why pay someone else to learn it?
That instinct is reasonable, and sometimes it’s right. But the math is more complicated than most teams expect.
The Learning Curve Nobody Budgets For
Most computer science programs and coding bootcamps don’t teach accessibility. A developer who has never specialized in it needs real time just to learn WCAG success criteria. They also need to understand how assistive technology actually interprets markup. And they need the judgment to know when an automated tool is simply wrong, which happens more often than people assume. One well known cost analysis in this space put it simply. A developer who specializes in accessible development is often roughly twice as efficient at remediation as a generalist encountering these problems for the first time.
That efficiency gap compounds fast. A generalist team doesn’t just take longer. They also make more mistakes along the way. That means more rework, more retesting cycles, and work that started out as a side project quietly chewing through your roadmap.
The Opportunity Cost Nobody Writes Down
There’s also a cost that rarely makes it into the spreadsheet. Every hour your senior front end engineer spends untangling a custom combobox for screen reader compatibility is an hour they aren’t spending on this quarter’s feature commitments. Weigh that engineer’s time honestly. Say it’s worth more building revenue generating features than fixing accessibility defects at a slower, first attempt pace. Then outsourcing that specific work usually wins on pure economics. The vendor’s hourly rate looks higher on paper, but the comparison changes once you count what your own team gives up.
None of this means in-house is the wrong choice. It means the true cost of in-house remediation runs higher than the number people usually write down. It deserves an honest calculation before you commit a team to it.
A Real Example
A mid sized SaaS company I worked with a couple of years back assigned accessibility remediation to two front end engineers. It was a part time project alongside their normal sprint work. Eight months later, they had made real progress. But the project had quietly eaten nearly triple the hours they’d originally budgeted, and three other features slipped a full quarter behind schedule. The company wasn’t wrong to try it in-house. They just hadn’t priced in how much a first attempt at unfamiliar, detail heavy work actually costs. That cost climbs fast when a team squeezes the work between other priorities instead of treating it as focused, specialized effort.
What a Specialized Accessibility Remediation Agency Actually Brings You
The case for accessibility remediation services isn’t just “someone else does the work.” A good agency brings three things. Each one is genuinely hard to build quickly in-house.
The first is pattern recognition. A specialist who has remediated hundreds of data tables, modals, and multi-step forms recognizes your specific problem within minutes. They’ve already solved variations of it before. Your internal team is solving it for the first time.
The second is testing depth that goes past automated scanning. Automated tools reliably catch somewhere around 30 to 40 percent of WCAG issues. Everything else requires manual testing with real assistive technology, by someone trained to use it the way an actual user would. Think keyboard trap behavior, focus order logic, and whether a screen reader actually announces an error message at the right moment. Agencies that specialize in this typically maintain that testing bench as a core capability, not a stretch assignment for whoever happens to be free.
The third is defensibility. Say your organization ever needs to demonstrate a good faith effort toward compliance, to a court, an auditor, or an enterprise customer’s procurement team. Documented remediation work from a specialized provider carries more weight than an internal team’s self assessment. That’s not a knock on your engineers. It’s just how third party validation works in any compliance context.
The tradeoff is real too. You pay a premium for that expertise, and you depend on an outside team’s availability and communication style. Pick a low quality vendor, one that just runs automated scans and calls it remediation. You can end up with a false sense of security that’s arguably worse than knowing you still have work left to do.
9 Questions to Ask Before You Decide
I use a version of this list with nearly every client I work with. It forces the conversation past vague preferences and into specifics that actually predict outcomes.
1. How large and how dynamic is the surface you need to fix?
A five page marketing site is a different project than a web application with a component library and weekly releases. The second scenario usually benefits from building at least some internal capability, because the work never really ends.
2. Do you have anyone on staff today who can evaluate WCAG conformance without guessing?
If the honest answer is no, that gap alone often tips the decision toward outside expertise, at least for the first remediation pass.
3. What’s your actual timeline, and is it driven by a legal demand letter?
A demand letter or settlement agreement usually comes with a fixed deadline. That kind of deadline leaves no room for a multi month learning curve.
4. What’s the opportunity cost of pulling your best engineers off feature work?
Put a real number on it. Compare that number honestly to a vendor’s quote before assuming internal is cheaper.
5. How will you handle new features once you finish the initial remediation?
Fixing what exists today doesn’t help if next quarter’s redesign reintroduces the same problems. Someone needs ongoing ownership, whether that’s internal or contracted.
6. Does your design system encode accessible patterns, or does every team reinvent components from scratch?
A mature design system dramatically cuts remediation cost regardless of who does it, because fixing the component fixes every instance at once.
7. What level of assistive technology testing does the work actually require?
Confirm whether a prospective vendor tests with real screen readers and real users. Some vendors lean mainly on automated scanning and dress it up as a full service offering.
8. Who takes responsibility if the team misses something?
Get clarity, in writing, on whether a vendor stands behind their remediation work with retesting and support. Or does the relationship end the moment they hand over the report?
9. What happens to institutional knowledge when the engagement ends?
The best agencies transfer knowledge back to your team through documentation, training, or pairing sessions. Your organization should come out stronger than it went in, not permanently dependent on the vendor for every future fix.
Walk through these 9 questions with your team, honestly and specifically, and the right path usually becomes obvious. Most teams already know the answer once they see it on paper. They just hadn’t asked the questions out loud.
The Hybrid Model, and Why It’s Becoming the Default
In practice, the choice isn’t purely binary. The most mature organizations I work with rarely pick one lane and stay there forever.
A common and effective pattern looks like this. Bring in accessibility remediation services for the initial heavy lift, clearing the backlog of existing issues across a live product. At the same time, train a small internal team to handle new development going forward. The agency clears the debt. Your team learns to stop creating new debt.
Another version puts a design system at the center. The agency remediates and documents the core components once. Your internal engineers then apply those patterns across new features without needing deep WCAG expertise for every implementation. The hard thinking already happened at the component level.
A third pattern suits organizations under active legal pressure. It pairs an outside firm for compliance critical, court facing work with an internal team handling lower risk, lower visibility areas on their own timeline.
None of these are compromises. They’re often the most cost effective path available. They put expensive specialist time where it has the highest leverage, and let internal teams handle the parts that play to their strengths.
A Practical Framework for Making the Call
If you want a simple way to frame this for leadership, here’s the version I actually use in client conversations.
Pick in-house first when your team already has real accessibility expertise, or has time to build it. This path works best when the surface area is small enough to master, and there’s no looming legal or contractual deadline forcing your hand.
Bring in outsourced accessibility remediation services when you’re facing a deadline you can’t afford to miss, or the technical surface area is large or legacy heavy. The same holds when your team has zero existing accessibility depth, or you need documented, defensible remediation work for legal or procurement reasons.
Lean toward a hybrid path when you need to clear a backlog quickly while building durable internal capability for everything that comes after. Most growing product organizations eventually land here.
Whatever you choose, put an owner’s name on the decision. Diffuse ownership is how accessibility work quietly stalls, regardless of whether the people doing it sit inside or outside your company.
Red Flags When Evaluating an Outside Provider
If you do go the agency route, a few warning signs are worth watching for. The market has plenty of vendors selling a quick badge or overlay widget rather than real remediation.
Watch for any provider who promises full compliance from a script they install on your site, with no code level changes involved. Watch for a report that lists issues without prioritizing them, since not every error carries equal legal or usability risk. And stay skeptical of a vendor who can’t clearly explain how they test with actual assistive technology, not just automated tooling. That gap is exactly where the real defects hide.
A good provider walks you through their methodology without hesitation. They prioritize fixes by user impact and legal exposure, and they leave your team more capable than they found it.
Ask for references from clients running a similar technical stack to yours, and actually call them. A provider who has remediated a dozen static marketing sites may not have the depth for a complex single page application. Custom component frameworks demand a different skill set. The work looks similar from the outside. It rarely is.
Where This Leaves You
There’s no version of this decision that’s free of tradeoffs, and anyone who tells you otherwise is selling something. After years of watching this play out across very different organizations, here’s what I can tell you. The teams who struggle most are the ones who never actually run the comparison. They default to whatever’s familiar: in-house because that’s how the team always works, or outsourced because someone saw a vendor demo. Either way, they skip weighing cost, timeline, expertise gap, and long term ownership before choosing between internal work and accessibility remediation services.
Run the 9 questions above with your actual team and actual numbers. The right model for your organization will look obvious once you do.
Frequently Asked Questions
What is the difference between an accessibility audit and accessibility remediation?
An audit identifies and documents accessibility barriers against a standard like WCAG. Remediation is the separate, follow-on work of actually fixing those barriers in code, design, and content. Many vendors offer one without the other, so it’s worth confirming which service you’re actually buying, especially when you’re comparing quotes from several accessibility remediation services. Section508.gov has a useful overview of remediation planning.
How much do professional accessibility remediation services typically cost?
Cost depends heavily on the size of the site or application, how many issues turn up, and whether the package includes ongoing monitoring. Rather than quoting a flat number, most reputable providers price based on scope after an initial audit. TestParty’s cost analysis breaks down how in-house and vendor costs compare.
Can automated tools alone achieve WCAG compliance?
No. Automated scanning tools typically catch a meaningful but limited share of WCAG issues, which experts generally put around 30 to 40 percent. Manual testing with assistive technology remains necessary to catch the rest. That includes keyboard navigation, focus order, and screen reader announcement issues. The WebAIM Million report documents how widespread these gaps remain even on major websites.
Does having an accessibility widget on our site protect us from lawsuits?
Not reliably. Recent litigation data shows a rising number of ADA lawsuits targeting sites that had already installed an accessibility widget. That pattern suggests widgets alone don’t resolve underlying code level barriers. EcomBack’s Q1 2026 lawsuit report covers this trend in detail.
How long does a typical remediation project take?
Timelines vary widely based on site size and issue volume. A focused initial remediation for a mid sized site commonly runs anywhere from six to sixteen weeks. Ongoing maintenance continues after that, as new content and features ship.
Should a small business build an in-house accessibility capability or outsource it?
For most small teams without existing accessibility expertise, an initial outsourced engagement to clear existing issues tends to work best. Pair it with lightweight internal training for future development. That combination usually beats building a specialist role from scratch on cost alone. AudioEye’s comparison of remediation services versus DIY approaches walks through this tradeoff in more depth.
What should an accessibility remediation quote include?
A trustworthy quote should specify which pages, templates, or components fall in scope. It should also state whether the work includes manual assistive technology testing alongside automated scanning. It should spell out how the team will prioritize issues, and what retesting or support follows after they deliver fixes. If a quote leaves those questions unanswered, ask before you sign rather than after.
References
WebAIM. “The WebAIM Million: The 2026 Report on the Accessibility of the Top 1,000,000 Home Pages.” https://webaim.org/projects/million/
AudioEye. “Accessibility Remediation Services vs. DIY Accessibility: Which Is Best for Your Business?” https://www.audioeye.com/post/accessibility-remediation-services-vs-diy/
TestParty. “Accessibility Remediation Cost Analysis: In-House vs Vendor Solutions.” https://testparty.ai/blog/remediation-cost-analysis
EcomBack. “Q1 2026 ADA Lawsuit Report.” https://www.ecomback.com/ada-website-lawsuits-recap-report/q1-2026
Groves, Karl. “The Financial Argument for Using an Outside Firm for Accessibility Remediation.” https://karlgroves.com/the-financial-argument-for-using-an-outside-firm-for-accessibility-remediation/
Section508.gov. “Remediation and Accommodation Planning.” https://www.section508.gov/manage/remediation-alternative-means-planning/
ADA Title III. “Federal Court Website Accessibility Lawsuit Filings Bounce Back in 2025.” https://www.adatitleiii.com/2026/03/federal-court-website-accessibility-lawsuit-filings-bounce-back-in-2025/