ADA Title II for small cities, towns and special districts

If you work for a small city, a town, a rural county or a special district, the ADA Title II web rule gives you one more year than larger governments. That is the whole of the difference. The standard is the same, the scope is the same, and the rule applies to the software you license from vendors exactly as it applies to the pages you write yourself. This is what ADA Title II means for small cities and similar entities, and how to use the time.

Which date applies

The DOJ's 2024 rule (28 CFR part 35, subpart H) originally set compliance dates of 24 April 2026 and 26 April 2027. On 20 April 2026 an interim final rule moved each back by one year:

Entity	Compliance date
Public entities, other than special district governments, with a total population of 50,000 or more	26 April 2027
Public entities with a total population under 50,000	26 April 2028
Special district governments, of any size	26 April 2028

The standard for both groups is WCAG 2.1 Level AA, for web content and for mobile apps. The 50,000 line was not arbitrary: the DOJ chose it because it matches the Regulatory Flexibility Act's definition of a "small governmental jurisdiction".

How population is counted for small cities and towns

The rule uses a defined term, "total population", in 28 CFR 35.104. It is not the number of people who use your website, and it is not your service area as you would describe it. In order:

1. If the Census Bureau calculated a population for your entity in the most recent decennial Census, that figure is your total population. For most cities, towns, townships and counties, that means the 2020 Census.
2. Independent school districts use the Census Bureau's most recent Small Area Income and Poverty Estimates instead.
3. An entity with no Census population of its own that is an instrumentality or commuter authority of one or more governments that do have one uses the combined Census population of those governments.

The third rule is where small departments get caught. A city library, a police department, a parks department or a municipal utility that is part of a city has no population of its own. It takes the city's. If the city has 62,000 residents, the library's date is 26 April 2027, however small its staff or budget. The DOJ's own fact sheet gives the school example: a city school district uses the city's population, a county school district uses the county's.

So the first task is a short one. Look up your entity's 2020 Census figure, or the figure for the government you belong to, and write down which date applies and why. It takes minutes and it removes a surprising amount of internal confusion.

Special district governments

The rule defines a special district government as a public entity, other than a county, municipality, township or independent school district, that is authorized by state law to provide one function or a limited number of functions, has enough administrative and fiscal autonomy to qualify as a separate government, and has no population calculated by the Census Bureau. The DOJ's examples include mosquito abatement districts, utility districts, transit authorities, water and sewer boards and zoning districts.

All special district governments get the later date, 26 April 2028, whatever the size of the region they serve. The DOJ's reasoning was that their populations are not calculated by the Census Bureau, so there is no reliable number to sort them by, and that single-purpose bodies tend to have narrower budgets.

Two cautions. First, a large transit or water authority is still a special district if it meets the definition; the later date is not a judgment about its size. Second, not every authority is a special district. One that lacks independent status and operates as an instrumentality of a city or county falls under rule 3 above and takes the parent government's population. If your entity's classification is not obvious, that is a question for counsel, and it is worth asking early.

What the extra year does not change

The later date is a later date. Nothing else is softened for small entities.

• Same standard. WCAG 2.1 Level AA, Level A and Level AA success criteria and conformance requirements.
• Same scope. The rule covers web content and mobile apps a public entity provides or makes available "directly or through contractual, licensing, or other arrangements". Your payment portal, agenda software and permitting system are covered even though a vendor built them. See ADA Title II and third-party vendors.
• Same exceptions. The five exceptions in 28 CFR 35.201 (archived web content, preexisting conventional electronic documents, certain third-party content, individualized secured documents, preexisting social media posts) apply to everyone, with the same conditions.
• Same limits on the defenses. The rule's fundamental alteration and undue burdens provision (28 CFR 35.204) is available, but it is not a small-entity exemption. The entity carries the burden of proof, the decision must be made by the head of the entity or a designee after considering all available resources, it must come with a written statement of reasons, and the entity must still provide access to the maximum extent possible.

The underlying Title II obligation to provide accessible services has applied for decades and was not deferred by either rule. The deadlines article covers this in more detail.

Why small governments depend more on vendors

A city of 300,000 may have a web team. A town of 8,000 often has a clerk who also maintains the website, and almost everything a resident does online runs on someone else's software: a hosted content management system, an online payment processor, utility billing, recreation registration, meeting agendas and minutes, permits and inspections, job applications.

That changes where the work is. A small government can fix its own content: headings, link text, image descriptions, the PDFs it posts. It cannot fix a vendor's checkout form that is unusable by keyboard. For most small entities, the larger part of the exposure sits in products they license and cannot modify.

The practical consequence is that a small government's main accessibility tool is procurement. What you require when you buy or renew, and what you do with the vendor's Accessibility Conformance Report, does more for conformance than almost anything you can do in-house.

A sequence for the next eighteen months

As of this writing, 26 April 2028 is about eighteen months away. That is one or two budget cycles, and for many vendors a handful of product releases. A workable order:

1. Inventory. List every public-facing website, portal and app, who provides it, and when its contract renews. Renewal dates matter more than anything else on the list.
2. Ask for reports. Request a current ACR from each vendor, written to the WCAG 2.1 (or INT) edition of VPAT 2.5, for the version you actually run. Note who does not have one.
3. Rank by what residents must do. Paying a bill, applying for a permit, registering for a program and reading meeting agendas come before an events calendar. Gaps in those workflows, especially at Level A, come first.
4. Use renewals. A renewal falling before the deadline is your best point of leverage. Put the standard, the report and a remediation commitment into the renewal rather than waiting for the next solicitation.
5. Fix your own content in parallel. The preexisting documents exception covers only documents posted before your compliance date, and not those currently used to apply for, gain access to or participate in a service. Application forms are not exempt because they are old.
6. Keep the record. What you asked each vendor, what they answered, and what they committed to. For a small entity without specialist staff, that record is the evidence of a reasonable process.

State law may set its own terms

Some states have their own accessibility requirements for state agencies or for local governments, and they do not all follow the federal dates or standards. Check your state's page before assuming the federal rule is the only one that applies; California's is one example.

---

Sources: 28 CFR part 35, subpart H, and the definitions of "total population" and "special district government" in 28 CFR 35.104 (the DOJ's 2024 Title II web rule, 89 FR 31320, including its section-by-section analysis); the DOJ's interim final rule of 20 April 2026 (91 FR 20912); the DOJ's ada.gov fact sheet on the web rule. This is general guidance, not legal advice.

GOVvpat reviews the conformance reports your vendors submit, so a small team does not need an accessibility specialist to read them. Request a quote.