ADA Title II Web Rule Deadlines: 2026 & 2027 Compliance Guide

Published January 15, 2025  ·  8 min read

In April 2024, the U.S. Department of Justice published a final rule under Title II of the Americans with Disabilities Act requiring all state and local government entities to make their websites and mobile applications conform to WCAG 2.1 Level AA. This is the most significant federal web accessibility mandate in decades, and it affects tens of thousands of public entities across the United States.

This guide explains who is covered, what the deadlines are, what WCAG 2.1 AA actually requires, and what practical steps you can take right now to prepare.

Compliance Deadlines at a Glance

Category 1 — Larger jurisdictions
April 24, 2026

Public entities with a population of 50,000 or more, plus state governments regardless of size.

Category 2 — Smaller jurisdictions
April 26, 2027

Public entities with a population of fewer than 50,000 and special district governments.

Source: DOJ ADA.gov — Web Accessibility Final Rule (2024)

Who Must Comply?

Title II covers all state and local government entities. In practice, this means:

  • State government agencies and departments
  • County and city governments
  • Public school districts (K–12)
  • Public colleges and universities
  • Public libraries
  • Transit authorities and transportation agencies
  • Courts and judicial agencies
  • Special districts (water, fire, parks, etc.)

Private businesses are not covered by Title II (they fall under Title III), but a growing body of court decisions and DOJ guidance makes WCAG 2.1 AA the practical standard for private websites as well. See our WCAG audit guide for small businesses for more on that.

What Does WCAG 2.1 Level AA Actually Require?

The W3C Web Content Accessibility Guidelines (WCAG) 2.1 organize requirements under four principles — often shortened to POUR:

PPerceivable
  • Alt text for images
  • Captions for video
  • Sufficient color contrast (4.5:1+)
OOperable
  • Full keyboard navigation
  • No keyboard traps
  • Skip navigation links
UUnderstandable
  • Clear form labels and error messages
  • Consistent navigation
  • Language declared in HTML
RRobust
  • Valid, semantic HTML
  • ARIA used correctly
  • Works with screen readers

Full technical specification: WCAG 2.1 — W3C Recommendation

Exceptions in the Rule

The DOJ rule includes several limited exceptions. These are narrow and should not be used to avoid compliance broadly:

  • Archived content: Web content that has not been changed since the compliance deadline and is kept only for reference or legal record.
  • Preexisting conventional electronic documents: PDFs, Word files, and similar documents posted before the compliance date — unless they are actively used to apply for government services.
  • Third-party content: Content posted by third parties that is not under contract with or for the government entity, and over which the entity has no editorial control.
  • Password-protected individual content: Content that is password-protected and maintained about a specific individual, such as a student's records — but the service itself must still be accessible.

How to Prepare Before Your Deadline

Whether your deadline is April 2026 or April 2027, waiting until the last month is a risk. WCAG remediation typically takes 2–6 months for a complex site. Here is a practical sequence:

  1. 1
    Run an automated scan

    Automated tools catch 30–40% of WCAG violations quickly. Start with AccessCheckup or another axe-core-based scanner to get a baseline.

  2. 2
    Prioritize by impact

    Fix critical issues first — missing form labels, images without alt text, keyboard traps, and insufficient color contrast affect the most users.

  3. 3
    Commission a manual audit for high-traffic pages

    Automated tools cannot catch all issues. A human tester with assistive technology is needed for full WCAG 2.1 AA conformance.

  4. 4
    Write or update your accessibility statement

    Document your conformance status, known issues, and a contact method for users who encounter barriers.

  5. 5
    Establish an ongoing testing process

    Accessibility regresses with every new feature. Build automated scanning into your deployment pipeline.

Frequently Asked Questions

What is the DOJ's Title II web rule?

The DOJ issued a final rule in 2024 under Title II of the Americans with Disabilities Act (ADA) that requires state and local government entities to make their websites and mobile apps conform to WCAG 2.1 Level AA. The rule was published in the Federal Register on April 24, 2024.

Who must comply with the Title II web rule?

All state and local government entities covered by Title II of the ADA must comply. This includes state agencies, county and city governments, school districts, public colleges and universities, public libraries, transit authorities, and other public bodies.

What are the compliance deadlines?

Larger public entities (those serving a population of 50,000 or more) must comply by April 24, 2026. Smaller public entities (those serving fewer than 50,000 people) and special district governments have until April 26, 2027.

What does WCAG 2.1 Level AA require?

WCAG 2.1 Level AA is the W3C's Web Content Accessibility Guidelines standard. It requires that web content be Perceivable, Operable, Understandable, and Robust (POUR). Key requirements include: text alternatives for images, captions for video, sufficient color contrast (at least 4.5:1 for normal text), keyboard navigation, accessible form labels, and no content that flashes more than three times per second.

Are there any exceptions to the Title II web rule?

Yes, the rule includes limited exceptions. Archived web content that has not been changed since the compliance date, preexisting conventional electronic documents (PDFs, Word files) that are not used to apply for government services, content posted by third parties not under contract with the government, and certain other categories may be exempt. However, new content and content used to access government services must comply.

Sources & Further Reading

See where your site stands

Run a free automated scan and get a plain-English report of your top WCAG issues. Know what to fix before your deadline.

Run a free scan →

Related Guides