Two dates. One standard.

The Department of Justice’s 2024 Title II web rule set WCAG 2.1 Level AA as the technical standard for state and local government web content and mobile apps. An April 20, 2026 Interim Final Rule moved the original dates by one year. The current dates, as published on ADA.gov’s fact sheet, are:

WhoCompliance date
Public entities serving a total population of 50,000 or moreApril 26, 2027
Public entities serving fewer than 50,000, and all special district governmentsApril 26, 2028

School districts are not special districts. A city school district uses the city’s population; a county district uses the county’s; an independent district uses the Small Area Income and Poverty Estimates figure ADA.gov names.

Many explainer posts still list 2026, the original large-entity date.

After your date, meeting video you provide or make available on the web generally must meet WCAG 2.1 AA — including video you host on YouTube or another platform you use to deliver the meeting.

What WCAG 2.1 AA actually requires of a meeting recording

For synchronized media (picture plus sound), clerks hit guideline 1.2 most often.

CriterionLevelWhat it means for a meeting
1.2.1 Audio-only / video-onlyAA text alternative when there is only audio or only video.
1.2.2AAccurate, synchronized captions on the file you post.
1.2.3 Audio description or media alternativeADescription or a full text alternative.
1.2.4AAReal-time captions on the livestream.
1.2.5AADescription of important visuals on the posted recording.

A clerk’s checklist covers what to inspect before you publish.

Live captions and the file you post are two different jobs

Most clerks livestream, then post a cleaned recording. Those are two success criteria.

Live captions are a starting point, not a finished 1.2.2 track. Names, motions, and ordinance numbers guessed in real time still have to be right on the public record. Aware Lens is built for that second pass.

YouTube and Zoom auto-captions do not close 1.2.2

W3C’s Understanding document for 1.2.2 is about captions that convey the audio track — dialogue, who is speaking, and meaningful non-speech sound — synchronized with the picture. Platform auto-captions are a speech-to-text guess. On a council or board meeting they routinely miss the things that make the recording a record: names, the text of a motion, an ordinance number, a roll-call vote.

Section 508 guidance is direct on the same point: do not rely solely on auto-captioning for prerecorded media.

Keeping YouTube or Zoom as the place you host the file is fine. Treating their auto-captions as the accessibility program is not.

Supporting page: Why YouTube auto-captions fail WCAG 1.2.2.

Audio description: talking-head dais vs. the budget on screen

WCAG 1.2.5 requires audio description for prerecorded synchronized video. W3C is also explicit that if the important information on screen is already in the soundtrack, no extra narration is needed.

  • A talking-head dais — members at microphones, the vote spoken aloud — often needs little or no additional description.
  • A screen-shared budget, map, slide deck, GIS layer, or chart usually does. A resident who cannot see the screen cannot follow an “as you can see on the slide” vote.

Aware Lens generates audio description for the posted recording, with emphasis on the on-screen materials that speech does not cover — not a second voice narrating every nod on the dais.

Supporting page: Audio description for government meetings.

Archived meetings: four tests, not a blanket pass

ADA.gov’s fact sheet carves out archived web content only when all four of the following are true:

  1. The content was created before your compliance date (or reproduces older physical media from before that date), and
  2. It is kept only for reference, research, or recordkeeping, and
  3. It is kept in a special area for archived content, and
  4. It has not been changed since it was archived.

Miss any one point and the exception generally does not apply.

  • A recording that still sits on your current meetings page is generally not “kept only for recordkeeping” in a designated archive.
  • Title II’s separate effective communication duty still applies: if a resident with a disability asks for access, you still need a way to provide it. ADA.gov’s own example is captioning an archived city video on request.

Aware Lens can bulk-import a channel or playlist so you can remediate what has to conform — and have a captioned, described copy ready if a request comes in for what might be excepted.

What Aware Lens returns from a meeting you already recorded

One import. The pieces of a WCAG 2.1 AA meeting record, plus the civic layer residents actually use.

  • Reviewed captions. Speaker labels, names, motions, and punctuation — the accuracy 1.2.2 is asking for, not the raw auto-transcript.
  • Audio description. Narration of on-screen materials — slides, exhibits, maps.
  • Searchable transcript. Time-synced text. Residents jump to an agenda item.
  • Searchable documents. Agendas, packets, and exhibits are OCR’d — residents search to the exact page, even text buried in a scan or a chart.
  • Plain-language summaries. A three-hour hearing becomes a short recap of what was decided, voted, and deferred.
  • Ask Aware Lens. A plain-English question against the meetings and documents you have published, answered with a citation to the moment or the page.

You can keep publishing to YouTube. Connect the account and Aware Lens can push reviewed captions back to those videos; residents use the Aware portal for the full record. Export captions, transcripts, and audio description anytime. Hosting is on enterprise platforms with U.S. data residency.

How clerks actually run it

  1. Import the source. Paste a YouTube link, connect Zoom, drop an MP4, or point at a channel to backfill.
  2. Review the output. Captions, description, transcript, and summary come back for clerk review. Names & Places lets you correct a local name once and propagate it.
  3. Publish, then stop babysitting. Embed the accessible player or sync back to your site. New meetings can flow in automatically.

Most agencies go live in days.

Sources

Product explanation, not legal advice. Confirm 28 C.F.R. Part 35 and current ADA.gov materials before you rely on them.