ADA Title II web accessibility: what small towns must do

Under the Department of Justice's rule for Title II of the Americans with Disabilities Act (ADA), state and local governments must make their websites, mobile apps and digital documents meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. As of September 2026, towns, counties and cities with fewer than 50,000 people, and all special district governments, must comply by April 26, 2028. Larger governments must comply by April 26, 2027.

This article is general information, not legal advice. Check ada.gov for the current rule and dates before you plan.

What is the ADA Title II web accessibility rule?

The Department of Justice published the final rule on April 24, 2024. It sets a technical standard for digital accessibility that Title II had not spelled out before: WCAG 2.1 at Level AA, a set of guidelines from the World Wide Web Consortium.

WCAG 2.1 AA covers things such as text alternatives for images, captions for video, keyboard access to every function, enough color contrast, content that reflows on small screens, clear form labels and error messages, and no content that flashes in a way that could cause seizures.

The rule does not replace a government's existing ADA duties. You must still communicate effectively with people with disabilities and make reasonable modifications, even for content that falls under an exception.

When are the compliance deadlines?

The Department of Justice set the original dates in 2024. On April 20, 2026, it published an interim final rule that extended them by a year. As of September 2026, the dates on the ada.gov fact sheet are:

Population is generally based on 2020 U.S. Census Bureau data, with separate rules for school districts. The extension came through an interim final rule with a public comment period, so check ada.gov again before relying on these dates.

The extra year is time to fix things in order, not a reason to wait. Accessibility work on a site with years of documents takes time.

What does the rule cover?

The rule applies to web content and mobile apps that a state or local government provides or makes available, directly or through contractors, vendors or other arrangements. That includes:

• The main website and any separate sites for departments, parks, libraries or courts.
• Mobile apps, such as for reporting potholes, paying bills or checking transit times.
• Documents posted online: PDFs, Word files, spreadsheets and presentations, including agendas, minutes, permit applications and budgets.
• Third-party platforms you use to deliver services, such as online payment portals, permit and licensing systems, agenda management tools, recreation sign-ups, maps and video streaming of meetings.
• Social media posts made by the government from the compliance date on.

Content a vendor builds or hosts for you is your responsibility. The exception for third-party content covers posts by independent members of the public, not your technology suppliers.

What are the exceptions?

The rule lists five exceptions. Each has conditions that must all be met, set out in the small entity compliance guide:

1. Archived web content. Created before the compliance date (or reproducing older physical media), kept only for reference, research or recordkeeping, stored in an area clearly marked as archived, and not changed since archiving.
2. Preexisting conventional electronic documents. PDFs, word processing files, presentations and spreadsheets available before the compliance date, unless they are currently used to apply for, access or take part in a service, program or activity.
3. Content posted by a third party. Posts by members of the public, such as comments on a forum, when the third party is not acting for the government.
4. Individualized, password-protected documents. Documents about a specific person, property or account, such as a utility bill, when they are secured.
5. Preexisting social media posts. Posts made before the compliance date.

Two further points limit the options. You do not have to take actions that would cause a fundamental alteration or undue burden, but that is decided case by case and you still must provide access some other way. And a separate "conforming alternate version" of inaccessible content is allowed only where a technical or legal limitation prevents the original from being made accessible.

A practical plan for small towns, counties and special districts

ADA.gov's first steps guidance sets out the sequence. Here it is adapted for a small team with a small budget.

1. Name an owner and learn the basics

Pick one person to coordinate, even if part-time. Give them and anyone who posts content short training on accessible documents and web publishing.

2. Inventory what you have

List every website, subdomain, app, third-party portal and document library. Record who owns each and how often it is used. Expect to find more than you thought, including old microsites and vendor portals.

3. Remove, archive or keep

Delete content no one needs. Move true reference material into a clearly labeled archive section that meets the archived content conditions. Everything that remains must meet WCAG 2.1 AA.

4. Fix the template first

Your content management system's theme, navigation, header, footer and forms appear on every page. Fixing them once improves the whole site. If your site uses a vendor theme, ask the vendor for its accessibility conformance report and a fix date.

5. Prioritize by use and by service

Start with what people need to reach a service: paying bills, applying for permits, registering for programs, finding meeting agendas, and emergency information. Then high-traffic pages. Then everything else.

6. Change how documents are made

New PDFs are a common source of new accessibility problems. Publish information as web pages where possible. When a PDF is needed, create it from an accessible Word template with headings, alt text and table headers, and check it before posting. Scanned images of text are not accessible.

7. Caption meetings

Recorded council and board meetings need captions. Live-streamed meetings need live captions under WCAG 2.1 AA. Check whether your streaming vendor provides them and at what quality.

8. Write accessibility into every contract

For new purchases and renewals, require WCAG 2.1 AA conformance, a current accessibility conformance report, a commitment to fix defects in a stated time, and the right to test before acceptance.

9. Publish an accessibility statement and a way to report problems

Give residents a named contact, email and phone number to report barriers and request information in another format. Respond promptly and log what you hear.

How to test for WCAG 2.1 AA

Use a mix of methods. ADA.gov notes that automated tools cannot test all aspects of accessibility, so a combination of automated and manual checks is needed.

• Automated scans with free tools such as WAVE or axe catch missing alt text, contrast failures, empty links and missing form labels. Run them on templates and key pages.
• Keyboard testing. Put the mouse away and use Tab, Shift+Tab, Enter and the arrow keys. Every link, menu, form and dialog must work, and you must always see where focus is.
• Zoom and reflow. Zoom to 200 percent and view the site at a narrow width. Content should stay readable without scrolling sideways.
• Screen reader checks. Try key tasks with NVDA on Windows or VoiceOver on Mac and iPhone. Listen for headings, link names and form labels that make sense.
• Document checks. Use the accessibility checker in Word or Adobe Acrobat, then check reading order manually.
• User feedback. Where possible, ask residents who use assistive technology to try key tasks.

How this differs by size

• Small towns and special districts: one site, a vendor template and many PDFs. Focus on the template, service pages, document habits and vendor contracts.
• Growing counties and cities: several departments posting content and many vendor portals. Add publishing standards, training and a regular testing cycle.
• Large governments and states: many systems and apps. Governance, procurement rules and testing built into every release become the main work.

We help public bodies plan and deliver this work; see our public sector page.

Frequently asked questions

Does the ADA Title II web rule apply to a town of 2,000 people?

Yes, if it is a state or local government entity. The rule applies regardless of size; smaller governments have a later compliance date, April 26, 2028 as of September 2026.

Do we have to fix every old PDF on our website?

Not always. Documents posted before the compliance date may be excepted, unless people currently use them to apply for or access a service. Anything used that way, such as a current permit form, must be accessible.

Is our website vendor responsible, or are we?

You are. Content provided through contractors and vendors is covered as if you provided it, so require WCAG 2.1 AA in your contracts and test what you receive.

Is an accessibility overlay or widget enough?

A widget that changes font size or contrast does not by itself make a site meet WCAG 2.1 AA. The underlying code, content and documents still have to meet the standard.

What happens if we miss the deadline?

The Department of Justice enforces Title II, and people can also file complaints or lawsuits. Document your plan and progress, fix high-use services first, and keep working toward full conformance.