Skip to main content
a promotional graphic telling you that PCI Compliance is no longer an annual exercise and that continuous monitory must be built in
Title II Deadlines Move. The Access Duty Doesn't.Laws and Regulations
5 min readFor Legal Counsel

Title II Deadlines Move. The Access Duty Doesn't.

Scope: what this guide covers

A moved deadline can change your compliance calendar, but it doesn't erase your entity's existing duty to provide access. This guide is for counsel advising state and local government entities, including public schools and universities, on web and mobile accessibility under ADA Title II. It separates two things that often get blurred: the standing legal duty to provide access, and the timetable and technical detail of the DOJ Final Rule (2024). Use it when leadership asks whether a delay, extension, or pending lawsuit changes what the entity must do today.

Short answer: it changes your compliance calendar. It doesn't change your obligation.

Key concepts and definitions

The underlying duty. Title II provides that no qualified individual with a disability shall, by reason of disability, be excluded from participation in, or denied the benefits of, the services, programs, or activities of a public entity, or be subjected to discrimination by that entity (42 U.S.C. 12132). That duty predates any web-specific regulation.

The technical regulation. The DOJ Final Rule (2024) became effective June 24, 2024. DOJ described the rulemaking as providing technical standards to assist public entities in complying with their existing obligations. It clarifies how to meet the duty. It does not create the duty. For counsel, that distinction means a change to the rule's timetable doesn't, by itself, resolve whether a service is accessible today.

Implementation timing. The effective date and compliance date are different things. The implementation timeline for the web and mobile standards Web Accessibility Specialist extended, and a lawsuit challenging that extension remained pending as of November 10, 2026. The National Federation of the Blind has moved for summary judgment, asking the court to rule that the extension violated the law. Treat the outcome as unknown.

The technical reference. WCAG is the widely accepted standard that DOJ itself uses and recommends. It's the concrete benchmark your team can point to.

Requirements breakdown

Sort your obligations into three layers. Each has a different stability profile.

  1. Stable: the nondiscrimination duty. Title II's access requirement is in force now. DOJ enforcement against public entities over website access goes back well before the 2024 rule. DOJ published guidance on accessibility of state and local government websites in 2003, and it negotiated web access settlements with counties in the years that followed.
  2. Settled but contested in timing: the DOJ Final Rule (2024). The rule is final. Its implementation schedule is the variable under challenge.
  3. Reference layer: WCAG. Your plan should name a specific WCAG version and conformance level as the target, so expectations are measurable regardless of how the rule's calendar moves.

History is a useful warning here. DOJ's 2010 advance notice of proposed rulemaking covered web accessibility for public and private entities, and three of the four regulations proposed that day were never finalized. Rulemaking can stall for years. Entities that waited on it were exposed the whole time.

Implementation guidance

Explaining the distinction to leadership. Use one sentence: "The regulation tells us how DOJ expects us to prove access; the ADA already requires the access." Then give an analogy leadership will recognize. A plumbing code is specific and testable, but the duty to provide safe plumbing doesn't begin the day the code is adopted.

Build a plan that survives deadline changes. Your accessibility plan should keep requiring the following, no matter what a court or agency does to the schedule:

  • A named conformance target (WCAG version and level) adopted by policy, not by reference to a regulatory date.
  • An inventory of public-facing web content, mobile applications, and third-party platforms that deliver services or programs.
  • Conformance testing that combines automated scanning with manual checks and screen reader testing.
  • A remediation backlog with owners, priorities, and dates set internally.
  • A documented process for receiving and resolving accessibility complaints.
  • Accessible procurement language so new purchases don't add to the backlog.
  • Records showing progress, since a defensible baseline is one you can demonstrate.

Use dates as internal commitments. Set remediation milestones your entity controls. If the regulatory date moves later, keep yours. If it moves earlier or is reinstated, you're already positioned.

Monitor the litigation, don't wait on it. Assign someone to track the pending challenge and brief leadership when the court rules. Draft two short decision memos in advance, one for each outcome, so a ruling triggers a review rather than a scramble.

Common pitfalls

  • Treating delay as permission. An extension may adjust when the rule's specific requirements apply. It doesn't excuse an inaccessible public service today.
  • Citing the rule as the source of the duty. If your policy says "we comply by [date] per the rule," a date change can unravel the policy. Anchor it to Title II and the WCAG target instead.
  • Leaving the standard unnamed. "We make accessibility a priority" gives your team nothing to measure. Name the version and level.
  • Scoping to websites only. The rule addresses web and mobile applications. Inventory both.
  • Forgetting vendors. Content and services delivered through third-party platforms are still your program. Contract for conformance and request an Accessibility Conformance Report.
  • Undocumented progress. Work performed but not recorded is hard to defend later.

Quick reference table

Question Answer Anchor
Does Title II already require accessible public services? Yes 42 U.S.C. 12132
What does the DOJ Final Rule (2024) do? Supplies technical standards to help meet existing obligations DOJ Final Rule (2024)
When did the final regulations become effective? June 24, 2024 DOJ Final Rule (2024)
Is implementation timing settled? No; challenge to the extension pending as of November 10, 2026 Summary judgment motion by National Federation of the Blind
What technical benchmark should we adopt? A named WCAG version and level WCAG
Does a delay pause remediation? No ADA Title II duty
What should the plan include regardless of timing? Inventory, testing, backlog, complaint process, procurement, records Accessibility Governance
What should counsel prepare for? Two decision memos tied to possible court outcomes Litigation monitoring

Keep this table with your accessibility governance documentation. When the next extension, ruling, or amendment arrives, the question to ask is not "do we still have to?" It's "does our baseline still hold?"

Promotional banner for the CUI buildout guide

You Might Also Like