ADA Title II deadlines: what April 2027 and 2028 mean for procurement
The DOJ extended both web accessibility compliance dates by a year. Here is what actually changed, what did not, and what it means for software you are buying now.
On 20 April 2026 the Department of Justice issued an interim final rule extending the ADA Title II web accessibility compliance dates by one year. If you were planning against the original dates, your timeline moved. If you took that to mean the obligation moved, it did not.
The dates
The compliance date depends on the population your entity serves:
| Entity | Compliance date |
|---|---|
| Public entities serving 50,000 or more | 26 April 2027 |
| Public entities serving under 50,000, and special district governments | 26 April 2028 |
The standard is unchanged: WCAG 2.1 Level AA for web content and mobile applications.
What the extension did not change
Three things are worth being precise about, because the extension has been read more generously than it reads.
The obligation to provide accessible services did not pause. Title II's underlying requirements have applied for decades. The rule that moved sets a date for conformance to a specific technical standard; it did not create the duty, and it does not suspend it. People can and do take action over inaccessible content during the extension.
Enforcement is still expected at the new date. The DOJ has said it fully anticipates implementing the regulation at the extended deadline. This is a change of date, not of intent.
Your procurement cycle did not get a year longer. This is the part that matters most and gets noticed least.
Why the procurement math is tighter than the date suggests
Software you buy today will still be in service on the compliance date. A five-year contract signed this year runs past both deadlines.
That means the relevant question is not "when must we comply?" but "what are we buying between now and then, and will it conform?" Every system procured between now and April 2027 is a system you will either be relying on at the deadline or replacing before it.
Work backwards from a realistic cycle:
- A vendor sends a conformance report during evaluation.
- You find gaps and raise them.
- The vendor commits to remediation in a future release.
- That release ships — typically quarters, not weeks, later.
- You verify it actually shipped.
That sequence is comfortably a year for a single product. Repeated across a portfolio of systems, with procurement calendars and budget cycles layered on top, the extension buys less room than it appears to.
What this means concretely
For things you are buying now. Ask for a conformance report during evaluation, not after award. Once a contract is signed your leverage is a change order; before it, your leverage is the award itself. Name the standard explicitly in the solicitation — "WCAG 2.1 Level AA" — so the report you receive answers the question you asked.
For things you already bought. Somebody should establish which of your existing systems have current conformance reports on file and which do not. That inventory is unglamorous and it is the thing that tells you the size of the problem. Absence of a report is not evidence of conformance.
For your own content. Title II covers what you publish as well as what you procure — websites, mobile apps, and the documents on them. Vendor reports cover the first half of the exposure only.
The documentation is the defence
If your conformance is ever questioned, the useful artifact is rarely the software itself. It is the record: what you required, what the vendor disclosed, what you challenged, when, and what they committed to.
An agency that can show it required a conformance report, reviewed it against the named standard, raised the gaps in writing and tracked the vendor's response is in a materially different position from one that can show a signed contract and nothing else — even if both are running the same imperfect software.
That record is built during procurement or it is not built at all. Which is the real argument for starting now rather than in 2027.
Sources: the DOJ's interim final rule of 20 April 2026 extending the Title II compliance dates. Verify specifics against the Federal Register for your entity's classification — this is general guidance, not legal advice.
GOVvpat reviews the conformance reports your vendors submit and keeps the record of what was raised and answered. Request a quote.