ADA Title II Web Accessibility: The 2027 Deadline and What It Actually Takes

The Department of Justice finalized its ADA Title II web accessibility rule in April 2024. State and local governments — and any "public entity" under Title II — were given two or three years to comply, depending on size. Then, in April 2026, DOJ issued an interim final rule extending the deadlines by exactly one year, citing implementation complexity.

The relief is real but limited. The technical bar didn't move. The covered entities didn't change. The vendors and contractors who supply websites, apps, and digital tools to public entities are now squarely in scope. And the 50,000+ population entities have until 24 April 2027 to comply — not 2028, not "eventually." The smaller entities have until 2028.

Here's what this rule actually requires and what teams should be doing right now.

What the Rule Says (In Plain English)

Title II of the Americans with Disabilities Act prohibits state and local governments from discriminating against people with disabilities. For 30+ years, that obligation has applied to physical buildings, services, and programs. But "web content" wasn't explicitly addressed in regulation, which led to a patchwork: courts disagreed, DOJ enforced inconsistently, plaintiffs sued sporadically. Public entities lived in legal ambiguity.

The 2024 final rule fixed that. Under 28 CFR Part 35, every state and local government entity must make its web content and mobile applications conform to WCAG 2.1 Level AA — the static 2018 version of WCAG 2.1, specifically.

Two things matter about that wording.

"Web content" is broad. Websites are obvious. So are intranets, learning management systems, library databases, public records portals, transit apps, parking apps, court filing systems, school district communications platforms, parks and rec registration, water utility billing, public health information pages. Almost anything a public entity puts online for users.

"WCAG 2.1 Level AA" is technical. It's an internationally recognized standard from the W3C with 50 specific success criteria across four principles: Perceivable, Operable, Understandable, Robust. Most public entities haven't been measured against it before. Most of their websites currently fail.

Who's Actually Covered

Title II covers public entities — which the regulation defines as state and local government and their departments, agencies, instrumentalities, and Public Special Districts. Practically, that includes:

• All 50 states and their executive agencies
• Cities, counties, townships, and municipalities
• Public school districts (K-12) and state colleges/universities
• Public libraries
• Public utilities and transit authorities
• Public hospitals
• Special districts (water, fire, parks, etc.)
• Public courts

The rule explicitly does not apply to federal agencies (they have Section 508 instead) or private businesses (Title III applies to them, with separate case law).

For vendors and contractors, you're not directly regulated — but your government customers are, and they're contractually pushing the accessibility requirements down to you. If you build websites, apps, content management systems, document services, or digital services for state and local governments, expect WCAG 2.1 AA conformance clauses in every new contract from 2026 onward.

The Deadlines (After the 2026 Extension)

The April 2026 interim final rule extended both deadlines by one year:

• Entities with population 50,000+ (including all 50 states, large cities, large counties, large school districts, large public universities): compliance required by 24 April 2027 (was 2026).
• Entities under 50,000 population, including most school districts, small cities, towns, and special districts: compliance required by 24 April 2028 (was 2027).

The rule defines "total population" by reference to the most recent decennial census or American Community Survey estimates. Special districts always get the smaller-entity timeline. School districts use their enrollment population, not the district boundary population — a clarification several state attorneys general had asked for.

DOJ was clear in the extension that this is a one-time accommodation, not a signal that deadlines will keep moving. The extension was driven by procurement timelines, the complexity of remediating legacy content, and the limited supply of accessibility expertise. The next stop is real enforcement.

What WCAG 2.1 AA Actually Requires

The 50 success criteria boil down to a few practical themes. If you're hearing this in a meeting and need the elevator version:

Text alternatives. All images need alt text. All videos need captions and audio descriptions. All audio needs transcripts. PDFs need to be tagged or replaced with HTML.

Keyboard accessibility. Every interactive element on every page must be operable using only the keyboard — no mouse required. Focus order has to be logical. Focus indicators have to be visible.

Color and contrast. Text needs minimum 4.5:1 contrast against its background (3:1 for large text). Color can't be the only way to convey information.

Forms and inputs. Every form field needs a programmatically associated label. Error messages need to be clear, identifiable, and announced to assistive technology.

Headings and structure. Pages need proper heading hierarchy (H1, H2, H3 in order). Tables need row/column headers. Lists need to use list markup, not just dashes.

Time limits. If you have session timeouts or auto-advancing content, users need to be able to extend or disable them.

Mobile-specific. WCAG 2.1 added criteria for orientation, input modalities, motion-based interactions, and touch target sizes. Mobile apps and responsive websites are squarely in scope.

Accessibility statement. Every covered web property needs a clear, current accessibility statement explaining conformance status, known limitations, and how to report barriers.

The bar isn't perfection. It's WCAG 2.1 AA conformance, which is auditable and well-documented. Tools like axe, WAVE, Lighthouse, and Accessibility Insights can identify roughly 30–40% of issues automatically. The rest requires manual testing — keyboard-only navigation, screen reader testing (NVDA, JAWS, VoiceOver), real-user testing.

The Hardest Parts (In Practice)

A few categories of content consistently trip teams up.

Legacy PDFs. Many public entities have decades of PDFs — meeting minutes, ordinances, forms, reports — that were never tagged for accessibility. Remediating each is non-trivial. The rule allows entities to archive content that isn't currently used or made available, but anyone who's tried to define "archived" knows the trap. If a PDF is linked from your current site, it's not archived.

Third-party content embedded in your site. Your social media feeds, your YouTube embeds, your map widgets, your third-party form builders, your payment processors — if they don't meet WCAG 2.1 AA, you're not compliant. This drives a lot of vendor conversations.

User-generated content. A user comments section, citizen-submitted images, public-records uploads. The rule doesn't make the entity responsible for retroactive remediation of all user content, but the platform (your CMS, your portal) must be accessible.

Documents people produce on demand. Property tax records, building permits, court filings. These are generated on the fly. The system needs to produce accessible output — not just be accessible as an interface.

Live and synchronous content. Live council meetings, school board meetings, court hearings. Real-time captions are required. Many entities have been getting by with auto-generated captions that aren't accurate enough; the rule pushes that quality bar up.

How This Sits Next to Section 508 and Title III

The federal landscape:

• Section 508 (federal agencies and federal contractors) — already requires WCAG 2.0 AA for federal procurement. Many federal procurements already require WCAG 2.1 in practice. Vendors with Section 508-aligned products are largely in good shape for Title II.
• Title III (private businesses) — case law applies WCAG-equivalent standards to "places of public accommodation" with digital interfaces, but there's no federal regulation specifying the standard. Practical effect: private websites face a similar bar, enforced through litigation rather than regulation.
• State accessibility laws — California, New York, and others have their own state-level accessibility statutes. These continue to apply in addition to Title II.

For state and local governments that already aligned to Section 508 internally (many do, for grant compliance), the Title II rule is more about formalizing what's already happening than building from scratch.

What to Do This Year

If you're a state or local government IT or digital services team:

1. Inventory your digital surface. All public-facing websites, intranets, apps, and tools. Note ownership (in-house vs vendor) and last review date. Don't forget subdomains and entity-controlled microsites.
2. Run automated scans. Use axe, WAVE, Lighthouse, or Accessibility Insights to identify the obvious issues. This catches 30–40% of problems and gives a baseline. Don't stop here — automated tools miss most issues.
3. Pilot manual audits. Pick three or four high-traffic properties and run full WCAG 2.1 AA audits. This sets the scope for remediation and reveals your real-world workload.
4. Update procurement. Every new contract for a digital tool, website redesign, document service, or content management system needs WCAG 2.1 AA conformance language and periodic audit rights. Sample VPATs (Voluntary Product Accessibility Templates) should be required.
5. Train your content authors. PDFs, social media posts, web pages, and emails published by hundreds of staff members are the long-tail problem. Title II remediation only sticks if content authors learn to produce accessible content by default.
6. Publish an accessibility statement and feedback channel. Even before full compliance, having a transparent statement of where you are and how to report barriers is required and signals good faith.
7. Plan for ongoing testing. Accessibility isn't a project — it's an operating capability. Build periodic auditing, regression testing, and user testing with people with disabilities into your software lifecycle. Many public entities are partnering with disability community organizations for this.

For vendors:

1. Get your VPATs current. A VPAT 2.5 Rev (WCAG 2.1 + 508 + EN 301 549) is the standard form. Any product you sell to state/local government needs one.
2. Build accessibility into your roadmap. Don't treat it as a one-time remediation. Add it to your definition of done.
3. Track WCAG 2.2 too. The rule cites WCAG 2.1, but WCAG 2.2 is already published and is the direction of travel. Some procurements are starting to ask for 2.2.

The Bottom Line

The one-year extension is breathing room, not relief. The 50,000+ population entities have less than 12 months to ship. The smaller entities have ~24 months. The procurement work, the vendor remediation, the legacy PDF cleanup, and the staff training don't compress easily.

The good news: WCAG 2.1 AA isn't an aspirational standard. It's well-documented, has open-source testing tools, has an established consultant and remediation market, and is the accessibility bar used in most developed countries. There's no need to invent a methodology. There's a need to start.

The bad news: the public entities that have been treating accessibility as a one-attorney's-concern, fix-it-when-someone-complains issue are looking at a near-term staffing and budget problem. Title II enforcement is a credible threat now in a way it wasn't before — both from DOJ and from private plaintiffs using the regulation as a baseline.

If you're starting late, the right move is to scope, prioritize highest-impact content first, and visibly publish your remediation plan. A documented good-faith effort to comply, with realistic timelines, is the strongest defense in an enforcement context — better than a quiet inventory you never started.

References

1. Final Rule on Web and Mobile App Accessibility (28 CFR Part 35) — U.S. Department of Justice (April 2024)
2. Extension of Compliance Dates — Interim Final Rule — Federal Register (April 2026)
3. Web Content Accessibility Guidelines (WCAG) 2.1 — W3C Recommendation
4. Section 508 Standards — General Services Administration