Back to resources

Resource article

What the ADA Title II web and mobile accessibility changes require

A practical breakdown of the Title II final rule, WCAG 2.1 AA expectations, and what public entities should do now.

Last updated: 5/11/2026

Direct answer

The DOJ's Title II final rule sets WCAG 2.1 AA as the technical standard for state and local government web and mobile content, with phased compliance dates based on entity size.[1][2][3]

What this means in practice

  • The DOJ finalized a Title II rule covering web content and mobile apps for state and local governments.[1][2]

  • The rule uses WCAG 2.1 Level AA as the technical conformance standard.[1][3]

  • Compliance timing is phased by population threshold, with separate timelines for larger and smaller public entities.[2][3]

  • Public entities should inventory digital assets, assign ownership, and create a remediation program before deadlines.[2]

FAQ

Does the rule apply only to websites?

No. DOJ guidance and the final rule framework cover both websites and mobile applications used to deliver public services.[1][2]

Is WCAG 2.1 AA optional?

For Title II web/mobile compliance under this rule, WCAG 2.1 AA is the baseline technical standard identified by DOJ.[1][3]

Annotated sources

  1. [1] Federal Register: DOJ final Title II web/mobile rule

    Federal Register / DOJ | 2024-04-24

    Primary rule text that defines scope, standard, and implementation framework for Title II web/mobile accessibility.

  2. [2] ADA.gov first steps for Title II web/mobile rule

    ADA.gov | Living guidance page

    Operational checklist for public entities preparing implementation and governance programs.

  3. [3] ADA.gov small entity compliance guide

    ADA.gov | Living guidance page

    Plain-language summary of obligations, timelines, and exceptions for smaller public entities.

This article is informational and not legal advice. Organizations should consult counsel for legal determinations.