ADA Title II Video Accessibility Exceptions: When Are Government Videos Exempt?
The DOJ's ADA Title II final rule requires state and local government web content, including video, to meet WCAG 2.1 Level AA. But not every video a government entity has ever published must be made accessible by the compliance deadline. The rule defines five specific exceptions, plus additional provisions for fundamental alteration, undue burden, and minimal-impact noncompliance.
This article explains each exception, how it applies to video content, and what obligations remain even when an exception applies.
The five exceptions under § 35.201
The DOJ recognized that requiring immediate accessibility for every piece of content a public entity has ever published could divert resources from making the most important, current content accessible first. The final rule defines five categories of content that do not need to meet WCAG 2.1 Level AA.
1. Archived web content
Video content that meets all four of the following criteria is exempt:
- It was created before the entity's compliance date (April 24, 2026 for entities with 50,000+ population; April 24, 2027 for smaller entities and special district governments)
- It is kept only for reference, research, or recordkeeping
- It is stored in a designated archive area
- It has not been changed since it was archived
What this means for video: A recording of a 2019 town hall meeting stored in an "archived meetings" section of a city website, left unedited, would likely qualify. However, if the city re-encodes the video, adds a new intro, or moves it to a non-archive section to feature it in a current page, the exception would no longer apply.
What does not qualify: Council meeting recordings created after the compliance date, even if placed in an "archive" section, must still meet WCAG 2.1 Level AA. The content creation date matters, not just the label on the webpage.
2. Preexisting conventional electronic documents
Word processing, presentation, PDF, and spreadsheet files that were available on the entity's website or mobile app before the compliance date generally do not need to meet WCAG 2.1 Level AA.
What this means for video: This exception applies to document formats, not video files. A PowerPoint presentation posted in 2022 may be exempt, but a video recording of that same presentation is covered under the archived content exception (if it qualifies) or must meet the standard. Video files themselves (MP4, MOV, WebM) are not "conventional electronic documents" under this exception.
Important caveat: Even exempt documents lose their exemption if they are currently used to apply for, access, or participate in a government service. A PDF application form from 2020 that residents still use to apply for permits is not exempt, regardless of when it was first posted.
3. Content posted by a third party
Content posted by members of the public or other third parties on a government website or app does not need to meet WCAG 2.1 Level AA, as long as the third party is not posting due to a contractual, licensing, or other arrangement with the public entity.
What this means for video: If a resident uploads a video comment to a city's online public comment portal, that video is third-party content and is exempt. But if a city contracts with a video production company to create informational videos, those are not third-party content, even though an outside party produced them. The city's contractual arrangement makes the content the city's responsibility.
What does not qualify: Videos created by a vendor under contract, embedded third-party tools (scheduling widgets, maps, payment portals) posted by the government, and content from a government contractor or subcontractor are all the government's responsibility.
4. Individualized, password-protected conventional electronic documents
Documents that are about a specific individual, their property, or their account, and that are password-protected or otherwise secured, do not need to meet WCAG 2.1 Level AA.
What this means for video: This exception is narrow and primarily applies to document formats (PDF, Word, spreadsheet, presentation files). A personalized PDF water bill in a resident's secure portal account would qualify. A video, even if password-protected and personalized, is not a "conventional electronic document" and would not fall under this specific exception.
5. Preexisting social media posts
Social media posts made by a state or local government before the entity's compliance date do not need to meet WCAG 2.1 Level AA.
What this means for video: A city's 2023 Facebook video announcing a summer concert series does not need to be captioned or audio-described under this rule. But every video the city posts to social media after its compliance date must meet the standard. This exception is purely date-based: before the deadline, exempt; after the deadline, required.
What does not qualify: Any social media video posted after the compliance date must be accessible, regardless of how short, informal, or time-sensitive it is.
Beyond the five exceptions: other provisions
Fundamental alteration and undue burden (§ 35.204)
Even outside the five exceptions, a public entity is not required to take actions that would result in a fundamental alteration of its services, programs, or activities, or that would impose an undue financial and administrative burden.
This is not a blanket exemption. The determination must be made by the head of the public entity (or their designee) after considering all available resources, and the entity must provide a written explanation of the decision. If full compliance would be an undue burden, the entity must still comply to the extent that it does not result in a fundamental alteration or undue burden.
What this means in practice: A small rural water district with a two-person staff and a minimal budget might be able to demonstrate that captioning hundreds of archived training videos by the deadline constitutes an undue burden. But the entity would still need to prioritize making its most important and current video content accessible, and would need to provide accessible alternatives upon request.
Minimal impact on access (§ 35.205)
If a public entity can demonstrate that a specific instance of noncompliance has such a minimal impact on access that it does not affect the ability of individuals with disabilities to use the entity's web content or app in a substantially equivalent manner, the entity may be considered to have met the requirements.
What this means for video: This provision is intended for truly minor technical issues, not for missing captions or audio descriptions entirely. A video where captions are present but one caption cue has a minor timing offset of a fraction of a second might qualify. A video with no captions at all would not qualify under this provision.
Conforming alternate versions (§ 35.202)
A public entity may use a conforming alternate version of web content (an accessible version that provides the same information and features) only when it is not possible to make the primary content accessible due to technical or legal limitations. This is not a general license to maintain inaccessible content alongside an "accessible version." The DOJ has stated that people with disabilities should get equal access to content on the same page, not a separate, lesser experience.
What the exceptions do not change
This is the most critical point that government entities often misunderstand: even when an exception applies, the entity's broader ADA obligations remain in effect.
Under the ADA, state and local governments must still provide:
- Effective communication to individuals with disabilities
- Reasonable modifications to policies, practices, and procedures
- An equal opportunity to participate in or benefit from services, programs, and activities
In practical terms, this means that if a resident with a hearing disability requests access to an archived, pre-deadline council meeting video, the city may still need to provide captions for that specific video upon request, even though the archived content exception applies to the proactive, sitewide accessibility requirement.
The exceptions reduce the scope of what must be made proactively accessible by the compliance deadline. They do not eliminate the obligation to provide accessible content to individuals who request it.
A practical framework for government video teams
Given the exceptions and provisions above, here is a straightforward approach to prioritizing video accessibility:
Must be accessible by the compliance deadline
- All new video content published after the compliance date (website, social media, YouTube, any platform)
- All pre-existing video content that does not meet one of the five exceptions
- Live-streamed meetings, hearings, and events (real-time captions required)
- Videos embedded on active, current-use pages of the entity's website
May be exempt (verify against the criteria)
- Pre-deadline videos stored in a designated archive that have not been edited
- Pre-deadline social media posts
- Third-party content posted by members of the public (not vendors or contractors)
Still requires on-request accessibility
- Archived videos that a resident with a disability specifically requests access to
- Any content where effective communication obligations apply, regardless of exception status
How Recap helps government entities prioritize
Recap's platform is designed for exactly this kind of phased approach to video accessibility. Government entities can:
-
Start with new content: Set up automated captioning, audio description, and transcript generation for all new videos going forward. This ensures compliance from day one of the deadline.
-
Process high-priority back-catalog videos: Identify pre-existing videos on active website pages, frequently accessed recordings, and content that does not qualify for an exception, and process them through Recap for captions, audio descriptions, and transcripts.
-
Handle on-request accessibility: When a resident requests access to an archived or exempt video, upload it to Recap and receive captions, a transcript, and audio descriptions within minutes, not days.
This approach lets government teams meet the legal requirements efficiently without spending resources on content that qualifies for an exception and has not been requested.
Contact us:
- Email: government@recap-innovations.com
- Demo: recap-innovations.com/demo
- Local government solutions: recap-innovations.com/solutions/local-government
This article is provided for informational purposes and does not constitute legal advice. Government entities should consult with legal counsel regarding specific ADA Title II compliance requirements. References to the DOJ's final rule and the ADA.gov fact sheet are included for your reference.