ADA Title II Deadline Extended to 2027: What It Means

If you run or build a website for a city, a county, a school district or a public college, you have probably been asked some version of this: "Didn't the ADA deadline get pushed back?" It did, by one year. But the rule itself did not change, the old obligations under the ADA never had a deadline to push, and for a large public entity the new date is now about seven months away.

This guide explains what the Justice Department actually changed, which date applies to which organization, what stayed exactly the same, and how to use the time that is left. It is general information, not legal advice.

What actually changed

On 24 April 2024 the Department of Justice published its rule on the accessibility of web content and mobile apps under Title II of the ADA, which covers state and local governments (Federal Register, 89 FR 31320). It adopted WCAG 2.1 Level AA as the technical standard and gave public entities two years or three years to comply, depending on size.

On 20 April 2026, four days before the first deadline, the Department published an interim final rule that moved both dates back by one year (Federal Register, 91 FR 20902). It took effect the same day. That is the entire change: two dates in 28 CFR 35.200(b).

The Department gave its reasons in the rule. It cited letters from higher education and school district associations and from the Small Business Administration's Office of Advocacy about staffing and cost, and concluded that it had "overestimated the capabilities (whether staffing or technology) of covered entities to comply with the rule in the time frames provided." It also recorded the other side: disability and accessibility organizations wrote that the rule should not be delayed.

The dates that now apply

Public entity	Original date	Date now
Total population of 50,000 or more	24 April 2026	26 April 2027
Total population under 50,000	26 April 2027	26 April 2028
Special district government (any size)	26 April 2027	26 April 2028

Source: the interim final rule above, and the Department's updated small entity compliance guide.

How to tell which date a client has

"Total population" is not the number of people an organization serves, and it is not its headcount. It is the Census population of the government the organization belongs to (ADA.gov first steps). The Department's own examples make this concrete:

• A state university with 40,000 students in a state of 6 million people takes the state's population, so its date is April 2027.
• A branch library serving 3,000 patrons in a county of 70,000 takes the county's population, so April 2027.
• A police department in a city of 25,000 takes the city's population, so April 2028.

School districts are not special district governments. A city or county school district uses the population of that city or county, and an independent school district uses the most recent Small Area Income and Poverty Estimates. Special districts, such as a water board or a transit authority, get the later date whatever their size. If you work with a public college or a mid-sized city, assume April 2027 until someone shows you otherwise.

What did not change

The interim rule says so directly: it "does not alter the substantive requirements adopted in the 2024 final rule, including the scope of coverage." Everything below is the same as it was in 2024.

The standard

Web content and mobile apps that a public entity provides or makes available, directly or through contracts and licensing, must meet WCAG 2.1 Level AA. That includes content built and posted by vendors: calendars, payment systems, maps and booking tools the entity puts on its site are its responsibility, according to the compliance guide. If you are the agency that builds and maintains the site, the content you post for the client is covered too. If you have not already, put that in writing with the client; our guide to accessibility clauses in client contracts covers how.

If you already test against WCAG 2.2 AA, you are testing a superset. WCAG 2.2 keeps every 2.1 success criterion except 4.1.1 Parsing, which is obsolete and removed, and adds nine new ones (W3C, What's new in WCAG 2.2). Our plain English guide to WCAG explains the levels.

The exceptions, and why their cutoff moved too

The rule keeps five exceptions: archived web content, preexisting conventional electronic documents (PDF, Word, presentation and spreadsheet files), content posted by third parties who are not acting for the entity, individualized password-protected documents such as a utility bill, and preexisting social media posts. Most come with several conditions, and the compliance guide is clear that an exception does not apply unless every one of them is met.

Here is the part many summaries miss. Three of those exceptions are defined by the compliance date: archived content, preexisting documents and preexisting social media posts. Archived content must have been created before "the date your government must comply," and a preexisting document must have been on the site before that date and not be used now to apply for or take part in a service. When the date moved, the cutoff moved with it. A large entity's PDF posted in May 2026 would not have been "preexisting" under the old date; under the new one it can be, if it is not in current use.

That is useful, and it is also a trap. Forms, applications and anything a resident uses to take part in a service never qualify, however old they are. The PDF accessibility checker is a quick way to see how much work the documents that do not qualify will need.

More runway, not a reprieve

Three reasons to treat the extra year as time to do the work properly rather than time to wait.

• Title II already applied to websites. The interim rule says: "Regardless of the compliance dates, covered entities have an ongoing obligation to ensure that their services, programs, and activities offered using web content and mobile apps are accessible to individuals with disabilities in accordance with their existing obligations under title II of the ADA." The Department's 2022 web guidance describes that as its longstanding position.
• People can still sue under Title II. The interim rule itself notes that Congress created a private right of action in Title II. The rule gave that exposure a precise technical yardstick; it did not create the exposure.
• The details may change again. The Department wrote that it "plans to engage in future rulemaking processes related to the substantive requirements" and will consider a proposed rule during the extension. Comments on the interim rule closed on 22 June 2026. As of 30 September 2026, the Federal Register shows no further document under the rule's identifier, RIN 1190-AA82. Plan for WCAG 2.1 AA, which is what the rule says today, and watch for a proposal.

For a manager or a council, the short version is: the date moved, the requirement did not, and the organization was already expected to make its services usable by people with disabilities before any of this.

Private-sector sites get no extra time

This rule, and its extension, cover only state and local government. The interim rule says in a footnote that it does not address the Title III regulations for businesses. Title III covers businesses open to the public, and the Department has no regulation setting a technical standard or a deadline for their websites; its web guidance points to WCAG and the Section 508 standards as helpful references. Nothing about a private company's position moved in April 2026. If you have heard "the ADA deadline was extended" from a shop, a clinic or a law firm, that is a misunderstanding worth correcting.

A plan for the time that is left

A large public entity has about seven months before 26 April 2027. A smaller one has about nineteen before 26 April 2028. The same steps apply to both; only the pace differs. The Department's first steps guide is a good outline, and this is how it translates into site work.

1. Inventory. List every site, subdomain, app and third-party tool the entity puts in front of the public: payment, booking, forms, maps, video. Mark who controls each one.
2. Baseline scan. Run an automated scan on the pages people use most: home, contact, payments, applications, the most visited services. A free accessibility scan gives you a starting count in minutes. Keep the dated result; it is the "before" in your progress record.
3. Manual checks on key journeys. Automated checks find many real failures but cannot confirm that a page conforms to WCAG. Walk each key task with a keyboard alone (our keyboard and focus checker and keyboard testing guide help), and check headings and landmarks (headings and landmarks checker). Our note on Lighthouse scores explains why a perfect score is not an audit.
4. Sort the documents. Decide which PDFs and files meet an exception, which can be retired, and which must be fixed or replaced with HTML. Forms and anything still in use go first.
5. Fix in order of harm. Services people need first: payments, applications, registration, anything with a deadline. Then high-traffic content, then the rest.
6. Vendors. Ask every vendor for a current accessibility conformance report and a date for fixing known issues. Put WCAG 2.1 AA into renewals and new contracts.
7. Keep it fixed. Train the people who publish content, and rescan on a schedule so new pages and new documents do not undo the work.

Our guide to auditing a website for accessibility goes through steps 2 and 3 in more detail, and the ADA Title II web rule page keeps the dates and sources in one place.

Checklist

• Confirm the client's date from its Census population, not its size or audience.
• Tell the client plainly: one more year, same standard, same exceptions, same existing obligation.
• Use the new cutoff for archived content and old documents, and never apply it to forms or content in current use.
• Scan the key pages now and keep the dated report.
• Test the key journeys by hand with a keyboard.
• List every vendor tool and ask each vendor for its plan.
• Correct anyone in the private sector who thinks this extension applies to them.
• Check the Federal Register for a new proposal before each quarterly review.