Video.js’s Approach to Video Player Accessibility
Updated: February 22, 2018
The original author of Video.js, Steve Heffernan, joined the expert panel at 3Play’s webinar on the future of video player accessibility. Play the video below to watch Steve’s presentation, or read on for highlights.
What is Video.js?
Steve Heffernan is the original author of Video.js and continues to lead the project at Brightcove. He tells the origin story of the platform:
As a free, open-source project, Video.js is entirely built and maintained by over 150 contributors.
“All of the features,” says Steve, “including accessibility features, have been added by contributors who have stepped up and said, ‘I want to improve the player in this way.'”
He encourages anyone who wants to contribute to Video.js development to do so on Github.
Video.js & Mozilla Build VTT.js
Since it was built with HTML5 in mind, Video.js has supported WebVTT captions for a long time — longer even than most web browsers.
To take caption support to the next level, Video.js partnered with Mozilla, the company behind the Firefox web browser, to build VTT.js. Now both Video.js and Firefox share the same code base for displaying captions, which allows for complex maneuvers like displaying vertical language captions or multiple caption tracks at once.
Challenge: Extensibility vs. Accessibility
Steve laments one of Video.js’s greatest design challenges:
“When we tried to make the player more customizable, it resulted in poor accessibility.”
He gives a few examples.
Divs vs. Buttons
For his first example, Steve compares the use of a
button tag with a
div that has a customized role of button. Defining a custom role of button within a
div protects your UI from adopting style formatting from other frameworks.
The image below shows an example of a video in Foundation framework that uses the
button tag instead of a
div. You can see how the button display is affected by Foundation’s style defaults for that tag. Using
div prevents this.
button tags are useful for screen readers to identify buttons on a video player and are a much better option for making your video accessible to blind users. Video.js will move to adopt the
button tag for this reason.
Video.js ran into other issues when updating the video player control bar. Steve explains:
Future Plans for Video.js Accessibility
In addition to switching to
button tags and fixing the tab order, Video.js has a few other plans for better video player accessibility. Improvements on the horizon include:
- Improve focus styles
- Possibly adding audio descriptions with YouDescribe.org
- Aiming for WCAG 2.0 compliance
Hear what else Steve has to say about the future of video accessibility in the post-webinar Q&A.
How to Produce WCAG-Compliant Video Captions and Audio Descriptions
If you want your video content to comply with the Web Content Accessibility Guidelines (WCAG) 2.0 Level AA then you need captions and audio description. But how do you determine what constitutes “WCAG compliant” captions or descriptions? What standards are your captions…
3 Essential Steps for Building Accessibility into the Procurement Process
Accessibility should be included from the start. The best way to achieve this is by having clear guidelines and processes in place that all members of an organization can refer to. Kara Zirkle is an accessibility specialist who has helped establish comprehensive…
Captioning and Transcription for Medical Content
Whether it’s a hospital marketing video, instructional surgery video, recorded medical course lecture, or any other kind of medical multimedia content, adding captions and transcripts is a must. Videos without captions are not accessible to people who are deaf and hard of…
Subscribe to the Blog Digest
Sign up for our blog digest. Your privacy is important to us. We’ll never share your email address.