Process

ADA Title II Web Accessibility Rule: Dates and Exceptions

By EZUD Published

The Department of Justice rule on web and mobile app accessibility for state and local governments requires those governments to meet WCAG 2.1 Level AA. As of November 2026 the compliance dates are April 26, 2027 for public entities with a total population of 50,000 or more, and April 26, 2028 for entities under 50,000 and for special district governments. The original dates, April 24, 2026 and April 26, 2027, were pushed back one year by an interim final rule published April 20, 2026. The National Federation of the Blind has sued to have that extension vacated; as of November 2026 the case is pending and the regulation still carries the 2027 and 2028 dates.

Quick facts

ItemCurrent answer (as of November 2026)
RuleSubpart H of 28 CFR part 35 (the Title II ADA regulation), sections 35.200 to 35.205
Original publication89 FR 31320, April 24, 2024; effective June 24, 2024
Who is coveredState and local government entities (“public entities”)
What is coveredWeb content and mobile apps a public entity provides or makes available, directly or through contracts, licensing or other arrangements
Technical standardWCAG 2.1, Level A and Level AA success criteria and conformance requirements
Compliance datesApril 26, 2027 (50,000 or more); April 26, 2028 (under 50,000 and special districts)
Date changeInterim final rule, 91 FR 20902, April 20, 2026, effective immediately
Legal challengeNational Federation of the Blind v. Department of Justice, No. 1:26-cv-02007 (D. Md.), filed May 21, 2026; pending as of November 2026

Sources for each row: the 2024 final rule, the current eCFR text of 28 CFR 35.200, the 2026 interim final rule and the case record at the Civil Rights Litigation Clearinghouse.

What the 2024 DOJ web accessibility rule does

The rule was published in the Federal Register on April 24, 2024 (89 FR 31320) and added a new subpart H to 28 CFR part 35. Section 35.200(a) says a public entity must ensure that web content and mobile apps it provides or makes available, directly or through contractual, licensing or other arrangements, are readily accessible to and usable by people with disabilities.

The “through contracts” language matters. DOJ’s fact sheet gives two examples: a county web page listing park addresses and hours must meet the standard even if an outside design company built and maintains it, and a city’s parking-payment app must meet it even if a private company runs it.

Section 35.104 defines web content as the information and sensory experience communicated to a user by a user agent, including the code or markup that defines structure, presentation and interactions. Examples in the definition are text, images, sounds, videos, controls, animations and conventional electronic documents. Mobile apps are software applications that are downloaded and designed to run on mobile devices such as smartphones and tablets.

Title II duties for websites and apps predate the rule. The 2024 preamble states that public entities were already required to ensure that services offered via the web or mobile apps meet the ADA (89 FR 31357), and the 2026 interim final rule repeats that covered entities have an ongoing Title II obligation regardless of the compliance dates (91 FR 20908).

Who is covered

Covered entities are public entities under Title II: state and local governments, their departments, agencies, special purpose districts and other instrumentalities, plus commuter authorities and Amtrak (§ 35.104). Which compliance date applies depends on “total population” as defined in § 35.104:

  • A public entity with a population calculated by the Census Bureau in the most recent decennial Census uses that figure.
  • An independent school district (or an instrumentality of one) uses the district’s figure in the Census Bureau’s most recent Small Area Income and Poverty Estimates.
  • Another instrumentality or commuter authority without its own Census figure uses the combined decennial Census population of the state or local governments it is part of.
  • Amtrak uses the population of the United States.
  • A special district government is a separate category: a public entity, other than a county, municipality, township or independent school district, authorized by state law to provide one function or a limited number of designated functions, with enough administrative and fiscal autonomy to qualify as a separate government, and whose population the Census Bureau does not calculate in the decennial Census or the Small Area Income and Poverty Estimates. Special districts always get the later date.

Population is therefore a Census figure; the number of people an entity serves or employs does not count. DOJ’s First Steps guide gives examples: a state university with 40,000 students, part of a state with 6,000,000 people, counts as 6,000,000 and has the April 2027 date; a county library branch serving 3,000 patrons in a county of 70,000 counts as 70,000; and a city police department in a city of 25,000 has until April 2028.

What is the compliance date for Title II in 2026 and beyond?

The 2024 rule set two dates. The interim final rule of April 20, 2026 (AG Order No. 6742-2026, 91 FR 20902) amended § 35.200(b)(1) and (b)(2) to move both back by one year.

Entity typeOriginal date (2024 rule)Current date (after April 20, 2026 interim final rule)
Total population of 50,000 or more (not a special district)April 24, 2026April 26, 2027
Total population under 50,000April 26, 2027April 26, 2028
Any special district governmentApril 26, 2027April 26, 2028

Under the current text, no Title II entity has a web-rule compliance date in 2026. The extension does not change the standard: § 35.200(b) still calls for WCAG 2.1 Level A and AA, and DOJ states that the amendments alter no other provision of the 2024 rule (91 FR 20908).

Why DOJ delayed

The interim final rule explains the delay in its preamble (91 FR 20906 to 20908). DOJ said it had overestimated the capabilities, in staffing or technology, of covered entities; that public entities face resource constraints; that generative AI does not yet reliably automate remediation of inaccessible content at scale; and that the private right of action under Title II exposes entities to litigation, including attorneys’ fees and injunctive relief. It also pointed to uncertainty about what compliance requires when WCAG materials are dynamically linked, and to confusion over course-content exceptions that appeared in the 2023 proposal but not in the final rule.

What happened after publication

  • April 20, 2026: the interim final rule took effect on publication. DOJ relied on good cause to skip prior notice and comment, citing the imminent April 24, 2026 deadline. It said it “will consider issuing an NPRM” on the rule’s substance during the extension period, and that if it issues no such proposal and no circumstances suggest a further delay, it “fully anticipates implementing the regulation at the new deadline” (91 FR 20908).
  • May 11, 2026: the Department of Health and Human Services published its own interim final rule (91 FR 25496, effective May 7, 2026), citing DOJ’s April action. It moved the Section 504 web and app deadlines for recipients of HHS financial assistance to May 11, 2027 (15 or more employees) and May 10, 2028 (fewer than 15). HHS notes that many state and local governments also receive its funding and are subject to its Section 504 rules.
  • May 21, 2026: the National Federation of the Blind sued DOJ and HHS in the U.S. District Court for the District of Maryland (No. 1:26-cv-02007). According to the Civil Rights Litigation Clearinghouse summary, the complaint alleges that both interim final rules skipped required notice and comment and were arbitrary and capricious, and asks the court to vacate them.
  • June 22, 2026: the comment period on DOJ’s interim final rule closed.
  • August 14, 2026: DOJ’s spring 2026 regulatory agenda (91 FR 53016) listed the rule at the final rule stage and said DOJ is considering whether to extend the deadlines and then publish an NPRM “to reconsider whether some of the regulatory provisions imposed by the April 24, 2024 rule could be made less burdensome”; the NPRM date is “To Be Determined”.

As of November 2026, the Federal Register shows no proposed rule, final amendment or further delay of the April 26, 2027 and April 26, 2028 dates. The eCFR text of § 35.200, current to November 13, 2026, carries those dates, and its source note lists only the 2024 rule and the April 2026 amendment. The NFB case is listed as ongoing. A DOJ proposal or a ruling for NFB could change the dates again, and any amendment to the regulation will appear in the Federal Register and the eCFR.

The technical standard: WCAG 2.1 Level AA

Section 35.200(b) requires conformance with Level A and Level AA success criteria and conformance requirements of WCAG 2.1, the W3C Recommendation dated June 5, 2018, incorporated by reference. The 2024 preamble says that where WCAG 2.1 and the rule differ, the standards in the rule prevail (89 FR 31321).

The legal standard is WCAG 2.1. W3C says version 2.2, a Recommendation since October 5, 2023, adds nine success criteria and keeps the 2.0 and 2.1 criteria essentially the same, with one exception: 4.1.1 Parsing is obsolete and removed. Our WCAG 2.2 explainer lists the additions. Content built to 2.2 Level AA can therefore still miss one requirement of the rule: DOJ’s 2024 preamble says conformance to 4.1.1 “is still required by subpart H”, while noting that an entity failing it can rely on the minimal-impact provision in § 35.205 if the failure does not affect use in the ways that section lists (89 FR 31347). An audit report should state the WCAG version it is measured against. A vendor conformance document should name WCAG 2.1 and the edition of the product; the VPAT and ACR guide explains how those reports are structured and what to ask for.

The five exceptions and where they stop

Section 35.201 lists five exceptions. Each has conditions, and each leaves other ADA duties in place. The 2024 preamble says that when someone asks for an accessible version of excepted content, such as archived town meeting minutes, the entity must still respond under its effective-communication obligations in 28 CFR 35.160 (89 FR 31322). DOJ’s fact sheet gives a parallel example: if a person with a hearing disability asks for an archived city video, the city could add captions and share a copy of the captioned file.

SectionExceptionConditions and limits
35.201(a)Archived web contentMust meet all four parts of the § 35.104 definition: created before the compliance date (or reproducing paper documents or other physical media created before it), retained exclusively for reference, research or recordkeeping, not altered or updated after archiving, and organized and stored in a dedicated area clearly identified as archived. Content kept for any other purpose, or edited after archiving, does not qualify; the fact sheet’s examples include council minutes created after the compliance date, even when posted in an archive section.
35.201(b)Preexisting conventional electronic documentsPDFs, word-processor, presentation and spreadsheet files available before the compliance date. Lost if the document is currently used to apply for, gain access to or participate in the entity’s services, programs or activities. A file first posted after the date is not preexisting.
35.201(c)Third-party contentContent posted by a third party is exempt unless it is posted because of a contractual, licensing or other arrangement with the public entity. A member of the public’s post on a town’s online message board is the fact sheet’s example; content posted by the entity’s contractors or vendors, and the message-board platform itself, are not exempt.
35.201(d)Individualized, secured conventional electronic documentsMust be both about a specific individual, property or account and password-protected or otherwise secured. A secured document that is not individualized does not qualify.
35.201(e)Preexisting social media postsPosts made before the compliance date. Posts after the date must conform.

“Conventional electronic documents” means only four file formats: PDF, word-processor, presentation and spreadsheet files. HTML pages are web content subject to the standard. Several exceptions turn on the compliance date, so an entity with the 2027 deadline measures “preexisting” and “before” against April 26, 2027, and an entity with the 2028 deadline measures against April 26, 2028.

Conforming alternate versions, equivalent facilitation and the burden defenses

Conforming alternate versions (§ 35.202)

An entity may use a conforming alternate version, as WCAG 2.1 defines it, only where it is not possible to make the content directly accessible because of technical or legal limitations. DOJ’s fact sheet describes it as an accessible copy that provides the same information and features, and says governments usually should not keep an inaccessible main page next to an accessible one.

Equivalent facilitation (§ 35.203)

Alternative designs, methods or techniques are allowed if they produce substantially equivalent or greater accessibility and usability of the web content or mobile app. DOJ’s fact sheet example: a state parks department would probably be allowed to build a campground-reservation app to a future standard, such as WCAG 3.0, if that standard provides the same or more accessibility and usability than WCAG 2.1 Level AA. The fact sheet adds that the entity must be able to prove it.

Fundamental alteration and undue burden (§§ 35.200(b), 35.204)

Compliance is not required to the extent it would cause a fundamental alteration in the nature of a service, program or activity, or undue financial and administrative burdens. Section 35.204 sets the procedure:

  • The entity bears the burden of proving the defense.
  • The head of the entity or a designee decides, after considering all available resources.
  • The decision must be recorded in a written statement of reasons.
  • The entity must still take any other action that does not trigger the defense so that people with disabilities receive benefits or services to the maximum extent possible.

Minimal impact (§ 35.205)

An entity that is not fully compliant is deemed compliant if it demonstrates the noncompliance has so little impact that people with disabilities can still access the same information, engage in the same interactions, conduct the same transactions and otherwise participate in the same services, with substantially equivalent timeliness, privacy, independence and ease of use. The fact sheet’s example is a color contrast ratio of 4.45:1 where 4.5:1 is required, which may be minimal if the entity can show access is not harder; a renewal form that is harder to complete for a person with a manual dexterity disability would not be.

Compliance checklist mapped to the rule

Each task below is tied to the section of 28 CFR part 35 it comes from. DOJ’s First Steps guide sets out its own 11 action steps, from learning the rule’s requirements to creating policies.

StepTaskRule section
1Find the entity’s total population in Census data, or confirm special district status, and write down the deadline: April 26, 2027 or April 26, 202835.104; 35.200(b)
2Inventory every website, portal, mobile app and vendor-run service the entity provides or makes available, including those run under contracts and licenses35.200(a)
3Set the audit target to WCAG 2.1 Level A and AA; test pages and app screens that carry services such as payments, applications, meetings and emergency information35.200(b)
4Sort documents: label real archives and move them to a dedicated, identified area; mark which PDFs and office files predate the deadline and are not used for services35.201(a), (b)
5Plan to fix or replace any PDF that is used to apply for, gain access to or participate in a service; set a standard for every new document after the deadline35.201(b)
6Review social media: posts made before the deadline are exempt; plan for those after35.201(e)
7Separate third-party content from vendor and contractor content; add accessibility clauses to contracts and ask vendors for WCAG 2.1 AA reports35.201(c); 35.200(a)
8Check password-protected files: exempt only if individualized and secured35.201(d)
9Use a conforming alternate version only where technical or legal limits make direct accessibility impossible35.202
10Document any equivalent-facilitation design and why it matches or exceeds WCAG 2.1 results35.203
11If invoking fundamental alteration or undue burden, route it to the head of the entity or a designee and keep the written statement of reasons; still do everything short of the burden35.204
12Record why any residual failure has minimal impact, and keep a process to supply accessible formats on request35.205; 28 CFR 35.160

Testing topics for step 3 are covered in our guides to color contrast and video captions and audio description.

Sources