Checklist: ADA Title II web and mobile accessibility for state and local governments
Twelve steps for a state or local government’s ADA coordinator, web team and procurement office before the April 26, 2027 and April 26, 2028 compliance dates in 28 CFR part 35 subpart H, each tied to the rule or to the Justice Department’s compliance guide.
Who this is for
State and local governments, and their departments, school districts and special districts, that offer services, programs or activities through websites, documents and mobile apps. Subpart H of 28 CFR part 35 requires their web content and mobile apps to meet WCAG 2.1 Level A and AA. The Justice Department’s interim final rule of April 20, 2026 moved the dates: April 26, 2027 for entities with a total population of 50,000 or more, and April 26, 2028 for smaller entities and all special district governments [1] [3]. The interim rule invited comments until June 22, 2026; the dates above are those in the eCFR as checked on November 14, 2026 [1] [3]. What the rule asks for is set out in our explainer.
How the steps are built
Each step says what to do, who usually owns it, and the section of the rule or the part of the Department’s Small Entity Compliance Guide [4] behind it. Many of the guide’s planning practices are suggestions, and the steps label them as good practice. The interim rule also notes that, whatever the compliance dates, covered entities keep their existing Title II obligations for services offered online [3]. This checklist explains the rule; it is not legal advice.
The checklist
Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.
ADA coordinator with counsel
Section 35.200(b) sets April 26, 2027 for entities other than special districts with a total population of 50,000 or more, and April 26, 2028 for smaller entities and special district governments [1]. Section 35.104 defines total population by the most recent decennial Census, or for an independent school district the Census Bureau’s Small Area Income and Poverty Estimates [2]. The guide explains how parts of a larger government, such as a city library, use the parent’s population [4].
Web and digital services lead
Section 35.200(a) covers web content and mobile apps the entity provides “directly or through contractual, licensing, or other arrangements” [1]. The guide confirms that content a contractor or vendor provides or posts for the government is covered [4]. The inventory itself is our suggestion.
ADA coordinator with records management
Section 35.201 excepts archived web content, preexisting conventional electronic documents, content posted by third parties not acting for the entity, individualized secured documents, and preexisting social media posts [1]. Archived content must have been created before the compliance date (or reproduce paper or other physical media from before it), be kept only for reference, research or recordkeeping, be unaltered since archiving, and sit in an area clearly marked as archived [2].
Department content owners
The exception for preexisting documents does not cover documents currently used to apply for, gain access to, or participate in the entity’s services, programs or activities [1]. The guide adds that a preexisting document updated after the compliance date loses the exception [4]. Putting these first is our suggestion.
Head of the entity or designee, with counsel
Section 35.204 puts the burden of proof on the entity, requires the decision to be made by the head or a designee after considering all resources available for the program, with a written statement, and still requires other action that ensures access to the maximum extent possible [1].
ADA coordinator
Section 35.205 deems an entity compliant only where it can show that nonconformance does not affect people’s ability to get the same information, interactions, transactions and services with substantially equivalent timeliness, privacy, independence and ease of use [1]. The guide says this provision cannot be used to avoid trying to meet WCAG 2.1 Level AA [4].
ADA coordinator
Section 35.107 requires an entity with 50 or more employees to designate a responsible employee, make their name, office address and telephone number available to all interested individuals, and adopt and publish grievance procedures [6]. The request and reporting channels are good practice from the guide [4].
ADA coordinator with communications
The guide suggests policies that name a coordinator, set out how content is tested and how requests for excepted content are handled, and training for developers, content authors and procurement staff. It presents these as planning practices, not requirements [4].
Department service managers
The guide says that where a person with a disability cannot use content that meets WCAG 2.1 Level AA, the government must still meet its other ADA obligations, such as effective communication and reasonable modifications, and gives the example of selling a fair ticket another way [4].
Spotted an error? Tell us and we will check it and correct the checklist where needed.