ADA Title II Web Accessibility: What It Means for Your Government Website

If you run communications, IT or administration for a city, county, fire district or any other unit of local government, there is a federal rule you need to know about, and the deadline is closer than most people realize.

In April 2024, the Department of Justice published a final rule under Title II of the Americans with Disabilities Act (28 CFR Part 35) that sets specific technical requirements for the accessibility of state and local government web content and mobile apps. This is not a new law. It is a rule clarifying what governments already had to do under the ADA, with a concrete technical standard attached to it for the first time.

I have spent most of my career building websites and digital tools for public safety and local government. I want to walk through what this rule actually requires, because I have seen too many agencies either ignore it or panic about it, and neither reaction is useful. The right reaction is to understand it and start working through it methodically.

Who Is Covered

The rule applies to all state and local governments and their agencies and departments. That is broad by design. It also explicitly covers special purpose districts, which is the part many people miss.

A special purpose district is a government entity created to provide a specific service, often with its own taxing authority and its own board, separate from a city or county's general government. Many fire departments operate exactly this way. If your department is a special district rather than a division inside city or county government, you are still covered. This rule does not carve fire districts out. It names them.

The relevant point for most readers is simple: if you are a unit of local government of any kind, including a special district, this applies to you.

What the Rule Actually Covers

The rule reaches the web content and mobile apps that a government "provides or makes available," including content or apps provided through a contractor, licensing deal or other third-party arrangement. You cannot outsource your way around this. If your website is built and hosted by a vendor, or your registration system runs through a third-party platform, the accessibility obligation still sits with the government entity.

Read that scope language carefully, because this is where a lot of agencies get it wrong. The rule is not limited to your public-facing website. It applies to the web content and mobile apps the government provides or makes available, full stop, and Title II of the ADA covers a public entity's employment and all of its programs and activities, not only the services it offers the general public. In practice that means your internal and employee-facing systems are in scope too: staff intranets, the HR or personnel portal, internal dashboards, scheduling and training tools, and any app your people are required to use to do their jobs. If your organization provides it, it needs to work for an employee or a job applicant with a disability the same way it does for a resident.

One boundary is worth naming so this is not overread. The obligation attaches to what your organization provides or makes available. It does not reach an employee's personal use of unrelated outside websites on their own device or their own time. The question is always whether the government is the one providing the content or the tool.

The Technical Standard: WCAG 2.1 Level AA

The rule adopts a specific, named technical standard: Web Content Accessibility Guidelines (WCAG) Version 2.1, Level AA.

This matters because it replaces a vague obligation to be "accessible" with an actual checklist that developers, content authors and auditors can test against. WCAG 2.1 AA covers things like sufficient color contrast, keyboard navigability for people who cannot use a mouse, text alternatives for images, captions for video, forms that work with screen readers, and page structure that assistive technology can actually parse.

If your website or app meets WCAG 2.1 AA, you are meeting the technical bar this rule sets. That is the standard to hand your web team, your CMS vendor and anyone building forms or portals on your behalf.

The Five Exceptions

The rule includes five specific exceptions, and it is worth knowing them precisely rather than assuming your content qualifies for one:

1. 1Archived web content that is retained only for reference, research or recordkeeping, is not currently used to apply for or access services, and is organized in a way that clearly identifies it as archived.
2. 2Preexisting conventional electronic documents such as PDFs, Word documents and spreadsheets, posted before your compliance deadline, unless they are still being used to apply for or access government services or programs.
3. 3Content posted by a third party that is not posted under contract with, or on behalf of, the government entity.
4. 4Individualized, password-protected documents, such as utility bills or account statements specific to one resident.
5. 5Preexisting social media posts.

Notice what these exceptions do not cover. A PDF permit application that residents still need to submit does not get a pass just because it is old. A form buried behind a login that any resident can create for themselves is not the same as a genuinely individualized document like a bill. These exceptions are narrow on purpose.

The Deadlines Have Already Been Extended Once

The original compliance dates were pushed back by a DOJ Interim Final Rule effective April 20, 2026. Under the current timeline:

• Governments serving a population of 50,000 or more must comply by April 26, 2027.
• Governments serving a population under 50,000, and any special district government, including fire districts, regardless of population, must comply by April 26, 2028.

That second deadline is the one most fire departments and other special districts will fall under, but do not read "2028" as "later problem." Fixing a website's accessibility properly, especially one with years of accumulated PDFs, forms and third-party widgets, takes real time. Departments that start now will finish calmly. Departments that wait until 2027 will be scrambling.

What This Means Beyond the Legal Risk

I want to be direct about enforcement, without inventing numbers I cannot back up: the Department of Justice can enforce this rule directly, and private individuals can and do file ADA complaints and demand letters against government websites that are not accessible. That risk is real and it is worth taking seriously.

But I would rather you think about this the way I do, which is as a community service obligation, not just a compliance exercise. Somewhere in your community, a resident who is blind, deaf, has a motor impairment or processes information differently is trying to find your burn permit rules, report a water main break, register for a CPR class or find out when the next town council meeting is. If your website cannot be navigated with a keyboard or read by a screen reader, you have quietly excluded a member of the public you exist to serve. That should bother you regardless of the legal deadline.

Where to Start

You do not have to solve this in one weekend, and you should not try to. A workable sequence looks like this:

Audit first. Get an honest picture of where your site stands against WCAG 2.1 AA before you start fixing anything. You cannot prioritize what you have not measured.

Fix your templates before your content. If your header, navigation, forms and footer are inaccessible, every page built on top of them inherits the problem. Fixing the template fixes hundreds of pages at once.

Train whoever adds content. Most ongoing accessibility failures come from well-meaning staff uploading a scanned PDF or an image of text without knowing there was a better way. A short training session for anyone who touches the website prevents a steady stream of new violations.

Prioritize what residents actually use. Your homepage, your forms, your emergency information and any page connected to applying for or accessing a service should move to the front of the line, well ahead of an archived newsletter from 2019.

The Department of Justice has published resources that are worth reading directly rather than relying on secondhand summaries, including from me. Start with the DOJ fact sheet on the web accessibility rule, the first steps guide for putting a compliance plan together, and the small entity compliance guide, which was written with smaller governments and special districts specifically in mind.

This rule is going to touch nearly every local government website in the country, including a lot of fire and EMS department sites that were never built with accessibility in mind. Start the audit now. The deadline will arrive faster than the to-do list will shrink.