Skip to content
ferndean

How-to

Accessible Video Player: What WCAG 2.1 AA Asks of Your Website's Player

Good captions and audio description don't help anyone who can't reach them. Here is what an accessible video player has to do on your website, what the YouTube embed covers, and a short test you can run this week.

Check your videos free

Published

Why the player matters as much as the captions

You can pay for accurate captions and a careful audio described version, then lose both to a player that a keyboard user can't operate. If the caption button can't be reached, the captions might as well not exist for that person.

Video embedded on current pages of your website is in scope under ADA Title II for school districts, cities and counties, and under Section 504 for HHS-funded health centers. Both rules adopt WCAG 2.1 AA. The first deadlines are April 26, 2027 for Title II entities of 50,000 people or more and May 11, 2027 for Section 504 recipients with 15 or more employees. Smaller entities have until 2028. Check yours with the deadline checker.

1. What kind of organization are you?
Answer the questions to see your deadline.

WCAG applies to the whole page, and the player is part of the page. So the questions are simple. Can someone use the player without a mouse? Can they see where they are? Do the controls say what they do? Can they turn on captions and find the described version? Does anything start talking on its own?

This post explains how the rules read for video players. It isn't legal advice. For questions about your own situation, talk to your district or agency counsel.

The WCAG 2.1 AA criteria a video player has to meet

Only Level A and AA success criteria are required. These are the ones that land on a video player most often.

CriterionLevelWhat it means for your player
2.1.1 KeyboardAPlay, pause, volume, captions, full screen and the seek bar all work with Tab, Enter, Space and arrow keys.
2.1.2 No Keyboard TrapAA keyboard user can Tab into the player and Tab back out to the rest of the page.
2.4.7 Focus VisibleAAEach control shows a clear outline or highlight when it has keyboard focus.
4.1.2 Name, Role, ValueAScreen readers announce each control by name ("Play", "Captions") and state (on or off, muted or not).
1.4.3 Contrast (Minimum)AAText in the player, like time stamps and menu labels, stands out from its background.
1.4.11 Non-text ContrastAAControl icons and focus outlines are visible against the video and the control bar.
1.4.2 Audio ControlAIf sound plays automatically, there is an easy way to pause or stop it, or turn the volume down.
2.2.2 Pause, Stop, HideAMoving content that starts on its own, like a background video, can be paused or stopped.
Captions (1.2.2) and audio description (1.2.5) apply to the video itself. The criteria above apply to the player that delivers them.

What's optional

Some video criteria sit at Level AAA, and the rules don't require them. That includes sign language interpretation (1.2.6), extended audio description that pauses the video (1.2.7), a full text media alternative (1.2.8) and low or no background audio (1.4.7). You can offer them. Don't let anyone tell you the law demands them.

Captions and audio description need a way in

A caption track only helps if the viewer can switch it on. Your player needs a caption button that a keyboard can reach and a screen reader can name. It should show whether captions are on or off.

Audio description is harder. WCAG 1.2.5 asks for it when the picture shows something the soundtrack doesn't, such as a name on screen, a chart, or a demonstration with no narration. The audio description guide walks through when it applies. You can also try the check below.

1. What's on the soundtrack?
Answer the questions about one video to see whether it needs audio description.

Once you have a described version, people have to find it. The YouTube Help page on audio description, according to YouTube Help, is written for creators adding a descriptive audio track and does not explain how viewers pick that track in the player. So don't count on viewers finding a hidden track. Post the described version as its own video and put a plain link to it right next to the original, for example "Watch the audio described version."

Is the YouTube embed an accessible video player?

The YouTube embed gives you a lot for free. It has a caption button, and YouTube Help lists built-in keyboard shortcuts: "c" turns captions on and off, "k" plays and pauses, and "m" mutes and unmutes. That page notes captions turn on "if available", so the shortcut is only as good as the track you uploaded.

Where it falls short is mostly outside YouTube's control:

  • Caption quality is yours. The button works, but auto-captions often miss names and terms. See whether YouTube auto-captions hold up.
  • The iframe needs a title. The embed sits inside an iframe on your page. A screen reader announces the iframe's title before the user enters it, and that title comes from your page code, not YouTube.
  • Described versions are hard to find. As noted above, plan on a separate described video and a visible link.
  • Your embed settings can add problems. Look at the embed code your website uses. If anything turns on autoplay or hides the controls, take it out.
  • Test, don't assume. Shortcuts and focus behavior can change. Run the test at the end of this post on a real page.

In short, the YouTube embed is a reasonable starting point. Whether the result helps you meet WCAG 2.1 AA depends on your captions, your page and your settings.

The page around the player

Even a solid player sits on a page you control. Check these on every page with a video:

  • An iframe title that names the video, like "Video: March board meeting", not just "YouTube video player".
  • A heading or label above the video so people know what it is before they press play.
  • No autoplay, especially with sound.
  • A link to the transcript if you have one, and a link to the audio described version.
  • A "request an accessible version" link so anyone who can't use the video can ask for another format. Our request form template gives you the wording and fields.

A short block of text under each embed covers most of this. Edit the bracketed parts.

Text to place under an embedded video
Captions: select the CC button in the player, or press C on your keyboard after selecting the video.
Audio described version: [link to described video]
Transcript: [link to transcript]
Need this video in another format? Request an accessible version: [link to your request form]

Anyone who asks for an accessible version has to get one, whether the video is new or old. Older video and archives follow their own rules, which the archived content guide explains.

Players and plugins to be careful with

The YouTube embed is not the only player on most websites. These are the ones that tend to cause trouble:

  • Background hero videos. A looping video behind your home page banner moves on its own. Under 2.2.2 it needs a visible pause button that works with a keyboard. If it has sound, 1.4.2 applies too.
  • Autoplay carousels and sliders. A carousel that plays video as slides rotate stacks two problems: moving content and possible autoplay sound.
  • Players built into website themes. Some themes and page builders include their own video player. They may lack labeled buttons, visible focus or a caption button. Test them like any other player.
  • Pop-up or lightbox players. When a video opens in an overlay, check that focus moves into it, that Escape or a close button works from the keyboard, and that focus returns to the page when it closes.

If a theme player fails, the simplest fix is often to swap it for a standard YouTube embed with a proper title and the text block above.

A 10-minute player test anyone on staff can run

You don't need special software. Pick one page with a video and work through these steps.

  1. 1

    Put the mouse away

    Load the page and press Tab until you reach the player. If you can't get there, or you can't tell where you are, note it.

  2. 2

    Operate every control

    Play, pause, change volume, turn captions on and off, and open full screen, all from the keyboard. Note any control you can't reach or use.

  3. 3

    Check focus

    As you Tab, watch for a clear outline on each control. If focus disappears into the video, that's a 2.4.7 problem.

  4. 4

    Tab back out

    Keep pressing Tab until you leave the player. If you get stuck, that's a keyboard trap.

  5. 5

    Zoom to 200%

    Zoom the browser to 200% and confirm the player controls and the links under it are still visible and usable.

  6. 6

    Spot check with a screen reader

    Turn on the screen reader built into your computer or phone. Listen for the iframe title and button names like "Play" and "Captions". Unlabeled buttons announced only as "button" need fixing.

  7. 7

    Reload and listen

    Reload the page. If any sound or motion starts on its own, find a way to stop it or turn it off.

Write down what failed and on which page. Fix the page-level items first, since you control them directly. Then decide whether any theme players need to be replaced. To check many pages at once, run the free website video check. It finds the videos on your site so you know which pages to test.

Ferndean is in early access, enrolling pilot districts and health centers for spring 2027. It will add checked captions and audio description to the YouTube videos you embed on your website, and give you a public page where people can request an accessible version. Today you can run the free website video check to see which pages have video.

Enter your website and we'll check it and the YouTube channel it links to.

Sources

This is a reading of the rules, not legal advice. Something out of date? Tell us and we'll fix it.

Questions

What people ask first.

Something else? Send us a message

What makes a video player accessible under WCAG 2.1 AA?
It works fully from the keyboard, shows visible focus, has labeled controls that screen readers announce, includes a reachable caption button, and doesn't start sound or motion that can't be stopped. The page around it needs an iframe title, a label and links to any described version or transcript.
Is the YouTube embed an ADA compliant video player?
No player makes a page compliant on its own. The YouTube embed has a caption button and keyboard shortcuts, but you still need accurate captions, an iframe title, no autoplay and a findable described version. Test it on your own pages.
How do viewers turn on captions in the YouTube player?
They can select the CC button, or press "c" once the player has focus, according to YouTube Help. Captions only appear if the video has a caption track.
Do we need sign language or extended audio description in our player?
No. Sign language (1.2.6) and extended audio description (1.2.7) are Level AAA criteria, and the rules require only Level A and AA. Standard audio description (1.2.5) is required when the picture shows something the soundtrack doesn't.
Can a background video on our home page cause problems?
Yes. Video that moves on its own needs a keyboard-accessible way to pause or stop it, and any sound that plays automatically needs a way to turn it off. A silent video with a visible pause button is the safer choice.

Free video check

How accessible is your video today?

Enter your website. We find the videos embedded on it and scan the YouTube channel it links to: which have accurate captions, which likely need audio description, and how much new video you post a year. Free with your work email.

Enter your website and we'll check it and the YouTube channel it links to.