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:
| Who | Compliance date |
|---|---|
| Public entities serving a total population of 50,000 or more | April 26, 2027 |
| Public entities serving fewer than 50,000, and all special district governments | April 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. That was the original large-entity date. It is not the date on ADA.gov today. The technical standard itself did not change.
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
Title II points at WCAG, not at a brand of captioning. For synchronized media (picture plus sound), clerks hit guideline 1.2 most often. Section508.gov’s synchronized-media page covers the same family of requirements.
| Criterion | Level | What it means for a meeting |
|---|---|---|
| 1.2.1 Audio-only / video-only | A | A text alternative when there is only audio or only video. |
| 1.2.2 | A | Accurate, synchronized captions on the file you post. |
| 1.2.3 Audio description or media alternative | A | Description *or* a full text alternative. |
| 1.2.4 | AA | Real-time captions on the livestream. |
| 1.2.5 | AA | Description of important visuals on the posted recording. |
AA is the level Title II names. A clerk’s checklist covers what to inspect before you publish. Prefer a short gated version? Get the checklist.
Live captions and the file you post are two different jobs
Most clerks livestream, then post a cleaned recording. Those are two success criteria.
- While it is live, WCAG 1.2.4 is about real-time captions on the stream.
- Once you post the file, it is prerecorded. WCAG 1.2.2 applies to that file, and 1.2.5 applies to important visuals that were not spoken.
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: the recording residents will search months later.
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: officials’ and residents’ names, local streets, the text of a motion, an ordinance number, a roll-call vote, who moved, who seconded, and how the vote landed.
Section 508 guidance is direct on the same point: do not rely solely on auto-captioning for prerecorded media. Auto-captions also do not produce audio description, a searchable transcript, or a plain-language summary.
Keeping YouTube or Zoom as the place you *host* the file is fine. Treating their auto-captions as the accessibility program is not. Aware Lens can keep your existing channel in the workflow and return reviewed captions instead of the raw auto track.
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.
That distinction matters for government meetings.
- A talking-head dais — members at microphones, the vote spoken aloud, the motion read into the record — often needs little or no additional description for those stretches, because the speech already says what happened.
- 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. Those visuals are exactly what 1.2.5 is for.
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:
- The content was created before your compliance date (or reproduces older physical media from before that date), and
- It is kept only for reference, research, or recordkeeping, and
- It is kept in a special area for archived content, and
- It has not been changed since it was archived.
Miss any one point and the exception generally does not apply.
What that means for meeting video, without overclaiming:
- A recording that still sits on your current meetings page, in the same list residents use to follow this year’s business, is generally not “kept only for recordkeeping” in a designated archive. The exception usually does not cover it.
- Labeling a folder “archive” is not enough if the video was created after your date, is still used to conduct current business, or has been edited or re-posted.
- A pre-deadline recording that truly lives in a designated archive, unchanged, and is kept only for reference, research, or recordkeeping may qualify. Even then, 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, roll-call graphics — so 1.2.5 is not an empty checkbox.
- Searchable transcript. Time-synced text. Residents jump to an agenda item; you have an indexed public record instead of an unsearchable file.
- 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. A plain-English question against the meetings and documents you have published, answered with a citation to the moment or the page.
- Ask Aware Atlas (optional). The same Q&A extended across 3,800+ U.S. communities plus records in Canada, the UK, Australia, and New Zealand, as currently claimed — every answer cited to an official record.
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. Streaming meetings live? Aware Lens Livestream adds real-time captions during the meeting (WCAG 1.2.4) and records the session into this same accessible archive.
How clerks actually run it
- Import the source. Paste a YouTube link, connect Zoom, drop an MP4, or point at a channel to backfill.
- 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.
- 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. You keep the recorder and channel you already have.
Video hosting stores the file. Auto-captions guess at the audio. Neither is a Title II program for meeting video. Aware Lens is the layer that turns the file into the record the rule describes.
Sources
- ADA.gov Title II web-rule fact sheet — deadlines (as amended by the April 2026 IFR) and the archived-content exception
- April 20, 2026 Interim Final Rule
- W3C Understanding 1.2.2 (WCAG 2.1)
- W3C Understanding 1.2.5 (WCAG 2.1)
- W3C Understanding 1.2.4 (WCAG 2.1)
- Section508.gov synchronized media
Product explanation, not legal advice. Confirm 28 C.F.R. Part 35 and current ADA.gov materials before you rely on them.