The ADA website deadline for smaller public entities is April 26, 2027.
The Department of Justice's ADA Title II rule sets WCAG 2.1 Level AA as the technical standard for state and local government websites, mobile apps and documents. Entities serving 50,000 or more were due on April 24, 2026. Everyone else — including every special district, whatever its size — is working to the date below.
Time remaining until
221 days remaining until the compliance date.
The April 26, 2027 compliance date has passed.
What matters now is what you can evidence: an inventory, real testing, and a dated remediation plan. Talk to us about where you stand.
A plain-language summary of a technical standard, not legal advice. Which obligations reach your entity is a question for your counsel — we provide the technical assessment and the remediation behind it.
Find your group.
The rule splits public entities by the population they serve. Special districts are the exception that catches people out: they are in the later group regardless of size.
Population 50,000+
· WCAG 2.1 Level AA
State and local government entities serving a population of 50,000 or more.
Under 50,000, and all special districts
· WCAG 2.1 Level AA
Public entities serving fewer than 50,000 people, and special district governments of any size — water districts, transit authorities, library systems, school districts.
Selling into the EU
· EN 301 549 (WCAG Level AA)
Products and services sold into the EU — e-commerce, consumer banking, e-books, ticketing, transport — generally demonstrated through EN 301 549.
If your deadline has passed, the question is no longer whether you made it. It is whether you can show a regulator, a resident or opposing counsel what you have tested, what you found, and what you are doing about it — on a dated plan with names against it.
WCAG 2.1 Level AA, across more than your website.
This is where most entities under-scope the work. The rule reaches web content and mobile apps a public entity provides or makes available — not just the pages your web team controls.
In scope
- Your main website, and every department microsite nobody remembers commissioning
- Mobile applications you offer to the public
- Documents you publish — agendas, minutes, budgets, permit forms, notices
- Third-party portals for permitting, utility billing, 311 and payments
- Content posted by contractors and vendors on your behalf
- Public meeting video, and its captioning
What "conformant" means in practice
There is no certificate and no permanent status. What exists is a conformance claim: a statement that defined content meets WCAG 2.1 Level AA at a point in time, backed by testing evidence. That is what you would be asked to produce.
- An inventory of everything public-facing
- Testing that goes beyond an automated scan
- A dated remediation plan with named owners
- A published accessibility statement and a working feedback path
- Trained content authors and accessibility language in procurement
The single most common mistake is treating a clean automated scan as conformance. Automated tools evaluate a minority of WCAG — the criteria they cannot judge are exactly the ones that block people. You can see the full standard, criterion by criterion, in our WCAG 2.2 success criteria reference, or run our free checker against your own pages right now.
What 221 days actually buys you.
Public-sector time is not calendar time. Between a budget cycle, a procurement cycle and a council calendar, the window is narrower than the number above suggests. This is the sequence that fits.
Now — inventory and baseline
Catalogue every public-facing property, portal, app and document library, then audit the highest-impact ones against WCAG 2.1 AA. You cannot budget for, or procure, work you have not scoped. This is weeks, not months, and it is the step that makes everything after it possible.
Next — get it funded and contracted
Take the baseline into a budget request or a grant application with a phased cost structure. If the scope exceeds your small-purchase threshold you are running a solicitation, and that timeline belongs to procurement, not to you. Start it before you feel ready.
Then — remediate what blocks people
Fix the barriers that stop a resident completing a task first: navigation, forms, permitting, payments. Then fix at the component level so every template inherits the correction rather than repeating the defect.
Alongside — deal with the documents
The PDF library is usually the longest pole and the most commonly deferred. Inventory it, retire what is obsolete, convert high-traffic forms to accessible HTML, and remediate only what genuinely must stay a document.
Before the date — make it evidenced and durable
Publish the accessibility statement and feedback path, adopt a written policy naming the standard and an owner, train the staff who publish, and put accessibility language into procurement so the next portal does not recreate the problem.
Nothing detonates on the date.
No penalty triggers automatically on April 26, 2027. Exposure arrives the way it always has — a complaint to the Department of Justice, or a private suit, usually prompted by a resident who could not do something.
What changes is the ground you are standing on. With a named technical standard in the rule, "we were making a good-faith effort" is a weaker position than it used to be, and "we have an inventory, current test results and a dated plan with owners" is a much stronger one. The gap between those two is work you can start this month.
The entities that handle this worst are the ones that do nothing until a letter arrives, then buy an overlay widget. Overlays do not produce conformance, and they do not touch the documents or the vendor portals.
Start here
- The nine steps, in order — what to do and when
- Check your own pages free — no email, results immediately
- How a municipal engagement runs
- Contracting paths and vendor information
- Which other rules reach you
- Writing accessibility into an RFP
What public entities ask us first.
When is the ADA website compliance deadline?
Under the Department of Justice's ADA Title II rule, public entities serving 50,000 or more people were required to conform to WCAG 2.1 Level AA by April 24, 2026. Public entities serving fewer than 50,000, and special district governments of any size, have until April 26, 2027.
Does the ADA Title II web rule apply to special districts?
Yes. Special district governments are covered regardless of the population they serve, and they fall in the later group with an April 26, 2027 compliance date. That includes water districts, transit authorities, library systems and school districts.
What standard does the ADA require for websites?
The rule names WCAG 2.1 Level AA specifically. That is a defined technical standard, not a general expectation, which means conformance can be tested and evidenced rather than argued.
Does the deadline cover PDFs and third-party portals?
Yes. The rule reaches web content and mobile apps a public entity provides or makes available. That includes documents such as agendas, minutes and permit forms, and services delivered through a vendor's platform — if residents pay a bill or apply for a permit through a third-party portal, that is still a service you provide.
What happens if we miss the deadline?
There is no automatic penalty that triggers on the date. Exposure comes through complaints to the Department of Justice and private suits, and the practical question becomes what you can evidence: an inventory, real testing, and a dated remediation plan with owners carry far more weight than nothing at all.
How long does it take to become WCAG 2.1 AA conformant?
An audit of a typical public-sector site runs a few weeks. Remediation depends on how the site was built — a coherent design system can be largely fixed in one cycle, while a decade of accumulated templates and an untagged PDF library is a phased programme. The document backlog is usually the longest pole.
Is an accessibility overlay enough to comply?
No. Overlay widgets do not produce WCAG conformance, are rejected by much of the disability community, and have themselves been cited in accessibility litigation. They also do not touch PDFs, vendor portals, or your source markup.