ADA Website Compliance Services: What to Buy and Skip

The phrase covers several different things sold under one label. Some vendors test your site and write a report. Some fix the code. Some watch your site over time. Some install a script that changes how pages behave in the browser. And some are law firms. These are not interchangeable, and most businesses need a mix of two or three.

One framing point before the list. The ADA does not define a technical standard for private business websites, and nobody can certify a site as “ADA compliant”. In practice, services measure your site against WCAG 2.2 Level AA. We explain why in ADA compliant website: why no badge or certificate exists and in our piece on the difference between WCAG and the ADA. So when a provider promises “compliance”, read it as “we will test and fix against WCAG”, and be wary if it sounds like more than that.

Here is the realistic menu, with the job each one does and its limit.

• Automated scanning. Software loads your pages and flags issues it can detect by rule, such as missing alt attributes, unlabeled form fields, and low contrast. It is fast and cheap and good for catching regressions. Automation covers roughly 30 to 40 percent of WCAG success criteria, so a clean scan is not a clean bill of health. CompliaScan is in this category: it runs axe-core plus 9 custom checks. Try the free WCAG checker to see what a scan looks like.
• Manual accessibility audit. A specialist tests with a keyboard and screen readers and reviews against each success criterion, then writes up findings. This is where you learn about problems scanners cannot see, like confusing focus order or unhelpful alt text. It is a point-in-time document. Our audit cost breakdown covers typical price ranges.
• Remediation (fixing). Developers or agencies change your templates and content to resolve the findings. This is the work that actually removes barriers. It is often priced hourly or per project, and the scope depends on your platform and how the site was built.
• Ongoing monitoring. Scheduled scans that alert you when something breaks after a redesign, plugin update, or new page. Good for keeping a dated record of effort. It does not replace periodic manual testing. See accessibility monitoring.
• Accessibility overlays. A script added to your site that adds a toolbar or tries to patch issues automatically. Evidence on these is poor and regulators have acted against marketing claims. Read do accessibility overlays work and accessiBe alternatives after the FTC fine before paying for one.
• Legal counsel. A lawyer experienced in accessibility law advises on risk, drafts policies, and handles demand letters or claims. No scanner or agency replaces this, and this article is not legal advice.

The right combination depends on where you are starting from.

• You have never checked your site. Start with a free automated scan to see the shape of the problem, then decide whether a manual audit is worth it. The how to check website accessibility guide walks through a first pass.
• You run a small site on a hosted platform. Many fixes are settings and content changes you can make yourself. Platform guides help: Shopify, WordPress, Wix, Squarespace, and Webflow. A scanner plus a few hours of fixes often covers the first round.
• You have a custom or large site. Budget for a manual audit and developer time for remediation, then add monitoring so fixes do not decay.
• You sell to government or enterprise buyers. You may be asked for a VPAT or Section 508 documentation. That points toward a manual audit by a qualified third party. See Section 508 explained.
• You received a demand letter. Talk to a lawyer first. Then, with their guidance, services for testing and remediation become relevant. Our first 14 days post describes what these letters generally look like.

Whatever you are buying, these questions separate careful providers from sellers of shortcuts.

• Which standard and level do you test against, and which WCAG version? The answer should be WCAG 2.2 Level AA, or 2.1 AA if a specific rule requires it.
• What is not covered? Honest vendors can tell you what their method misses. Anyone claiming full coverage from automation alone is overstating it.
• Do you change my live site automatically? Be careful with anything that rewrites markup without review. You should be able to see and approve every change.
• Who does the testing, and with which assistive technologies? For audits, ask which screen readers and browsers were used and whether you get the evidence, not only a score.
• What do I own when the contract ends? Reports, fix lists, and issue history should be exportable.
• Do you promise compliance, certification, or lawsuit protection? If yes, walk away. No one can promise that, and a statement like that is a marketing claim, not a legal outcome.

Prices vary a lot by provider and site size, so treat these as ballparks and get quotes. Manual audits commonly run from a few thousand dollars for a small site into the tens of thousands for a complex one. Automated scanning subscriptions run from free single-page checks up to a few hundred dollars a month for multi-site tiers. Remediation is the most variable line because it depends on how many issues exist and how your site is built. Our full pricing breakdown has more detail, and you can see what CompliaScan includes on the pricing page.

A common and sensible split for a small business is automated scanning and monitoring as the ongoing baseline, with a manual review of the highest-value flows (checkout, booking, contact) when budget allows.

Some scanners now suggest code fixes with AI. Used well, that speeds up the fixing step, because a developer gets a proposed change instead of a bare error message. The important part is control. In CompliaScan, AI fixes are bring-your-own-key and nothing is applied to your site automatically. You read a suggestion, decide whether it is right, and make the change yourself. Treat any AI fix as a draft to review, since context like the purpose of an image or the intent of a control is something only your team knows.

If you want a sequence that does not require a big contract, this works for most small sites.

• Week 1: scan your key pages and export the results. Note the date.
• Week 2: fix the highest-impact items first. See the most common WCAG failures for what to look for.
• Week 3: test by hand. Tab through the main flows, zoom to 200 percent, and try one flow with a screen reader. The keyboard guide helps.
• Week 4: publish an honest accessibility statement, set up scheduled re-scans, and decide whether a paid manual audit is warranted.

Is there a service that makes my site ADA compliant? No service can guarantee that. Good ones find and help fix barriers against WCAG, and you keep maintaining the site.

Are automated tools enough? They are a solid baseline and catch a real share of issues, but roughly 30 to 40 percent of WCAG criteria are testable by automation, so manual checks are still needed.

Should I hire a lawyer or an accessibility firm? They do different jobs. Accessibility firms test and fix; lawyers advise on legal risk. If you face a claim, a lawyer comes first.

How often should I re-check? Whenever you ship significant changes, and on a schedule in between, since content and plugins change constantly.

Treat ADA website compliance services as tools for different jobs: scanners to find and watch, auditors to go deeper, developers to fix, lawyers to advise. Skip anything promising a certificate or a one-line fix. If you are not sure where to start, scan your site and let the results tell you which service you actually need.