ADA Title II web accessibility deadline for small governments

In 2024 the U.S. Department of Justice adopted a rule setting a specific accessibility standard for state and local government websites and mobile apps. In April 2026 it pushed the compliance dates back a year. For a small town, township, or special district, that means more time, but not a different finish line. This article covers what the rule requires, the current dates, and what it means for the documents and video clerks post every month.

This is general information, not legal advice.

The rule in brief

The rule, under Title II of the Americans with Disabilities Act, requires state and local governments to make their web content and mobile apps conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA (ADA.gov fact sheet). WCAG is a technical standard published by the W3C. It covers things like text alternatives for images, captions for video, keyboard navigation, color contrast, and documents that screen readers can read.

Using a vendor doesn't shift the obligation. ADA.gov is plain about this: your entity "is still responsible for ensuring the accessibility of its web content and mobile apps, even if it outsources the accessibility work to somebody else" (ADA.gov first steps).

The current compliance dates

On April 20, 2026, DOJ published an interim final rule, effective immediately, extending the original deadlines by about a year (DOJ interim final rule, PDF; Federal Register):

Population is based on 2020 Census data, not on staff size or the number of people you serve (ADA.gov first steps). ADA.gov's small entity compliance guide explains how to determine which date applies to your entity.

The technical standard did not change. The extension only moved the dates.

The uncertainty

A few things are still unsettled as of this writing:

• It's an interim rule. DOJ took public comments through June 22, 2026. A final rule could keep, change, or further revise the dates.
• It's being challenged. On May 27, 2026, the National Federation of the Blind filed suit in federal court in Maryland challenging the extension (Law Office of Lainey Feingold). If a court sets the interim rule aside, the original dates could come back into play.
• Title II itself still applies. The ADA's general obligation to communicate effectively with people with disabilities existed before this rule and hasn't been paused. People can still request accommodations and file complaints.
• Other federal rules may apply. Entities that receive certain federal funds may have separate obligations. For example, HHS's 2024 Section 504 rule set its own web accessibility dates, starting May 11, 2026, for recipients of HHS funding; the DOJ extension does not by itself change those (Jackson Lewis).

The practical reading: plan to April 26, 2028 if you're a small government or special district, but don't treat that date as a reason to wait. Anything you fix now is content you won't need to fix later.

What it means for meeting documents

Agendas and minutes

If your agendas and minutes are posted as web pages, they need to meet WCAG 2.1 AA like the rest of your site: real headings, lists, readable contrast, and link text that makes sense out of context.

If they are posted as PDFs, the PDFs need to be accessible too. That means tagged PDFs with a logical reading order, real text rather than a scanned image, alternative text for any images, and a document title and language set. A scanned, signed agenda with no text layer is the most common problem.

A practical fix many clerks use is to post the agenda and minutes as HTML pages and attach the PDF as a secondary copy.

Packets

Meeting packets are often the hardest part: dozens of pages assembled from engineers' reports, site plans, bids, and letters from other agencies. Each item you post after your compliance date is covered. Start by asking the people who send you documents to send the original Word or PDF file rather than a scan, and make sure your own templates produce tagged PDFs.

The exceptions that matter to clerks

The rule has five exceptions (ADA.gov fact sheet). Two matter most for meeting records:

• Archived web content. Content qualifies only if all four conditions are met: it was created before your compliance date (or reproduces older paper or physical media), it's kept only for reference, research, or recordkeeping, it's stored in a clearly designated archive area, and it hasn't been changed since it was archived. ADA.gov notes that "city council meeting minutes created after the date the city must comply" would not qualify (small entity guide).
• Preexisting conventional electronic documents. PDFs, word-processing files, presentations, and spreadsheets posted before your compliance date are exempt, unless they're still used to access your services, programs, or activities.

So old minutes in a clearly labeled archive can generally stay as they are. Minutes from meetings after your compliance date need to be accessible. A current application form posted years ago does not get a pass.

Meeting video and captions

WCAG 2.1 AA includes two captioning requirements:

• Recorded video: captions for all prerecorded audio in synchronized media (WCAG 1.2.2).
• Live video: captions for all live audio in synchronized media (WCAG 1.2.4).

For a board that livestreams and then posts the recording, that means real-time captions during the stream and synchronized captions on the recording.

Two notes on YouTube, which many small bodies use:

• Your channel counts. The social media exception covers only posts made before your compliance date; posts made after it must meet WCAG 2.1 AA (ADA.gov first steps).
• Automatic captions need review. YouTube offers automatic captions, including English-only automatic captions for live streams, but warns they "might misrepresent the spoken content" and says you "should always review automatic captions and edit any parts that haven't been properly transcribed" (YouTube Help). For recordings, uploading a reviewed caption file (WebVTT or SRT) is the more reliable route.

Captions depend on audio. If members don't use their microphones, no captioning method will be accurate.

A practical checklist

1. Find your date. Confirm your population category and write the date down.
2. Inventory. List where meeting content lives: your website, a vendor portal, YouTube, social media, a document library.
3. Fix templates first. Make your agenda and minutes templates produce accessible HTML or tagged PDFs, so new documents start out compliant.
4. Stop scanning. Post text-based documents and keep signed paper originals on file.
5. Set up an archive. Move older meeting records into a clearly labeled archive section and leave them unchanged.
6. Caption everything new. Plan for live captions on streams and reviewed caption files on recordings.
7. Ask vendors. Request accessibility documentation and a WCAG 2.1 AA commitment in contracts, as ADA.gov suggests.
8. Publish a contact. Tell people how to request an accessible version of a document and respond promptly.
9. Watch for changes. Check ADA.gov for a final rule or court decisions.

Where CivicPorch fits

CivicPorch publishes agendas and minutes as accessible HTML pages, generates WebVTT and SRT caption files from meeting recordings for you to review, and embeds the video from your own YouTube channel. You can start free with one board.