ADA Title II 2027: Making Your Video Content Accessible in Time

For years, digital accessibility in public higher education lived in a gray zone. The Americans with Disabilities Act clearly applied to state and local government, but there was no single technical standard that told a university exactly what "accessible" meant for a website or a lecture video. That gray zone is gone. The Department of Justice's 2024 final rule under Title II of the ADA adopts a specific standard, WCAG 2.1 Level AA, and attaches hard compliance deadlines to it. Video, one of the most common and most frequently non-compliant asset types on campus, sits squarely inside the scope.

This article maps the rule to video, explains what the recent deadline extension did and did not change, and shows how to build accessibility into your video engagement layer instead of bolting it on the week before an audit.

The deadline that changes procurement: Title II, WCAG 2.1 AA, and April 2027

In April 2024 the DOJ published a final rule requiring that web content and mobile apps offered by state and local government entities, public universities included, conform to WCAG 2.1 Level AA (Ohio State ASC). The original compliance dates were April 24, 2026 for public entities serving a population of 50,000 or more, and April 26, 2027 for smaller entities and special district governments.

Those dates moved. In mid-April 2026 the DOJ issued an Interim Final Rule extending each deadline by one year. Large public entities, effectively all public universities, now have until April 26, 2027, and smaller entities have until April 26, 2028 (UPCEA). The critical point that institutions keep getting wrong: the extension changed only the compliance date. The WCAG 2.1 Level AA standard is unchanged, and every underlying obligation remains fully in force. This is a schedule adjustment, not a reprieve, and it is exactly why accessibility is now a compliance line item in procurement rather than a best-effort aspiration.

What does "all digital content" actually include?

The instinct is to read "web accessibility" narrowly as the public marketing site. The rule is far broader. Covered content includes course materials, learning management systems like Canvas, mobile apps, PDFs, third-party tools, and videos, whether or not the institution created or owns them (Ohio State ASC). If a student encounters it as part of their education, it is in scope.

For a video-heavy program that is a large surface area. Every recorded lecture, every embedded YouTube or Kaltura clip, every interactive overlay on top of that video has to meet the standard. And because the rule reaches third-party and linked content, you cannot assume the problem belongs to someone else. If you assign it, you own its accessibility.

Where video fails WCAG: captions, transcripts, keyboard, and overlays

Video tends to fail WCAG 2.1 AA in a predictable handful of places. Knowing them tells you where to look first.

• Captions. Synchronized captions for all prerecorded audio are a core Level A/AA requirement, and auto-generated captions that are riddled with errors do not clear the bar. The rule specifically calls out captioning video as part of accessible course content (Ohio State ASC).
• Transcripts. A text alternative lets students who are deaf-blind, who use screen readers, or who simply learn better by reading follow the material and search it.
• Keyboard access. Every control, the player and any interactive layer on top of it, has to be operable without a mouse. WCAG requires all navigational and interactive elements to work with assistive technology.
• Interactive overlays. This is the one teams forget. If you add quizzes, notes, or discussion on top of a video, those components are now web content too. They need proper focus order, labels, and screen-reader compatibility, or they become a new accessibility failure layered onto content that was otherwise fine.

That last point matters enormously for engagement tools. An inaccessible interactive layer does not just fail its own users. It can make a compliant video non-compliant.

From compliance to UDL: designing for variability, not just the audit

Treating April 2027 as a finish line is a mistake. Meeting WCAG is the floor, and a floor is worth clearing, but the more durable frame is Universal Design for Learning. CAST's UDL Guidelines 3.0 start from the premise that learner variability is the norm, not the exception, and that content should offer multiple means of engagement, representation, and action from the outset (CAST UDL Guidelines 3.0).

The practical difference is timing and mindset. Compliance asks "does this pass the audit?" UDL asks "can every learner engage with this?" Captions help students in a noisy dorm and non-native speakers, not only deaf students. Transcripts help anyone reviewing for an exam. When you design for variability up front, WCAG conformance tends to fall out as a byproduct, and you stop paying the far higher cost of remediating thousands of legacy videos under deadline pressure.

Accessible-by-default engagement: captions, notes, and screen-reader-friendly discussion

The goal is a video experience where the interactive layer is accessible in the same way the video is. In practice that means a few things being true by default rather than by heroic effort:

• Captions and transcripts are present and synchronized, and searchable text lets students jump to the moment they need.
• Discussion, notes, and quizzes anchored to the timeline are fully keyboard operable and expose proper roles and labels to screen readers.
• Students who cannot use a mouse can still participate in the interaction, not just watch the video, because participation is where the learning happens.

This is the accessibility case for building engagement into the video with a standards-aware layer rather than stitching together tools that were never designed to work together. Annoto's accessible engagement layer and video assignments are meant to keep captions, notes, and discussion usable for every student, so adding interaction does not quietly add an accessibility liability. Because the same layer runs across any LMS and any video host, you get one accessibility posture to verify instead of a different answer for every tool.

Building an accessible video workflow across the institution

Accessibility fails when it depends on one conscientious instructor remembering to caption a file. It succeeds when the workflow makes the accessible path the default path. That means captioning as a step in the publishing pipeline rather than an afterthought, transcripts generated automatically, procurement contracts that require vendors to document WCAG 2.1 AA conformance, and a review process that treats interactive overlays as covered content. When accessibility is infrastructure, the burden on individual faculty drops and consistency goes up.

A Title II video-readiness checklist

1. Inventory every video students touch, including third-party and linked content, and flag what lacks accurate captions and transcripts.
2. Verify that captions are accurate and synchronized, not just auto-generated and left uncorrected.
3. Test the player and every interactive overlay for full keyboard operability and screen-reader compatibility.
4. Confirm that any quiz, note, or discussion layer on top of the video exposes proper labels, roles, and focus order.
5. Write WCAG 2.1 Level AA conformance into procurement so new tools arrive compliant.
6. Shift from remediation to UDL: design new video with captions, transcripts, and accessible interaction from the start.
7. Assign clear ownership and a schedule that finishes well before April 26, 2027, because remediation always takes longer than expected.

The deadline extension bought institutions a year, not a pass. The obligations are already in force, the standard is fixed, and video is where most programs have the most work to do. The teams that treat this as a chance to design accessible, engaging video from the ground up, rather than a last-minute audit to survive, will end up with courses that are both compliant and genuinely better for every learner. For a broader look at how this fits alongside data protection and governance, see our work on security and how it supports programs across higher education.