--- title: "Media Players" title_image: /content-images/wai-media-guide/player-nobackground.svg nav_title: "Media Player" lang: en # change "en" to lang code, here and 2 @@s below last_updated: 2021-11-29 # Change to date of translation YYYY-MM-DD (month in middle) # translator: "..." # contributors: "..." permalink: /media/av/player/ # Add lang to end /link/to/page/@@ ref: /media/av/player/ # Do not change this layout: default github: repository: w3c/wai-media-guide path: 'content/player.md' # Add lang to the middle of the filename, e.g., index.@@.md resource: ref: /media/av/ navigation: previous: /media/av/sign-languages/ next: /media/av/acknowledgements/ changelog: /media/av/changelog/ acknowledgements: /media/av/acknowledgements/ description: Introduces considerations for providing a media player that supports accessibility. image: /content-images/wai-media-guide/social.png footer: > # Translate words below, including "Date:" and "Editor:". (Do not update the date.)

Date: Updated 29 November 2021. First published September 2019. CHANGELOG.

Editor: Shawn Lawton Henry. ACKNOWLEDGEMENTS lists contributors and credits.

Developed by the Education and Outreach Working Group (EOWG). Originally drafted as part of the WCAG TA Project funded by the U.S. Access Board. Revised as part of the WAI Expanding Access project funded by the Ford Foundation.

--- {::nomarkdown} {% include box.html type="start" title="Summary" class="" %} {:/} Some media players are not accessible to people with disabilities. There are players developed specifically for accessibility. Usually it's best to use one of these existing players, rather than code your own. {::nomarkdown} {% include box.html type="end" %} {:/} {::nomarkdown} {% include toc.html type="start" title="Page Contents" %} {:/} - This will be replaced by an automatically generated TOC when using Markdown formatting. {:toc} {::nomarkdown} {% include toc.html type="end" %} {:/} ## Introduction Modern browsers provide a default media player. Most have limited functionality to support accessibility. Rather than coding all the things needed to make a player support accessibility, most organizations choose to use an existing player with good accessibility support. There are players developed specifically for accessibility. Some are free, open source and some are commercial. ## Skills Needed {#skills} Using an existing media player developed for accessibility requires moderate HTML skills. Developing your own accessible media player requires advanced HTML and JavaScript skills. ## Player Accessibility Functionality {#player-accessibility-functionality} Accessible media players provide a user interface that works without a mouse, through speech interface, when the page is zoomed larger, and with screen readers. For example, media players need to: * Provide keyboard support ([in Understanding WCAG: Keyboard Accessible](https://www.w3.org/WAI/WCAG21/Understanding/keyboard-accessible)) * Make the keyboard focus indicator visible ([in Understanding WCAG: Focus Visible](https://www.w3.org/WAI/WCAG21/Understanding/focus-visible)) * Provide clear labels ([in Understanding WCAG: Labels or Instructions](https://www.w3.org/WAI/WCAG21/Understanding/labels-or-instructions), [Info and Relationships](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships)) * Have sufficient contrast between colors for text, controls, and backgrounds ([in Understanding WCAG: Contrast (Minimum)](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum), [Contrast (Enhanced)](https://www.w3.org/WAI/WCAG21/Understanding/contrast-enhanced), [Non-text Contrast](https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html)) Some media players provide additional accessibility functionality to users such as: * Changing the speed of the video * Setting how captions are displayed (e.g., text style, text size, colors, and position of the captions) * Reading the captions with a screen reader and braille device * Interactive transcripts Interactive transcripts use the captions file. Interactive transcripts highlight text phrases as they are spoken. Users can select text in the transcript and go to that point in the video. More details on player accessibility functionality are in a separate document: [Media Accessibility User Requirements](https://www.w3.org/TR/media-accessibility-reqs/). ## Existing Players {#existing-players} There is information online about the accessibility of media players. For example, [Web-Based Media Player Accessibility Comparison Table _(last updated July 2016)_ {% include_cached external.html %}](http://kensgists.github.io/apt/). Each media player provides documentation of the steps to set it up in a web page. For example, [AblePlayer Setup Steps {% include_cached external.html %}](https://ableplayer.github.io/ableplayer/#setup-step-1-use-html5-doctype). ### Support for Description Methods Media player functionality is required for some methods of providing description of visual information *(called audio description, video description, or described video)*, as explained in the [Description page](/media/av/description/). To the best of our knowledge, the following media players provide such functionality: * Supports description in text file (VTT format): * AblePlayer — supports description when there is space in the audio, and when the video needs to pause ("extended description") * video.js — supports description when there is space in the audio; does **not** support description when the video needs to pause ("extended description") * Supports separate audio file with description: * AblePlayer * OzPlayer * video.js — with plug-in _(If you know of other players that provide that functionality, please let us know via GitHub or e-mail with the links in [Help improve this page below](#helpimprove). Thanks!)_