ADA Title II: the new 2027 and 2028 deadlines and what software vendors must do
On 20 April 2026 the US Department of Justice pushed back the compliance dates in its ADA Title II rule for web content and mobile apps by one year. If you sell software to public schools, colleges, universities, cities, counties or state agencies, the new dates set your customers' timetable, and so your own. This guide covers what changed, what did not, and what vendors should do now.
The new compliance dates
The extension is an interim final rule published in the Federal Register as document 2026-07663. It took effect on 20 April 2026 (Federal Register, 91 FR 20902).
| Public entity | Original date (2024 rule) | New date |
|---|---|---|
| State and local governments with a total population of 50,000 or more | 24 April 2026 | 26 April 2027 |
| Public entities with a total population under 50,000, and all special district governments | 26 April 2027 | 26 April 2028 |
The current text of the regulation, 28 CFR 35.200(b), already reflects the new dates (eCFR, 28 CFR part 35, subpart H). The DOJ invited comments on the interim rule until 22 June 2026, so check ADA.gov for any later change before you rely on a date in a contract.
Which date applies to a school district? The DOJ says a school district is not a special district government. A city school district uses the city's population and a county school district uses the county's. An independent school district uses the Census Bureau's Small Area Income and Poverty Estimates (ADA.gov fact sheet). For a part of a larger government without its own population figure, such as a city police department or library, the DOJ says to use the population of the government it belongs to. For most governments that figure comes from the 2020 Census.
What did not change
Only the dates moved. Everything else in the April 2024 final rule (89 FR 31320) stands:
- The standard is WCAG 2.1 Level AA, for both web content and mobile apps (W3C, WCAG 2.1).
- It covers content provided through vendors. Section 35.200(a) applies to web content and mobile apps that a public entity "provides or makes available, directly or through contractual, licensing, or other arrangements".
- The five exceptions are unchanged (28 CFR 35.201): archived web content; preexisting conventional electronic documents, unless still used to apply for or take part in a service; content posted by a third party, unless the third party posts under a contract or other arrangement with the entity; individualized password-protected documents; and preexisting social media posts.
- The limits on alternatives are unchanged. A conforming alternate version is allowed only where direct accessibility is not possible "due to technical or legal limitations" (35.202). The rule also covers equivalent facilitation (35.203), fundamental alteration and undue burden (35.204), and noncompliance with a minimal impact on access (35.205).
- The ADA's general duties still apply before and after the dates: effective communication, reasonable modifications, and equal opportunity to participate.
How a rule for governments reaches software vendors
Title II places the legal duty on the public entity, not on you. But a school district cannot meet its duty for a learning platform it licenses unless the platform conforms. So the requirement flows to vendors through procurement and contracts.
The ADA.gov fact sheet is explicit about the third-party exception. It does not cover "content posted by a state or local government's contractor or vendor". If a company manages or posts content for the government, that content "would usually need to meet WCAG 2.1, Level AA". The fact sheet lists public schools, community colleges, public universities, public libraries, public hospitals, courts and transit agencies among the entities covered.
For a vendor, this shows up as:
- RFPs and renewals that ask for an Accessibility Conformance Report (ACR) against WCAG 2.1 AA or later;
- contract clauses asking you to state conformance, fix defects within a set time, or share a remediation plan;
- questions from accessibility offices at colleges and districts, often alongside a security review.
The extension gives your customers another year, but most will not wait until April 2027 to evaluate tools. Contracts signed or renewed in the 2026–27 school year will run past the deadline, so the questions arrive now.
What software vendors should do now: seven steps
1. Map which customers are covered, and when
List your public-sector customers and pipeline with their population band: 50,000 or more means 26 April 2027, smaller entities and special districts 26 April 2028. Note renewal dates that fall before each deadline. That is where accessibility will come up first.
2. Evaluate the product against WCAG 2.1 AA, or 2.2
The rule names WCAG 2.1 AA. WCAG 2.2 adds criteria on top of 2.1, so a WCAG 2.2 AA evaluation also answers a 2.1 requirement and lasts longer. Test the parts real users touch: sign-in, the core workflows, content created in your editor, and any mobile app. Use a keyboard, at least one screen reader, zoom and reflow, as well as automated checks. Automated tools catch only part of the problems.
3. Publish an honest ACR
Write the results up in the ITI VPAT 2.5Rev template. The WCAG edition covers 2.0, 2.1 and 2.2 (ITI). Name the product version, date the report, state your test method, and write specific remarks. "Partially Supports" with a workaround and a fix date is more useful to a district than a wall of "Supports". New to the format? Read What is a VPAT? first.
4. Put the ACR where buyers can find it
Link it from your product page, your trust or security page, and any LMS or app-directory listing. In AccessRecord's review of the 471 tool listings in the public Edu App Center catalog (data checked 11 October 2026), only 41 led to an ACR a buyer could open. Thirty said "available on request", and 12 of the 69 that linked to an ACR led to a broken page. A reviewer who cannot open your report will move on to one they can.
5. Write a remediation roadmap you can keep
Where the ACR says "Partially Supports" or "Does Not Support", have a dated plan ready. Buyers ask for one, and contracts increasingly refer to it. Under-promise. A missed fix date damages trust more than a later, honest one.
6. Prepare for contract language
Expect clauses that ask you to warrant WCAG 2.1 AA conformance, to fix reported barriers within a set period, and to give accessible alternatives in the meantime. Decide in advance what you can commit to, and make sure your ACR and your contract say the same thing.
7. Keep the record current
Conformance is a property of a version. Each release can fix or introduce a barrier, and a report from two releases ago describes software the customer is not using. Re-test after significant releases and re-issue the ACR. Keep earlier versions available so a contract that cites an old report still makes sense.
How this relates to Section 508 and other rules
Title II covers state and local government. Federal agencies are covered by Section 508, whose Revised Standards incorporate WCAG 2.0 Level AA (US Access Board, ICT standards). The VPAT 2.5 508 edition reports against those. Many states also have their own accessibility requirements for agencies and schools. If you sell to both federal and state or local buyers, an INT edition ACR or separate WCAG and 508 editions will cover both.
Quick answers
Does the extension mean we can wait?
Not if you sell to public bodies. Their evaluations and renewals happen before the deadline, and they ask vendors now.
Does Title II apply to private companies directly?
Title II applies to public entities. Vendors are reached through contracts, licensing and procurement, as described above. Private businesses open to the public fall under Title III, which this rule does not cover.
Is there an official certificate we can get?
No. There is no DOJ certification, and ITI does not certify VPATs. What a buyer can check is your ACR and the product itself.
Where AccessRecord fits
AccessRecord is software for publishing and maintaining ACRs. It puts your report on a public page at a stable link, pinned to the product version it describes, and flags it when a release moves past it. It does not test your product. You or your auditor do that, and it works with any auditor's findings. If nobody on your team has time to write the report, there is a fixed-price option to have one written.
Sources
- US Department of Justice, interim final rule, Extension of Compliance Dates, 91 FR 20902, 20 April 2026 (PDF on ADA.gov)
- US Department of Justice, final rule, 89 FR 31320, 24 April 2024 (Federal Register)
- 28 CFR part 35, subpart H (current text, eCFR)
- ADA.gov, Fact sheet: new rule on the accessibility of web content and mobile apps
- W3C, WCAG 2.1 and WCAG 2.2
- ITI, VPAT 2.5Rev