Compliance

ADA Title II and Course Video: What Changes by April 2027

The Department of Justice rule requires web content and mobile apps at state and local government entities, public universities and colleges among them, to meet WCAG 2.1 Level AA. In April 2026 the DOJ extended the compliance dates by a year: entities serving 50,000 or more people now have until 26 April 2027, and smaller entities and special districts until 26 April 2028.

That extension bought time, not relief. Course video is where most institutions still fall short, because the obligation covers the player, the captions and everything layered on top of them. An inaccessible quiz or discussion panel fails the standard as surely as a missing transcript.

Learn more: what the rule covers, and where video estates usually fail

Title II and Video

The Standard, the Dates and the Video Problem

The 2024 rule set a technical standard rather than a general duty: WCAG 2.1 Level AA for web content and mobile applications. In April 2026 the DOJ issued an interim final rule pushing both compliance dates back twelve months, citing resource constraints, staffing limits, the immaturity of automated remediation including generative AI, and litigation risk. The requirement did not change. The date did.

Who does this apply to?

State and local government entities, which includes public colleges, universities, community colleges and school districts. Entities serving a population of 50,000 or more work to 26 April 2027. Entities serving fewer than 50,000, and special district governments, work to 26 April 2028. Private institutions sit under Title III, where the direction of travel is the same even though this particular rule does not name them.

Why is course video the hard part?

Three reasons. Volume, because a decade of recorded lectures is a large remediation surface. Ownership, because media teams, faculty and IT each hold part of the workflow. And layering, because the accessibility obligation does not stop at the video file. Whatever sits on top of the player, including quizzes, discussion panels and note-taking, has to be operable by keyboard and legible to a screen reader.

What does captioning actually require?

WCAG 2.1 AA asks for captions on prerecorded and live synchronised media, and audio description for prerecorded video where meaning is carried visually. Auto-generated captions are a starting point rather than an answer, since accuracy on technical vocabulary and accented speech is where most audits find failures. Most video platforms handle the captioning pipeline, and Annoto sits on top of whichever one you run.

Where does the engagement layer fit?

If you add interaction to video, that interaction inherits the obligation. Annoto's interface meets WCAG 2.1 AA, so in-video quizzes, discussion, polls and notes remain operable for keyboard and screen reader users. See the accessibility statement for the current conformance position.

Does interaction help or hurt accessibility?

It helps, when it is built correctly. A student who cannot follow a fast-moving lecture benefits from timestamped notes, a transcript they can question, and a discussion thread anchored to the moment they lost the thread. Accessibility work framed only as remediation misses that the same features improve comprehension for everyone.

What should we do between now and the deadline?

Inventory the video estate and find out what actually carries accurate captions. Fix the highest-enrolment courses first, because that is where exposure concentrates. Check every tool layered on the player, not only the player. And write the standard into procurement, so the next contract does not recreate the problem.

How do we test the interaction layer with a keyboard?

Test on a real course, not a demo page. Tab from the player into the engagement panel and confirm that focus stays visible at every stop, that timeline markers are reachable without a pointer, and that a comment can be opened, replied to and submitted from the keyboard alone. In-video quizzes are the sharpest test, because the question interrupts playback: focus has to move deliberately, Escape has to behave predictably, and focus has to return to the control that held it. Repeat the pass on peer review and video assignments, where recording adds controls of its own.

What does a screen reader user hear in a discussion thread?

More than the words. A comment in the timeline discussion carries an author, a timestamp and a position in its thread, and a student who cannot see the timeline needs all three read aloud, or the remark floats free of the moment it refers to. Quiz questions should be announced with their type and options, and feedback on submission should reach the user as text, not as a colour change alone. Notes and AI recaps are text by construction, so they read cleanly. Ask any vendor to demonstrate with NVDA, JAWS or VoiceOver on your own course.

Who owns captions once a layer sits on the player?

The host does, and that division matters when you plan remediation. Annoto overlays Panopto, Kaltura, YouTube and Vimeo or hosts video natively, but caption tracks, transcripts and audio description stay with the media platform, so adding a layer leaves your captioning queue where it was. What the layer owes you is that it never obscures the caption region, breaks the player's own controls, or collapses at 200 per cent zoom. Test with captions switched on, since that is the state an auditor will use.

What should we ask a vendor before signing?

Ask for a current accessibility conformance report against WCAG 2.1 AA, with the evaluation date and method named. Ask which components were tested and by whom, and for the open defect list with remediation dates, since a candid list is a better signal than a clean one. Confirm that LTI 1.3 launch and gradebook sync work without a mouse, and that staff-facing analytics are in scope, because instructor dashboards carry the same obligation as student screens. Then ask who a student contacts when they hit a barrier, and how quickly that is answered.

FAQ

ADA Title II and Course Video, Answered

When is the ADA Title II web accessibility deadline?

The DOJ extended both dates by a year in April 2026. State and local government entities serving a population of 50,000 or more must comply by 26 April 2027. Entities serving fewer than 50,000, and special district governments, have until 26 April 2028. The technical standard is WCAG 2.1 Level AA for web content and mobile applications.

Why were the deadlines extended?

The DOJ cited resource constraints and staffing limitations at public entities, slower than expected progress on technical remediation including the limits of generative AI for that work, and litigation risk. The obligation itself was not weakened.

Does the rule cover our lecture recordings?

Yes, where they are web content your institution provides. That means captions on prerecorded media, audio description where meaning is carried visually, and an accessible player. It also covers anything layered on the player, which is the part most audits overlook.

Are auto-generated captions enough?

Treat them as a first pass. Accuracy tends to fall on technical vocabulary, accented speech and overlapping talk, which is exactly where a course needs it most. Institutions that pass audits generally review captions on high-enrolment courses rather than trusting the automatic output everywhere.

Is the Annoto layer accessible?

Annoto's interface meets WCAG 2.1 AA, so quizzes, discussion, polls and notes stay operable by keyboard and legible to screen readers. See the accessibility statement and Security and Trust for the current position, and ask us for documentation during procurement.

We are a private institution. Does this apply?

This particular rule applies to Title II entities, which are state and local government bodies including public colleges and universities. Private institutions fall under Title III, where WCAG 2.1 AA has become the practical benchmark in settlements and procurement even without an equivalent rule. Confirm your position with counsel.