Does this apply to public universities?

Yes. Public colleges and universities are arms of state government and are covered by Title II. The 2024 rule and 2026 IFR apply to admissions sites, registrar systems, public-facing course catalogs, library catalog interfaces, athletics sites, and LMS-hosted public content. Population tiering generally follows the population the parent entity (the state) serves, so most public universities fall in the April 26, 2027 cohort. Password-protected coursework areas fall under the pre-existing password-protected content carve-out, but only for content unchanged since the relevant compliance date — actively maintained LMS courseware is in scope.

What about a contractor or agency building a state portal?

The Title II obligation rides with the public entity, not the contractor — but contracts and procurement language are now the practical compliance lever. A vendor or agency building a state portal should expect WCAG 2.1 AA conformance to be a contractual deliverable, with audit rights, defined remediation SLAs, and indemnification for accessibility findings post-launch. Agencies that quietly hand over inaccessible sites are the most common source of Title II exposure for public entities. For the practical side, our ADA demand-letter response guide covers what to do when a complaint arrives.

Are we required to remediate archived content?

Generally no — the 2024 rule includes an archived-content exception, preserved by the 2026 IFR. To qualify, content must (1) be kept solely for reference, research, or recordkeeping, (2) be clearly identified as archived, (3) be stored in a dedicated archive area, and (4) not have been changed since being archived. If you 'archive' content but still link to it from a current navigation menu or reuse parts of it in active programs, it will not qualify. The carve-out is narrower than it sounds.

What if our vendor has not been ADA-tested?

Most public-sector SaaS vendors will provide a VPAT (Voluntary Product Accessibility Template) or ACR (Accessibility Conformance Report) on request. Treat unverified VPATs as a starting point, not a deliverable — run an independent automated scan against the live vendor interface, then a manual review of the highest-traffic flows (login, search, payment, form submission). Findings should drive a remediation plan negotiated with the vendor, with target dates aligned to your population-tier deadline.

Compliance & Lawsuits

ADA Title II for State and Local Governments: Web Accessibility Deadlines

Last updated May 25, 2026

On April 20, 2026, the U.S. Department of Justice published an Interim Final Rule (Federal Register doc 2026-07663) extending the ADA Title II web and mobile-app compliance dates by one year. State and local government entities serving a population of 50,000 or more now have until April 26, 2027; entities serving fewer than 50,000 people, plus special district governments serving such populations, have until April 26, 2028. The technical target is unchanged: web content and mobile apps must conform to WCAG 2.1 Level AA — not 2.2 — because the underlying 2024 rule binds Title II to the 2.1 standard.

This page is the niche, government-specific companion to our broader ADA website compliance guide. If you build or remediate sites for a state agency, a city, a public university, a public-school district, a county court, or a special district (water, transit, library), the rest of this page is for you.

What ADA Title II covers

Title II of the Americans with Disabilities Act applies to public entities — defined by 42 U.S.C. § 12131 as any state or local government, any department or agency of a state or local government, and any special-purpose district. The 2024 DOJ rule and its 2026 extension cover the web content and mobile applications these entities provide to the public. In practice this sweeps in:

State and city government sites — the public-facing portal, every agency subdomain, and the mobile apps a resident might use to pay a parking ticket, renew a permit, or check trash pickup.
Public K-12 schools and districts — student/parent portals, lunch-menu PDFs, board-meeting agendas, athletics calendars, and any teacher-published page hosted on the district domain.
Public colleges and universities — admissions, registrar, course catalogues, LMS-hosted public pages, library catalogue interfaces, and athletics sites.
Courts and court-adjacent systems — e-filing portals, public-records lookup tools, jury-summons response forms.
Special district governments — transit authorities, water and sewer districts, library districts, port authorities, and similar single-purpose public bodies.

The rule covers content the entity itself publishes and content posted on its behalf by contractors and vendors. A third-party portal vendor that holds the parking-payment flow does not absorb the public entity's Title II obligation; the entity still owns it.

Population-tier deadlines

The April 2026 Interim Final Rule pushed both original deadlines back by one year. The current schedule:

Compliance date	Who must comply
April 26, 2027	Public entities serving a total population of 50,000 or more, and any special district government serving a population of 50,000 or more. Original deadline was April 24, 2026.
April 26, 2028	Public entities serving a total population of fewer than 50,000, and any special district government serving such a population. Original deadline was April 26, 2027.

Population is measured using the most recent U.S. Census data the entity uses for general administrative purposes. For multi-purpose entities (a county that contains both 50K+ cities and sub-50K townships), the higher tier governs the county's own sites and apps; sub-entities are evaluated independently.

What WCAG 2.1 AA actually requires

The rule binds public entities to WCAG 2.1 Level AA — the 2018 update to WCAG 2.0 that added 17 success criteria, most of them mobile-touch and low-vision focused. WCAG 2.2 (published in October 2023) is not the Title II standard; the DOJ rule and its 2026 extension both explicitly reference 2.1. The Level A and Level AA criteria together cover four broad areas:

Perceivable — text alternatives for non-text content, captions and transcripts for multimedia, sufficient color contrast (4.5:1 for normal text, 3:1 for large), and resizable text without loss of content.
Operable — full keyboard access without traps, sufficient time to read and use content, no seizure-inducing flashing, and clear navigation with skip links and meaningful page titles.
Understandable — readable language declaration, predictable navigation patterns, and input assistance including labeled form fields and clear error identification.
Robust — compatibility with assistive technologies, valid name/role/value exposure for every UI control, and conformant status-message announcements.

For the practical Level A vs. Level AA breakdown and what to target if you have headroom past AA, see our WCAG conformance levels guide.

Title II topics agencies often miss

The 2024 rule is broader than most procurement teams initially read it. Four areas trip up government remediation programs more than any others.

Third-party portal vendors. State permitting, tax, and payment portals are typically run by a handful of national SaaS vendors. The public entity owns the Title II obligation regardless. Contracts signed after the relevant compliance date should require WCAG 2.1 AA conformance, include an audit clause, and tie remediation SLAs to violation severity.
Social-media content the entity controls. Posts on an official account that link to or embed information about programs and services fall inside the rule. Image posts need alt text; videos need captions; PDFs linked from posts need to be tagged.
Public-facing PDFs. Budget documents, board-meeting minutes, planning notices, and forms published as PDF are some of the most common Title II violations. They need tagged structure, proper reading order, alt text on figures, and accessible form fields where interactive. Image-only scans are not compliant.
Captioned and described video. Auto-generated YouTube captions are not WCAG-conformant captions. SC 1.2.2 requires synchronized accurate captions; SC 1.2.5 requires audio description for prerecorded video where visual content carries meaning the audio does not. Board-meeting recordings and public-information videos are the most common failure cases on government sites.
Maps and geographic content. Interactive maps published by transit authorities, planning departments, and emergency-management agencies must offer an equivalent accessible alternative — a list view, a downloadable tagged document, or a text description that conveys the same information. A map alone is not a compliant primary surface.

What changed: the April 2026 Interim Final Rule

The April 2026 Interim Final Rule did two things. First, it pushed both original compliance dates back by one year — the larger-entity deadline moved from April 24, 2026 to April 26, 2027, and the smaller-entity / special district deadline moved from April 26, 2027 to April 26, 2028. DOJ cited new information about compliance capacity received in the months leading up to the original 2026 date as the trigger for the extension. Second, the IFR opened a written-comment window closing June 22, 2026, which the Department will use to evaluate whether further adjustments to the rule are warranted.

The IFR preserved — and did not narrow — the 2024 rule's existing exceptions: archived web content (content kept solely for reference, research, or recordkeeping, clearly identified as archived, and not modified since being archived); pre-existing conventional electronic documents (Word, PDF, PowerPoint, Excel) posted before the relevant compliance date unlessthey are currently used to apply for, gain access to, or participate in services; pre-existing content on password-protected individualized portals (e.g., a student grade page); and content posted by third parties on a public entity's site that is not posted by, for, or on behalf of the entity. None of these carve-outs are blanket — read the rule text before relying on one.

One concrete operational implication: the extension does notchange Section 504 obligations, and HHS's May 2026 Section 504 web-accessibility deadline for recipients of federal financial assistance is independent of the Title II schedule. Many public universities and public health agencies are covered by both.

Frequently asked questions

Does this apply to public universities?: Yes. Public colleges and universities are arms of state government and are covered by Title II. The 2024 rule and 2026 IFR apply to admissions sites, registrar systems, public-facing course catalogs, library catalog interfaces, athletics sites, and LMS-hosted public content. Population tiering generally follows the population the parent entity (the state) serves, so most public universities fall in the April 26, 2027 cohort. Password-protected coursework areas fall under the pre-existing password-protected content carve-out, but only for content unchanged since the relevant compliance date — actively maintained LMS courseware is in scope.
What about a contractor or agency building a state portal?: The Title II obligation rides with the public entity, not the contractor — but contracts and procurement language are now the practical compliance lever. A vendor or agency building a state portal should expect WCAG 2.1 AA conformance to be a contractual deliverable, with audit rights, defined remediation SLAs, and indemnification for accessibility findings post-launch. Agencies that quietly hand over inaccessible sites are the most common source of Title II exposure for public entities. For the practical side, our ADA demand-letter response guide covers what to do when a complaint arrives.
Are we required to remediate archived content?: Generally no — the 2024 rule includes an archived-content exception, preserved by the 2026 IFR. To qualify, content must (1) be kept solely for reference, research, or recordkeeping, (2) be clearly identified as archived, (3) be stored in a dedicated archive area, and (4) not have been changed since being archived. If you 'archive' content but still link to it from a current navigation menu or reuse parts of it in active programs, it will not qualify. The carve-out is narrower than it sounds.
What if our vendor has not been ADA-tested?: Most public-sector SaaS vendors will provide a VPAT (Voluntary Product Accessibility Template) or ACR (Accessibility Conformance Report) on request. Treat unverified VPATs as a starting point, not a deliverable — run an independent automated scan against the live vendor interface, then a manual review of the highest-traffic flows (login, search, payment, form submission). Findings should drive a remediation plan negotiated with the vendor, with target dates aligned to your population-tier deadline.

How SweepHound helps

SweepHound runs dual-engine automated WCAG 2.1 / 2.2 scans (axe-core plus IBM Equal Access) across the pages and flows you point it at, produces concrete remediation guidance with before/after code, and generates an accessibility statement you can adapt for a public-entity Title II program. For state and local government use, treat the scan as the automated layer of a broader compliance program — Title II readiness also requires procurement policy updates, manual keyboard and screen-reader review of high-traffic flows, PDF remediation, and ongoing monitoring of vendor-hosted portals. See our manual accessibility checklist for the human-review pass that no automated tool can replace, and our ADA demand-letter response guide for the playbook when a complaint or DOJ letter lands.

To see what a dual-engine scan flags on a government site or vendor portal, start a free scan. Paid plans add scheduled re-scans, authenticated scanning for staff-portal areas, and the statement generator — see pricing for the agency-friendly tiers.

Sources

Federal Register, Extension of Compliance Dates for Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities (FR Doc 2026-07663) — Primary source. DOJ Interim Final Rule, published April 20, 2026, extending Title II web/app compliance dates to April 26, 2027 and April 26, 2028.
U.S. Department of Justice, ADA.gov — Web and Mobile App Accessibility Under Title II — Primary source. DOJ plain-language summary of the 2024 final rule, including covered entities, applicable standard (WCAG 2.1 AA), and the original compliance schedule the 2026 IFR extended.
U.S. Code, 42 U.S.C. § 12131 — Definitions (Title II covered entities) — Primary source. Statutory definition of "public entity" for Title II coverage scope.
W3C, Web Content Accessibility Guidelines (WCAG) 2.1 — Primary source. The technical standard incorporated by reference in the DOJ Title II web rule.
Seyfarth Shaw, DOJ Extends ADA Title II Website Accessibility Deadlines for Governmental Entities — Secondary. Law-firm analysis of the IFR and ongoing litigation risk for public entities during the extension window.