US Federal · State & Local Government

ADA Title IIWebsite AccessibilityRequirements

Accessibility TeamWCAG 2.1 AA
United States

ADA Title II applies to state and local government websites and mobile apps. The DOJ extended compliance deadlines by one year in April 2026 — but the standard, the underlying duty, and private litigation exposure are all unchanged.

ADA Title II covers all state and local government entities — agencies, municipalities, counties, school districts, public universities, transit authorities, courts, and special districts. The Department of Justice published a final rule on April 24, 2024 that formally adopts WCAG 2.1 Level AA as the technical standard for government websites and mobile applications.

On April 20, 2026, the DOJ issued an Interim Final Rule extending the compliance deadlines by one year: public entities serving 50,000 or more now have until April 26, 2027 (originally April 24, 2026), and entities under 50,000 plus special district governments now have until April 26, 2028 (originally April 26, 2027). The substantive requirements are unchanged — only the dates moved. WCAG 2.1 Level AA remains the standard; the DOJ did not adopt WCAG 2.2.

A 60-day public comment period on the extension ran through June 22, 2026, and the DOJ has signaled possible further rulemaking. Treat the technical standard as stable but the broader regulatory picture as still evolving.

What is ADA Title II Website Accessibility Requirements?

ADA Title II prohibits discrimination on the basis of disability in services, programs, and activities provided by state and local government entities. For digital accessibility, this means government websites, web applications, and mobile apps must be accessible to people with disabilities.

The 2024 DOJ rule removed prior ambiguity by explicitly requiring conformance with WCAG 2.1 Level AA for web content and mobile applications used to access government services. Covered content includes online forms, document portals, payment systems, scheduling tools, and any digital interface through which residents interact with government programs.

Limited exceptions exist for archived web content, certain pre-existing conventional electronic documents (e.g. PDFs posted before the compliance date), third-party content not under the entity's control, and pre-deadline social media posts. These exceptions are narrowly defined; relying on them without documented justification creates enforcement risk.

Risk, enforcement, and penalties

  • Inaccessible online forms that prevent residents from completing required transactions independently.
  • PDF documents posted without accessible structure, alt formats, or text equivalents.
  • Payment portals or scheduling systems not operable with keyboard or screen reader.
  • Third-party platforms integrated without accessibility verification or contractual requirements.
  • Video content (public meetings, official communications) published without captions or audio descriptions.

Who it applies to

  • State governments, local governments, and their instrumentalities: counties, cities, towns, school districts, public universities, community colleges, transit authorities, courts, law enforcement agencies, public hospitals, housing authorities, and special districts.
  • The digital accessibility rule covers any web content or mobile application the entity uses to provide services, programs, or activities to the public — paying taxes, registering for programs, requesting permits, accessing court records, completing any government transaction.
  • Contractors and vendors providing digital services on behalf of covered entities are not directly regulated under Title II, but the government entity remains responsible for the accessibility of services delivered through third-party platforms. The rule applies even where a private vendor operates the digital asset. Procurement language and vendor accountability are critical controls.

WCAG benchmark

The 2024 DOJ rule adopts WCAG 2.1 Level AA as the technical standard. The DOJ did not adopt WCAG 2.2, did not change the conformance level, and did not narrow scope. WCAG 2.1 AA spans 50 success criteria across perceivable, operable, understandable, and robust — covering keyboard navigation, screen-reader compatibility, color contrast, form labeling, and error identification.

WCAG conformance is not a safe harbor: an entity could technically conform and still fail to provide effective communication to a specific individual. But documented WCAG conformance significantly strengthens an entity's legal position and demonstrates the kind of good-faith effort DOJ weighs in enforcement decisions.

For forward-looking teams: most accessibility programs already audit against WCAG 2.2 AA (the de-facto industry standard), so building to 2.2 satisfies the 2.1 floor and future-proofs the work against later updates.

Common misconceptions

Title II only applies to physical buildings, not websites.

The 2024 DOJ rule explicitly requires WCAG 2.1 AA conformance for state and local government websites and mobile applications. Digital services are squarely covered.

Small municipalities and special districts are exempt.

There is no size exemption under Title II. Only the compliance deadline differs — entities under 50,000 and special districts get until April 26, 2028 instead of April 26, 2027.

Posting a PDF satisfies accessibility requirements.

PDFs must themselves be accessible — tagged, with reading order, alt text, and accessible form fields. An inaccessible PDF is just as much a barrier as an inaccessible web page.

Third-party vendor platforms are outside our responsibility.

The government entity remains responsible for the accessibility of services delivered through third-party platforms. Procurement specifications and vendor accountability are the practical controls.

Good-faith compliance checklist

  • Documented accessibility policy with a designated coordinator and published grievance procedure
  • Systematic testing against WCAG 2.1 AA with dated audit reports and remediation tracking
  • Procurement requirements with accessibility specifications and vendor accountability
  • Staff training records covering content authors, developers, and procurement officers
  • Responsive handling of prior complaints with documented remediation
  • Ongoing monitoring to prevent regression as the digital estate grows

Recent lawsuits

2024DOJ Civil Rights Division (letter of findings)

United States v. State of Alaska

DOJ found that Alaska denied voters with disabilities an equal opportunity to participate in elections, including by maintaining an inaccessible elections website alongside physical polling-place and ballot issues.

Settled

Why it matters: Election infrastructure is high-stakes; DOJ prioritizes access to democratic participation, and election websites are a recurring focus area.

2024DOJ Civil Rights Division + U.S. Attorneys' Offices (E/N/S/W Districts of Texas)

Four Texas Counties (Colorado, Runnels, Smith, Upton)

County election websites discriminated against individuals with vision or manual disabilities, in violation of Title II.

Settled

Why it matters: Shows DOJ pursuing smaller jurisdictions, not just large states, and the concrete structural remedies (independent audit, coordinator, training, feedback channel) it requires.

2024U.S. Department of Justice (settlement agreement)

Service Oklahoma

Service Oklahoma — a state agency — maintained a mobile application that was inaccessible to individuals with vision disabilities.

Settled

Why it matters: Confirms that mobile applications — not just websites — are squarely within Title II scope, and reinforces that the DOJ's enforcement reach extends to state agencies' app properties.

Frequently asked questions

Does ADA Title II apply to government contractor websites?

Yes — the government entity remains responsible even when a vendor operates the asset. Use procurement language and vendor accountability clauses to push accessibility requirements down the supply chain.

What is the deadline for ADA Title II website accessibility compliance?

April 26, 2027 for public entities serving 50,000 or more. April 26, 2028 for entities under 50,000 and special district governments. Both dates reflect the one-year extension issued in the April 2026 Interim Final Rule.

Are there exceptions for legacy content or archived documents?

Yes, narrowly. The rule excepts archived web content, certain pre-existing conventional electronic documents (e.g. PDFs posted before the compliance date), third-party content not under the entity's control, and social-media posts published before the deadline. Document the basis for any exception you rely on.

Can we satisfy Title II by providing a phone number for assistance?

No. An alternative contact method does not substitute for an accessible digital service. The rule requires the website or app itself to be accessible to people with disabilities.

Does WCAG 2.1 AA conformance guarantee compliance?

No standard is an automatic safe harbor, but documented WCAG 2.1 AA conformance is the benchmark DOJ and courts reference. It substantially strengthens an entity's legal position and is the practical target.

What happens if we receive a complaint before the deadline?

Existing ADA obligations and the effective-communication requirement apply today, regardless of the WCAG conformance deadline. Respond to the complaint, document the remediation, and don't wait for 2027 or 2028 to act.

How does ADA Title II interact with Section 508?

Section 508 covers federal agencies; Title II covers state and local governments. Both reference WCAG-based standards, but they apply to different jurisdictions and are enforced separately.

Do public universities fall under ADA Title II?

Yes — public colleges and universities are state instrumentalities covered by Title II. Most fall in the 50,000-or-more tier, putting their compliance deadline at April 26, 2027.

Questions about ADA Title II Website Accessibility Requirements?

Book a consultation — our team can walk you through how this law applies to your specific product and stack.

Disclaimer. This page provides general information about ADA Title II Website Accessibility Requirements for orientation purposes only and is not legal advice. Laws and enforcement practices change; consult qualified counsel for decisions specific to your product or organization.