The ADA Title II web and mobile accessibility rule (28 CFR part 35, subpart H), explained
The Justice Department’s 2024 rule requires state and local governments to make their web content and mobile apps meet WCAG 2.1 Level AA. An interim final rule effective April 20, 2026 moved the compliance dates to April 26, 2027 and April 26, 2028.
The rule and the delay
Title II of the Americans with Disabilities Act covers the services, programs and activities of state and local governments. On April 24, 2024, the Department of Justice published a final rule adding technical requirements for the web content and mobile apps those governments provide. It took effect on June 24, 2024, but set later dates by which entities had to comply [1].
On April 20, 2026, shortly before the first of those dates, the Department published an interim final rule, effective the same day, that extends both compliance dates by one year and does not alter the substantive requirements of the 2024 rule [1]. The Department cited correspondence it received through OMB’s 2025 request for deregulation ideas, including from higher education associations and the Small Business Administration’s Office of Advocacy, describing the resources and staff time compliance demands. It also pointed to uncertainty about what the rule requires and to litigation risk if the dates arrived before entities were ready. It took comments until June 22, 2026 [1].
Who is covered
The rule covers public entities under Title II. The Department’s fact sheet lists examples: state and local offices that provide benefits and social services, public schools, community colleges and universities, police departments, courts, elections offices, public hospitals and clinics, parks and recreation programs, libraries and transit agencies. It also names special purpose districts, Amtrak and commuter authorities [3].
The requirement reaches web content and mobile apps the entity provides or makes available directly or through contractual, licensing or other arrangements [2]. In our reading, that reaches a city portal built by a vendor, a payment page run by a processor or a library app licensed from a supplier, which puts the requirement into contracts and procurement as well as web teams’ work.
The standard: WCAG 2.1 Level AA
Section 35.200 requires covered web content and mobile apps to meet the Level A and Level AA success criteria and conformance requirements of the Web Content Accessibility Guidelines version 2.1, published in June 2018 and incorporated by reference [1] [2]. Three further sections shape how that applies [2]:
- Conforming alternate versions (section 35.202) may be used only where technical or legal limits make it impossible to make the content itself accessible.
- Equivalent facilitation (section 35.203) allows other designs or methods that give substantially equivalent or greater accessibility and usability.
- Duties (section 35.204): where full compliance would fundamentally alter a service, program or activity, or impose undue financial and administrative burdens, the entity must still comply up to that point.
The new compliance dates
Section 35.200(b), as amended by the interim final rule, now reads [1] [2]:
- April 26, 2027: a public entity with a total population of 50,000 or more, other than a special district government. The original date was April 24, 2026.
- April 26, 2028: a public entity with a total population under 50,000, and any special district government. The original date was April 26, 2027.
The Department stated that, regardless of these dates, covered entities keep their existing Title II obligation to make services offered online accessible. It said it plans future rulemaking on the substance of the 2024 rule and will consider issuing a proposed rule during the extension; if it does not, and circumstances suggesting further delay do not exist, it fully anticipates implementing the rule at the new dates [1].
A parallel change affects many of the same organizations. The Department of Health and Human Services, by an interim final rule effective May 7, 2026, extended the web and mobile app compliance dates in its section 504 rule for recipients of its financial assistance: to May 11, 2027 for recipients with 15 or more employees, and May 10, 2028 for those with fewer [4]. In our reading, a public hospital or health department that receives HHS funding may be subject to both.
Five exceptions and the minimal-impact test
Section 35.201 excludes five kinds of content from the WCAG requirement [2]:
- Archived web content, as defined in section 35.104. The fact sheet explains that the content must have been created before the compliance date (or reproduce older physical media), be kept only for reference, research or recordkeeping, sit in an area set aside for archived content, and be unchanged since it was archived [3].
- Conventional electronic documents posted before the compliance date, unless they are still used to apply for, gain access to or take part in a service, program or activity.
- Content posted by a third party, unless the third party posts it under a contractual, licensing or other arrangement with the entity.
- Individualized documents about a specific person, their property or their account that are password-protected or otherwise secured.
- Social media posts made before the compliance date.
Under section 35.205, an entity that does not fully conform is treated as compliant only if it can show the gap has so little effect that people with disabilities can still get the same information, carry out the same interactions and transactions, and take part in the same services with substantially equivalent timeliness, privacy, independence and ease of use [2]. The fact sheet gives a color contrast ratio of 4.45:1 against the required 4.5:1 as a likely example, and says entities cannot use this provision to avoid trying to meet WCAG 2.1 [3].
What the extra year buys
The extension moves dates, not requirements [1]. Documents posted before the compliance date are excepted unless they are currently used to apply for, gain access to or take part in a service [2], so older documents still used that way are covered whichever compliance date applies. In our view, the larger decision is contractual: contracts signed now for portals, payment systems and apps will often run past April 2027 or April 2028, and the accessibility terms written into them will shape whether the entity can meet the rule on time.
Status as checked on November 14, 2026: the eCFR shows the amended dates as of November 12, 2026. This page explains the rule and is not legal advice; whether a particular entity, document or app is covered, and whether a defense applies, depend on facts that counsel should review.
Moraph’s teams help organizations with work like this: see our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.