For a typical small-business website, making it ADA compliant takes about 4 to 12 weeks: one to two weeks for an audit, then a remediation sprint of two to ten weeks depending on size and complexity. E-commerce stores usually land at three to four months, and large web apps longer. Anyone promising compliance in 48 hours is selling a widget, not remediation — and the “3 to 8 months” figure that tops Google applies to government websites, not yours.
Here’s where those numbers come from, what actually happens week by week, and the one deadline that genuinely matters for a business: the clock a demand letter starts.
The short answer, by site type
In Curbcut’s remediation engagements, timelines cluster by site type more than anything else. Page count matters less than you’d think — what drives the schedule is the number of templates, forms, and third-party components that need fixing and re-testing.
| Site type | Audit | Remediation | Typical total |
|---|---|---|---|
| Brochure site (under 20 pages, one template) | About 1 week | 2–3 weeks | 4–6 weeks |
| Small-business site (20–100 pages, forms, blog) | 1–2 weeks | 3–6 weeks | 6–10 weeks |
| E-commerce store (product templates, cart, checkout) | 2–3 weeks | 6–10 weeks | 3–4 months |
| Web app or large multi-template site | 3–4 weeks | 3–6+ months | 4–8 months |
Independent providers land in the same range. TestPros, a security and compliance firm, says “a full website remediation can take anywhere from 4-6 weeks,” extending for sites with many pages or complex features. The target in every case is the same standard courts and the DOJ point to: WCAG 2.1 AA.
One honest caveat: these are timelines to a remediated, tested site, not to a magic certificate. Accessibility isn’t a one-time stamp — new content can reintroduce barriers, which is why the last phase below is ongoing.
Why the “3 to 8 months” answer you found isn’t about you
If you searched this question, you likely found estimates of three to eight months. That figure describes government websites under a different part of the ADA. Accessible.org’s Title II timeline guide recommends state and local governments “plan for approximately 3-8 months” per website — and notes it’s safer to budget the full eight, because these projects run over more often than they finish early.
Those government deadlines also explain the urgency in much of what ranks. According to Jackson Lewis, the DOJ announced in April 2026 that Title II compliance dates were extended to April 26, 2027 for entities serving 50,000 or more people and April 26, 2028 for smaller ones. We break down that rule in our Title II web rule explainer.
Private businesses fall under Title III, which has no calendar deadline at all. That sounds like good news until you realize what replaces it: plaintiffs’ law firms set your deadline for you, one demand letter at a time. More on that clock below.
Can a website really be ADA compliant in 48 hours?
No — and the source of that number is worth knowing. Overlay vendor accessiBe’s own accessWidget page says the product “improves accessibility and usability in as little as 48 hours” and that its “AI-powered process takes up to 48 hours from the initial installation.”
What the widget does in 48 hours is install. It does not repair your HTML, your form labels, or your checkout flow — the things a screen-reader user actually hits. In January 2025, the FTC ordered accessiBe to pay $1 million to settle charges that it falsely claimed its product could make any website WCAG compliant, an order the Commission finalized in April 2025.
So when you compare a “48-hour” option against a “6-week” option, you’re not comparing two speeds of the same thing. One is a script that loads over broken code; the other is fixing the code. Only one of them ends with a site a disabled customer can use.
What actually happens during those weeks
A remediation engagement isn’t six weeks of mystery. It breaks into four phases — the same three cost phases we describe in our ADA compliance cost guide, plus a verification pass:
- Audit (1–3 weeks). A tester goes through your site with a screen reader, a keyboard, and automated tools, mapping every failure against WCAG 2.1 AA. The output is a prioritized fix list — here’s what a real audit includes. This is also where your timeline stops being an estimate and becomes a schedule.
- Remediation (2–10+ weeks). Developers fix the code: alt text, form labels, focus order, contrast, ARIA, heading structure. Template fixes come first because one corrected template repairs every page built on it. This phase is where site type drives everything — a Shopify theme with a dozen apps behaves differently than a static brochure site.
- Verification (about 1 week). Every fix gets re-tested with the same assistive technology that found it. Skipping this step is how “remediated” sites fail the exact same screen-reader test six months later.
- Monitoring (ongoing). New products, posts, and PDFs reintroduce barriers. Ongoing monitoring catches them before a plaintiff’s tester does — and keeps the calendar from resetting to week one.
The clock that actually matters: a demand letter’s response window
Here’s the timeline question almost nobody ranking for this keyword answers: how long do you have once a lawyer is already looking at your site? Much less time than remediation takes.
Demand letters typically include a “deadline for response, usually 30 to 60 days from the letter date,” according to accessibility firm TestParty — and if you ignore it, the sender “typically files a lawsuit in federal court within weeks or months.” Once a suit is filed, the law firm NK Legal notes you generally have just 21 days to respond in federal court, and missing that risks a default judgment.
Now put the two timelines side by side. A 30-day response window against a 6-to-16-week remediation schedule means you cannot fully fix a typical site inside the letter’s deadline. What you can do in 30 days is start an audit, show documented good-faith progress, and give your attorney something real to negotiate with. Some states even reward that: Missouri’s SB 907, effective August 28, 2026, presumes a later lawsuit abusive when a business takes substantial corrective steps within 90 days of notice.
The exposure behind this is not hypothetical for small companies. UsableNet’s 2025 year-end lawsuit data counted more than 5,000 digital accessibility lawsuits filed in 2025, and 64% of sued companies generated under $25 million in annual revenue. The same report found 1,427 suits targeted companies that had already been sued once — so a rushed, cosmetic fix doesn’t close the risk either.
Overlay vs. DIY vs. professional remediation: the honest comparison
| Overlay widget | DIY / in-house | Professional manual remediation | |
|---|---|---|---|
| Time to “done” | Installs in about 48 hours (vendor claim) | Months of part-time work; depends entirely on your developer’s accessibility experience | 4–12 weeks for most small-business sites |
| Reaches real WCAG 2.1 AA? | No — the underlying code is untouched | Possible, but self-testing misses what trained screen-reader testing catches | Yes — audited, fixed, and re-verified against each criterion |
| Holds up under a demand letter? | Weak — suits are routinely filed against sites running widgets, and the FTC fined the leading vendor over its compliance claims | Only with documentation you probably aren’t producing | Strongest — dated audit, remediation log, and re-test evidence |
| Honest verdict | Fastest to install, but it doesn’t shorten the road to actual compliance at all | Workable for simple sites if your developer commits to learning WCAG — budget far more calendar time | The fastest route to compliance that’s real; costs more up front than a widget subscription |
If your developer wants to attempt the DIY route, our guide to making a website ADA compliant lays out the steps — just budget calendar time honestly.
How to shorten the timeline without cutting corners
Most delays we see aren’t technical. The same engagement can run four weeks or ten depending on things you control:
- Have code and hosting access ready on day one. Waiting on a former web designer for admin credentials is the single most common week-eater.
- Name one decision-maker. Fixes like rewriting link text or re-ordering a form need fast yes/no answers, not a committee.
- Freeze major redesigns mid-project. Remediating a template that’s being rebuilt means paying for the work twice.
- Fix templates before pages. One corrected product template can repair hundreds of pages at once — prioritize accordingly.
- Start with a scan, not a guess. An automated baseline tells you which tier of the table above you’re actually in before anyone quotes a schedule.
That last one is where we’d start. Run a free accessibility scan and you’ll see your site’s biggest issues in minutes — and we’ll follow it with a fixed-scope quote and a firm timeline, so “how long” stops being a range on a blog post and becomes a date on your calendar.