A manual accessibility audit takes one to two weeks for most small-to-mid-size websites, measured from kickoff to report delivery. Larger sites and complex web apps run two to four weeks. Add one to two days for the proposal up front, and plan on a separate remediation period afterward – typically two to eight weeks depending on how much is broken – followed by a retest that takes a few days. If a vendor promises a complete audit in 24 hours, you’re being sold an automated scan with a cover page.

That’s the answer most buyers are looking for, and the rest of this post breaks down where the time actually goes, what stretches a WCAG audit timeline from two weeks to six, and what to do when a legal deadline means you don’t have two weeks.

The full timeline, stage by stage

An accessibility audit isn’t one block of time. It’s four stages, and buyers who only budget for the middle one get surprised.

Scoping and proposal: 1 to 2 business days. You share your URL and describe the site, the auditor identifies unique templates and flows, and you get a fixed price and a start date. At Labrador Services the proposal lands within two business days of your request. Enterprise firms often take one to two weeks for this stage alone, because discovery calls have to be scheduled before anyone will name a number.

The audit itself: 1 to 2 weeks for most sites. This is the manual testing – a human working through your pages and flows with a keyboard, with screen readers, at 200% zoom, then documenting every failure against a specific WCAG 2.2 success criterion with severity ratings and remediation guidance. We covered what that deliverable looks like in what an accessibility audit actually includes.

Remediation: 1 to 6 weeks, sometimes more. The audit hands your developers a prioritized work order. How long the fixes take depends on your team’s capacity and how deep the problems go. A brochure site with 15 issues might be clean in two weeks; a web app with a custom component library and 60 findings can take a quarter.

Retest: 2 to 5 days. The auditor verifies your fixes with the same assistive technology that found the issues. Ours is included in the audit price. Skip this stage and you have a list of things someone intended to fix, which is not the same as evidence that they’re fixed.

So when someone asks how long the whole process takes, site broken to site verified, the honest answer for a typical small business is six to twelve weeks, and the audit itself is the shortest part.

What actually drives audit turnaround time

The same things that drive audit cost drive the timeline, because both are measures of human hours.

Unique templates and flows, not page count. A 500-page blog on three templates audits faster than a 12-screen app with checkout, account management, and a drag-and-drop interface. Auditors test experiences, not URLs.

Component complexity. A custom date picker has to be tested in every state it can reach – open, closed, focused, errored – with a keyboard and a screen reader. One complicated component can take longer than ten static pages.

Assistive technology coverage. Testing with NVDA alone is faster than testing across JAWS, NVDA, and VoiceOver on desktop and mobile. Broader coverage multiplies hours. Whether you need it depends on your audience and your risk.

How much is broken. Every failure gets reproduced, rated, and written up with a fix. A site with 40 issues takes meaningfully longer to document than a site with 8, even when the testing covers identical ground. Teams that run a free automated scan first and clean up the obvious failures – missing alt text, empty buttons, low-contrast text – shorten their own audit. The scan only catches about a third of WCAG failures, which is why manual testing exists, but that third is fast to fix and slow to document.

Auditor availability. The quoted timeline starts at kickoff, not at signature. Ask every vendor two separate questions: how long the audit takes, and when they can start. A two-week audit that starts in six weeks is an eight-week wait.

Why can’t it be faster?

It’s worth taking the question seriously, because the instinct behind it is reasonable. Automated scanners return results in minutes. If a tool can check your whole site before lunch, why does a human need two weeks?

Because the tool and the human are answering different questions. A scanner checks whether your code matches patterns it can parse – alt attributes present, contrast ratios above threshold, form fields labeled. It cannot tell you whether the alt text describes the image, whether the label makes sense, or whether a screen reader user can actually complete your checkout. Finding that out means a person navigating every flow the way your users do, and there’s no compression algorithm for attention.

The documentation is the other half of the time. A finding that just says “keyboard trap on checkout” starts an argument with your developers. A finding with the failing criterion, reproduction steps, a screen recording, and code-level guidance starts a fix. The second kind takes hours the first kind doesn’t, and it’s the difference between a report that gets acted on and one that sits in a drawer.

When you don’t have two weeks

Legal deadlines change the math. An ADA demand letter usually gives you 10 to 30 days to respond, and your attorney needs a factual read on the claims well before that.

An expedited accessibility audit is a real option, though it means the auditor is reprioritizing their queue rather than skipping steps, so expect a rush premium and say what your deadline is upfront. We can scope and start within days when a client is on a legal clock.

There’s also a faster first move: a single-page audit. Our $495 homepage audit turns around quickly, gives your attorney an early factual read, and the fee is credited in full if you continue to a complete audit. If the letter names specific pages, a scoped audit of those pages does the same job. We wrote a full playbook for responding to an ADA demand letter if that’s what brought you here.

What a deadline doesn’t justify is the 24-hour “compliance” shortcut. A widget installs in an afternoon and fixes nothing underneath, and roughly a quarter of accessibility lawsuits now target sites that were running one when they got sued.

A worked example

Say you run a mid-size e-commerce site: product catalog, search, cart, checkout, customer accounts. You request a quote on a Monday. The proposal arrives Tuesday with a fixed fee and a kickoff the following Monday.

The audit runs two weeks, because checkout and account flows have to be tested end to end with a keyboard and two screen readers. You get the report on a Friday: 34 findings, 6 critical, sequenced into a remediation plan. Your two developers work through the criticals in three weeks and the rest over the next four, alongside their normal sprint work. The retest takes three days and verifies 32 of 34 fixed, with two sent back with notes.

Total elapsed time: about ten weeks from first email to verified fixes. The audit was two of those weeks. Budgeting ten weeks from the start is what keeps this process calm; discovering it in week six is what makes it expensive.

Frequently asked questions

How long does an accessibility audit take for a small website?
One to two weeks from kickoff to report for a typical small-business site, plus a day or two for the proposal up front. A single-page homepage audit turns around in days.

How long does a WCAG audit take for a large site or web app?
Two to four weeks for most large sites and SaaS products with authenticated flows and complex components. Very large engagements with broad assistive technology coverage can run longer, which is one reason to scope by unique templates and flows rather than raw page count.

Can I get an accessibility audit done in a week?
Sometimes. Expedited audits exist for legal deadlines and procurement crunches – expect a rush premium, and mention the deadline when you request a quote. A scoped single-page or few-page audit is the fastest legitimate option. Anything promising full-site results in 24 hours is an automated scan.

How long does accessibility remediation take after an audit?
One to six weeks for most sites, depending on your developers’ capacity and the number of findings. Complex web apps with many critical issues can take a quarter. A good audit report shortens this by sequencing fixes and including code-level guidance.

Does the audit timeline include the retest?
Ask, because it varies by vendor. Ours includes a retest after remediation at no extra cost – it typically takes two to five days and verifies fixes with the same assistive technology that found the issues.

How soon can an audit start after I sign?
That’s a separate question from how long the audit takes, and worth asking every vendor. Queues of two to six weeks are common at larger firms. We typically kick off within days, and faster when a legal deadline is involved.

If you’ve received an ADA website demand letter, here’s what to do: don’t panic, don’t reply to the letter yourself, don’t install an accessibility widget, and don’t delete anything. Preserve a copy of your site as it exists today, get the letter to an attorney with ADA Title III experience, and start an independent accessibility audit so you know whether the claims are real. Most of these letters settle for between $5,000 and $25,000, and how you handle the first two weeks has a lot to do with where in that range you land.

That’s the compressed version, and the rest of this post walks through each step: what the letter actually means, what order to do things in, and the mistakes that make these situations more expensive than they need to be.

One thing up front: I run an accessibility auditing firm, not a law firm. Nothing here is legal advice. It’s the practical playbook we walk clients through when they show up with a letter in hand, and it’s meant to make your first conversation with an actual attorney faster and cheaper.

First, understand what you’re holding

An ADA demand letter is a formal notice, usually from a law firm representing a plaintiff with a disability, alleging that your website violates Title III of the Americans with Disabilities Act. It typically lists specific barriers (missing alt text, keyboard traps, unlabeled form fields), references WCAG as the measuring stick, and demands two things: that you fix the site, and that you pay a settlement to avoid a lawsuit.

You are not alone in receiving one. Plaintiffs filed 3,117 website accessibility lawsuits in federal court in 2025, up 27% from the year before, and lawsuits are the visible tip. Industry estimates put demand letters at roughly 7 to 10 for every suit actually filed – somewhere between 35,000 and 50,000 letters in 2025 alone.

The letters are also concentrated. In the first half of 2025, just 31 plaintiffs accounted for more than half of all filings, and a small group of law firms files the overwhelming majority of cases. This matters for your response, because a serial filer’s economics run on volume: they generally want a fast, predictable settlement, not a court fight.

Knowing that shouldn’t make you dismissive, though. For what it’s worth, I think the volume-filing model is ugly, and I say that as someone who tests websites for a living. But the model only works because most of the sites getting letters genuinely fail WCAG, and ignoring the letter is the single most reliable way to turn an $8,000 problem into a $40,000 one.

The playbook

Step 1: Preserve everything, change nothing (today)

Before you touch your site, capture it. Save the letter and its envelope or email headers. Take full-page screenshots of every page the letter mentions. If you can, archive the pages with the Wayback Machine or a crawl tool.

This feels backwards – your instinct is to start fixing immediately. Your attorney, though, will need an accurate record of what the plaintiff actually encountered. If the letter’s claims don’t match your site (they tested an old version, or relied on a bad automated scan), that mismatch is negotiating leverage, and you can only prove it with evidence from before you changed anything.

The fixes can start next week. The record of what your site looked like before them can only be made today.

Step 2: Do not respond to the letter yourself (this week)

Anything you write to the plaintiff’s firm can be used in the negotiation or in court. Business owners who fire off an indignant reply, or an apologetic one promising fixes by Friday, hand the other side ammunition either way.

The same goes for silence, though. Most letters include a response deadline, often 10 to 30 days. Missing it doesn’t automatically trigger a lawsuit, but it tells a volume-based firm that suing you is the faster path to getting paid.

Step 3: Get an attorney with ADA Title III experience (this week)

Not your cousin who does real estate closings. ADA website defense is a niche, and lawyers who work in it know the specific plaintiff firms, their settlement patterns, and which arguments actually move numbers. Your attorney can pull the plaintiff’s filing history on PACER in minutes; a plaintiff who has filed 200 identical suits negotiates differently than a first-time filer, and typically settles for less.

A few hours of the right lawyer’s time is one of the cheaper line items in this whole process. Settlement demands are opening positions, and represented defendants consistently pay less than unrepresented ones.

Step 4: Get an independent audit, not a widget (week one to two)

You need to know whether the claims in the letter are accurate, and how deep the problems actually go. The letter will list maybe five to ten issues; when we audit a site that’s received one, we almost always find more, and the plaintiff’s firm is counting on that.

So what does an audit actually buy you here? Verification, mostly. If the letter says your checkout can’t be completed with a keyboard and your auditor confirms it can, your attorney now has a factual defense on that claim.

It also tells you what remediation will really involve before you sign a settlement agreement committing to it, and nearly every settlement agreement includes that commitment. Signing one without an audit is agreeing to a renovation before anyone has inspected the house.

The audit does one more quiet job: it documents good faith. Dated evidence that you hired a professional and started fixing things is persuasive in negotiation, and in front of a judge if it gets that far. Proof that you acted early often counts for more than the current state of the site.

What you should not do is install an overlay widget and call it handled. The FTC fined accessiBe $1 million in 2025 for deceptive compliance claims, and roughly a quarter of accessibility suits now target sites that were running a widget when they got sued. Plaintiff firms can detect overlays, and some appear to treat them as a signal that the underlying site was never actually fixed. We wrote about this at length in our post on the FTC fine and what it means for widget customers.

If you’re on a legal clock, say so when you contact an auditor. We can scope and start within days when a response deadline is bearing down – ask about expedited timelines when you get a quote. A $495 homepage audit can also serve as a fast, cheap first read on how bad things are while the full engagement gets scoped.

Step 5: Fix the real barriers (weeks two through eight)

Whatever happens with the settlement, the barriers that are real need fixing, both because the next demand letter is otherwise a matter of time and because there are actual people who can’t use your site right now.

Repeat targeting is not hypothetical, either. Roughly 45% of 2025 federal digital accessibility defendants had been sued before. Settling with one plaintiff does not immunize you against the next one, and plaintiff firms share target lists in practice if not in name. The only durable exit from this cycle is a site that holds up to testing.

Prioritize by severity: barriers that block a task entirely (can’t complete checkout, can’t submit the contact form, can’t close a modal) come before cosmetic issues. A good audit report hands you this priority order with code-level guidance, so your developers fix instead of guessing. If you don’t have developers, remediation is a service you can buy – we do it, and so do others.

Step 6: Settle or fight, with your eyes open (timeline varies)

Most of these matters settle, and settling is often the rational move. Defense through trial can run $30,000 to $175,000 in legal fees even if you win, because Title III fee-shifting means a losing defendant often pays the plaintiff’s attorneys too. Against a settlement demand of $10,000, the math usually points one direction.

Fighting makes sense in narrower cases: the plaintiff has standing problems, the claims are demonstrably false against your preserved evidence, or the demand is wildly out of line for your size. Some federal courts, especially in New York, have grown visibly less patient with serial plaintiffs, and your attorney will know whether your case sits in that current.

There are two negotiation details worth knowing going in. Settlements after a demand letter run cheaper than settlements after a filed complaint, so speed has monetary value. And small businesses that can document limited revenue routinely settle below $10,000; if that’s you, make sure your attorney knows the real numbers.

An example of how this goes wrong

A store owner gets a demand letter on a Monday alleging twelve WCAG failures. She’s furious – the letter is clearly a template, two of the claims describe pages her site doesn’t have, and the whole thing smells like a shakedown. So she ignores it.

Six weeks later she’s served with a federal complaint. Now she needs a lawyer under deadline pressure, the settlement number has roughly doubled because the plaintiff’s firm has filing costs to recover, and she’s making decisions about her website in a panic instead of on a schedule. She installs a widget because it promises overnight compliance, which becomes an exhibit in the plaintiff’s next filing.

The frustrating part is that her instinct about the letter was half right. It probably was a template from a volume filer, and the two false claims were real leverage. Handled in week one with counsel and an audit, that letter likely resolves for a modest settlement and a remediation plan she controls. Handled in month three under a federal docket number, it costs multiples of that.

Frequently asked questions

I received an ADA website demand letter. What should I do first?
Preserve evidence before changing anything: save the letter, screenshot the pages it mentions, and archive your site as it exists today. Then contact an attorney with ADA Title III experience and commission an independent accessibility audit. Don’t respond to the plaintiff’s firm yourself, and don’t install an accessibility widget.

Is an ADA demand letter the same as a lawsuit?
No. A demand letter is a pre-litigation notice offering to settle before a complaint is filed. No court is involved yet, and matters resolved at the letter stage generally settle for less than matters that reach a docket. The threat behind the letter is real, though – the firms sending them file thousands of suits a year.

How much does it cost to settle an ADA website demand letter?
Most settle between $5,000 and $25,000, with small businesses frequently under $10,000. Factors include your revenue, the plaintiff firm’s history, whether the claims hold up, and whether a complaint has been filed yet. Legal defense through trial costs far more, which is why most defendants settle.

Can a small business be sued over website accessibility?
Yes. There is no small-business exemption under ADA Title III, and the majority of web accessibility suits target companies under $25 million in revenue. Serial plaintiffs favor defendants likely to settle quickly, which often means smaller businesses without in-house counsel.

Will installing an accessibility widget protect me?
No. Roughly 25% of accessibility lawsuits now name sites that were running a widget at the time of filing, and the FTC fined accessiBe $1 million in 2025 for overstating what its overlay could do. Widgets don’t fix the underlying code that the plaintiff’s expert will test.

How fast can I get an accessibility audit if I’m facing a deadline?
Faster than the standard timeline if you say so upfront. We can start within days when a client is on a legal clock, and a single-page audit can be turned around quickly to give your attorney an early factual read. Most full small-to-mid-size audits run one to two weeks from kickoff to report.

Does fixing my website make the demand letter go away?
Not by itself. Remediation resolves the injunctive side of the claim, but the plaintiff’s attorney fees are the engine of these cases, and those get resolved through settlement. Prompt, documented remediation does strengthen your negotiating position and reduces the odds of the next letter

Sources

Accessibility.build lawsuit research – settlement and legal-cost benchmarks by resolution type, including defense fee ranges.

Seyfarth Shaw ADA Title III blog: Federal court website accessibility lawsuit filings bounce back in 2025 – 3,117 federal website accessibility lawsuits in 2025, up 27% from 2,452 in 2024.

UsableNet ADA lawsuit tracker and year-end reports – total digital accessibility filings across federal and state courts, repeat-defendant rate (45-46% of 2025 federal cases named a defendant already sued before), and defendant revenue breakdowns.

UsableNet 2025 Midyear Digital Accessibility Lawsuit Report – filing pace, industry targeting, and plaintiff concentration for the first half of 2025.

EcomBack 2025 Mid-Year ADA Website Lawsuit Report – 31 plaintiffs accounted for over half of H1 2025 filings; 22.6% of sued sites had an accessibility overlay installed; 16 law firms filed the large majority of cases. The 7-10 demand letters per filed lawsuit estimate comes from defense attorneys interviewed alongside this report’s data.

FTC press release: order requires accessiBe to pay $1 million for deceptive claims – the January 2025 complaint and order, finalized April 2025.

Seyfarth Shaw ADA Title III blog: New York federal courts and serial plaintiffs – judicial skepticism toward serial filers in New York.

Accessible.org: ADA website lawsuits – typical settlement ranges and defense cost estimates from a firm that works with defense attorneys.