ADA Title II Compliance: A Practical Guide for Government Agencies

Who this guide is for

If you're an IT director, ADA/Section 504 coordinator, or compliance officer at a state agency, county, city, school district, transit authority, or any other state or local government entity, this guide walks through what ADA Title II actually requires of your digital properties right now, what changed with the DOJ's 2026 rule extension, and where to start if you haven't yet begun a formal compliance effort.

The legal baseline: Title II applies to every government entity, regardless of size

Title II of the ADA prohibits state and local governments from discriminating against people with disabilities in any service, program, or activity — an extremely broad category that includes courts, public schools and universities, transit systems, parks, voting, social services, and government websites and apps. Unlike Title III, which applies to private businesses meeting certain criteria, Title II has no minimum size threshold: if your organization is an instrumentality of a state or local government, Title II applies, full stop.

That baseline nondiscrimination obligation has been in force since Title II took effect in 1992. What's newer is a specific technical standard for digital accessibility.

The 2024 rule and the 2026 extension

In April 2024, the DOJ finalized a rule requiring state and local governments to make their web content and mobile applications conform to WCAG 2.1 Level AA — the first time the federal government mandated a specific technical web accessibility standard under the ADA. The rule covers all web pages on your entity's site, web content you provide through third parties, mobile applications, and content posted to social media when it functions as an official communication channel. It carries limited exceptions for archived content, third-party content you don't control, preexisting conventional electronic documents (unless they address currently provided services), and certain password-protected course content at educational institutions.

On April 20, 2026, the DOJ published an Interim Final Rule (91 Fed. Reg. 20902) extending the original compliance dates by one year:

• April 26, 2027 for entities serving populations of 50,000 or more (originally April 24, 2026)
• April 26, 2028 for entities serving populations under 50,000, and for special district governments regardless of population (originally April 26, 2027)

The DOJ stated it issued the extension because it had "overestimated the capabilities (whether staffing or technology) of covered entities" to meet the original timeline, and it also reclassified special district governments into the smaller-entity tier. A public comment period on the IFR ran through June 22, 2026.

Here's the part that matters most for planning purposes: the extension changes only the WCAG 2.1 AA technical-conformance deadline. It does not pause Title II's underlying nondiscrimination mandate, which is already in force; it does not affect DOJ's authority to investigate complaints in the meantime; and it does not affect a private plaintiff's ability to sue your entity directly in federal court over an inaccessible website today, without needing to wait for your compliance deadline to pass. The DOJ has said it "fully anticipates implementing the regulation at the new deadline" — this is a scheduling adjustment, not a reprieve. For the full timeline and FAQ detail, see our breakdown of the DOJ Title II rule and 2026 IFR and the Title II legal reference page.

What a self-evaluation and transition plan involve

Title II's implementing regulations require public entities with 50 or more employees to conduct a self-evaluation: a systematic review of current policies, practices, programs, and services to identify where people with disabilities are being denied equal access. For digital properties, this means inventorying your websites, web applications, mobile apps, and the documents and third-party tools embedded in them, then assessing each against WCAG 2.1 AA.

Based on that self-evaluation, entities develop a transition plan — a document that identifies the barriers found, describes the specific steps needed to remove them, sets a schedule (with milestones), and names who is responsible for each item. The transition plan must be made available for public inspection, which also means it functions as a public accountability document, not just an internal roadmap.

Practically, for a digital accessibility self-evaluation, expect to:

• Inventory every public-facing website, subdomain, and mobile app your entity operates or controls
• Identify third-party platforms embedded in your digital properties (payment processors, permit/licensing portals, appointment scheduling, public comment forms, GIS map tools)
• Run automated scans across your highest-traffic and highest-consequence pages as a baseline (our Compliance Checker is a reasonable free starting point for this)
• Layer in manual testing — keyboard navigation and screen reader passes — on your most critical citizen-facing flows: permit applications, tax payments, court filings, public meeting notices, emergency alerts
• Document findings against WCAG 2.1 AA criterion by criterion, using our WCAG Quick Reference to map issues to specific success criteria
• Prioritize remediation by both citizen impact and legal exposure, and build that prioritization into your transition plan's schedule

For the full methodology behind a rigorous evaluation, our ADA audit process guide covers the three layers — automated, manual structural review, and assistive-technology testing — that a complete evaluation should include, and our self-check guide is a reasonable starting point if you want to get a baseline going before commissioning formal audit work.

Designating an ADA Coordinator

Public entities with 50 or more employees must designate at least one ADA Coordinator — a responsible employee who coordinates the entity's Title II compliance, manages grievance procedures, and serves as the public point of contact for accessibility complaints. Your entity is required to publicize this person's name and contact information.

Many ADA Coordinators today oversee both physical and digital accessibility, which means the role increasingly touches website governance, procurement standards, and staff training on content authoring (alt text, heading structure, accessible document formats) alongside the traditional facilities-and-programs mandate. If your entity doesn't currently have someone in this role with digital accessibility explicitly in scope, closing that gap is one of the highest-leverage organizational steps you can take.

Procurement: where a lot of government accessibility risk actually lives

Government websites rarely run on custom-built code alone — most rely on third-party platforms for payments, permitting, scheduling, GIS mapping, public comment forms, and content management. That means a meaningful share of your Title II exposure is determined by vendor choices made during procurement, often years before an accessibility complaint surfaces.

The standard tool for evaluating a vendor's accessibility posture during procurement is the VPAT (Voluntary Product Accessibility Template) — a standardized document vendors complete describing how their product conforms to WCAG, Section 508, and related standards. Requesting and actually reading a VPAT before you sign lets you catch accessibility gaps at the negotiating table instead of after a citizen complaint lands on your ADA Coordinator's desk.

Practical procurement steps:

• Require a current VPAT as part of any RFP or contract renewal for public-facing digital tools. "Current" matters — a VPAT from two product versions ago doesn't describe what you're actually buying.
• Read the remarks, not just the conformance ratings. A vendor who marks every criterion "Supports" with no explanatory detail is a red flag; specific, detailed remarks are a better signal of a genuine evaluation.
• Build accessibility requirements into contract language, not just into the RFP evaluation criteria, so there's a remedy if a vendor's product doesn't perform as represented after deployment.
• Test embedded third-party tools yourself once integrated — a vendor's VPAT describes their product in isolation, not necessarily how it behaves once embedded in your specific site template.
• Include an accessibility maintenance clause for ongoing conformance across vendor updates, not just at initial delivery.

Practical first steps if you're just getting started

1. Confirm your population tier and deadline. Know whether your entity falls in the 50,000+ tier (April 26, 2027) or the under-50,000/special-district tier (April 26, 2028), and work backward from there.
2. Designate or confirm your ADA Coordinator, and make sure digital accessibility is explicitly part of that role's mandate.
3. Run a baseline scan of your most-visited and most-consequential pages using our Compliance Checker, and do a first-pass manual check using our self-check guide.
4. Inventory third-party tools embedded across your digital properties and request current VPATs from each vendor.
5. Start (or update) your self-evaluation and transition plan, and make sure the transition plan is genuinely available for public inspection, not just filed away.
6. Budget for a full professional audit on your highest-traffic and highest-consequence citizen-facing flows well before your deadline — not in the final quarter before it.
7. Don't treat the 2026 extension as a pause. The underlying nondiscrimination mandate is active today, and the extension is a scheduling adjustment for the technical conformance deadline, not a reason to slow down.

Ready to take the next step? Grow Wild Agency offers a free preliminary WCAG 2.1 AA scan to help your agency establish a baseline before committing to a full Title II self-evaluation and remediation plan.