# 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.

Checklist · Government · Customer & Citizen Experience. Published November 14, 2026. Last reviewed November 14, 2026.

## 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](https://insights.moraph.com/ada-title-ii-web-mobile-accessibility-rule-explained).

## 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

1. **Work out which compliance date applies, using the population figure the rule names, and record how you reached it.** (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].
2. **Inventory every website, web application, document library and mobile app the entity provides, including those run by vendors under contract or license.** (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.
3. **Sort the inventory against the five exceptions, and write down the facts that make each one apply.** (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].
4. **Fix first the forms, PDFs and pages people use to apply for, get, or take part in a service.** (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.
5. **Test content and apps against WCAG 2.1 Level A and AA success criteria, including tests by people with disabilities.** (Web team or accessibility tester) Section 35.200(b) incorporates WCAG 2.1 Level A and AA success criteria and conformance requirements [1] [5]. Testing with people with disabilities is good practice the guide suggests, not a requirement of the rule [4].
6. **Write WCAG 2.1 Level AA into every new or renewed contract for web platforms, apps and content services, and train procurement staff to check it.** (Procurement office) The obligation reaches content provided through contracts and licenses [1]. The guide gives procurement training as an example of good practice [4]. The contract language is our suggestion.
7. **Use a separate accessible version only where a technical or legal limitation stops the main content being made accessible, and document the limitation.** (Web team) Section 35.202 allows conforming alternate versions only where it is not possible to make web content directly accessible due to technical or legal limitations [1]. The guide says a separate accessible version is usually not allowed [4].
8. **Route any claim of fundamental alteration or undue burden to the head of the entity, with all available resources considered and a written statement of reasons.** (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].
9. **Do not plan around the minimal-impact provision; keep it for small, documented gaps that do not change what users can do.** (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].
10. **Publish the ADA coordinator’s contact details and the grievance procedure, and add a clear way to request accessible versions of excepted content and to report problems.** (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].
11. **Adopt a written web and mobile accessibility policy and train everyone who posts content.** (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].
12. **Keep a route for people who still cannot use conforming content, so they receive the service another way.** (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].

## Corrections

- November 14, 2026: Step 10 said section 35.107 requires an entity to publish the responsible employee’s name, office address and telephone number. The rule says to make them available to all interested individuals; the step now says so.

## Sources

1. Office of the Federal Register, eCFR. 28 CFR part 35, subpart H, Web and Mobile Accessibility (eCFR, current as of November 12, 2026). <https://www.ecfr.gov/current/title-28/chapter-I/part-35/subpart-H> Checked November 14, 2026.
2. Office of the Federal Register, eCFR. 28 CFR 35.104, Definitions (eCFR, current as of November 12, 2026). <https://www.ecfr.gov/current/title-28/chapter-I/part-35/subpart-A/section-35.104> Checked November 14, 2026.
3. Department of Justice, Federal Register (via GovInfo). Extension of Compliance Dates for Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities (interim final rule, 91 FR 20902, April 20, 2026). <https://www.govinfo.gov/content/pkg/FR-2026-04-20/html/2026-07663.htm> Checked November 14, 2026.
4. U.S. Department of Justice, ADA.gov. Accessibility of Web Content and Mobile Apps Provided by State and Local Government Entities: A Small Entity Compliance Guide. <https://www.ada.gov/resources/small-entity-compliance-guide/> Checked November 14, 2026.
5. World Wide Web Consortium. Web Content Accessibility Guidelines (WCAG) 2.1, W3C Recommendation, June 5, 2018. <https://www.w3.org/TR/2018/REC-WCAG21-20180605/> Checked November 14, 2026.
6. Office of the Federal Register, eCFR. 28 CFR 35.107, Designation of responsible employee and adoption of grievance procedures (eCFR). <https://www.ecfr.gov/current/title-28/chapter-I/part-35/subpart-A/section-35.107> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-ada-title-ii-web-mobile-accessibility>
Publisher: Moraph Insights
