ADA compliance video captions

Federal ADA Title II Digital Accessibility: What’s Required Now

A Deadline That Applies Regardless of Which State You're In

The Department of Justice’s Title II rule on web and mobile app accessibility requires state and local governments, including special districts, to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, for their web content and mobile apps, which includes the video and web presence of public meetings.

In April 2026, DOJ issued an interim final rule extending the timeline. As of the current compliance schedule, governments with a population of 50,000 or more have until April 26, 2027. Governments under 50,000 residents, and any special district government regardless of size, have until April 26, 2028.

This one isn’t state-specific, and the deadline recently moved, which means a lot of offices are now working from outdated information. The Department of Justice’s Title II digital accessibility rule sets a real, specific standard, WCAG 2.1, Level AA, for public meeting video and web content, with a compliance date of April 26, 2027 for larger governments and April 26, 2028 for smaller ones and special districts. Auto-captions of the kind a video platform generates on its own often don’t clear that bar. Here’s what actually does.

What WCAG 2.1, Level AA Actually Requires for Meeting Video

Here’s the detail that catches offices off guard. WCAG 2.1, Level AA, includes a specific requirement that prerecorded video have accurate captions, and captions generated automatically by a general video platform, the kind that transcribes speech without any customization, often fall short of that standard in practice. A caption track that consistently misspells a council member’s name or mangles a local place name isn’t just an embarrassing detail. Under this standard, inaccurate captions are a real accessibility gap, not a cosmetic one.

The Requirement Most Agencies Haven’t Heard Of: Audio Description


This is the piece that took even seasoned professionals a while to fully understand, so don’t feel behind if it’s new to you. WCAG 2.1, Level AA also includes a requirement for audio description of prerecorded video, essentially a narrated voiceover describing meaningful visual content for residents who can’t see it. When a presentation, slide, or other visual content appears during a meeting video, an audio description track needs to convey that same information audibly. If your meeting videos include presentations, and most do, this applies to you.

In practice, this means the audio description track needs to find natural pauses in the meeting audio and narrate what’s currently being shown, a presentation is now on screen, for example, so residents relying on audio alone still get the full picture, not just the spoken portion of the meeting.

Why This Matters Beyond Compliance

It’s easy to file this under legal risk and move on, and the risk is real. But there’s a more direct way to think about it: residents who are blind, low-vision, or Deaf and hard of hearing are part of the public your meetings are legally required to serve, and captions or video that fall short of WCAG 2.1, Level AA leave real gaps in what those residents can actually access. This requirement exists because those gaps were genuinely excluding people from public participation, not because of an abstract legal technicality.

What Compliant Video Looks Like


A meeting video built to meet this standard includes accurate captions so names and local terms come through correctly, along with an audio description track for any meaningful visual content shown during the meeting. Both should be part of how your meeting video is produced by default, not a separate, optional step someone has to remember to add later.

Closing the Gap on Historical Video Too


This requirement doesn’t apply retroactively to your entire archive. DOJ’s rule includes specific exceptions for certain preexisting content, but city council meeting minutes and video created after your compliance date generally don’t qualify for those exceptions, even if they’re later moved into an archive section of your site. For agencies with a back catalog of older meeting video without proper captions or audio description, retroactive processing of historical video is possible, which matters for anything in your active, ongoing public record.

What to Ask About Your Current Setup


A question worth answering honestly: if a Deaf resident pulled up last month’s meeting video right now, would the captions accurately reflect what was actually said, including names? And if a resident who is blind listened to that same video, would they understand what was shown on screen during the presentation portions? If either answer is uncertain, that’s worth addressing well before your applicable 2027 or 2028 deadline, not the week it arrives.

Where to Go From Here

This pairs directly with California SB 707 and what city clerks need to know, since both requirements are pushing public meeting accessibility in the same direction at the same time, one at the state level, one at the federal level. For the full, current compliance timeline and technical requirements, ADA.gov’s official fact sheet is the authoritative source, and it’s worth bookmarking directly since this rule has already changed once.

Want a straight answer on where your current meeting video stands against this standard, and how much runway you actually have? Request a demo and bring a recent meeting video with you.

This is a general overview and not legal advice. Deadlines and applicability under this federal rule depend on your entity’s population and specific circumstances, and the compliance schedule has already been revised once. Consult your legal counsel and ADA.gov directly for guidance specific to your jurisdiction.