The first completely accessible video player

OzPlayer is fully compliant with the W3C Web Content Accessibility Guidelines, Version 2.0, Level AA. It has no keyboard traps, supports captions and audio descriptions, and has a unique system for providing a moving transcript.

Demo Features Browsers Implementation

Transcripts, captions and audio descriptions

Test your video


Image on screen: OzPlayer Logo

Gian: Hi, my name is Gian Wild and I'm the Director of AccessibilityOz.

We've been operating for two years and today I would like to introduce you

to the world's first accessible video player, OzPlayer.

Text on screen: What is web accessibility and how does it translate to online videos?

Web accessibility is about making websites and applications accessible to people with disabilities.

When it comes to online videos, this is about people with deafness, or people

who are blind or visually impaired, as well as people who have physical disabilities or

cognitive disabilities. So we developed OzPlayer to address the needs of all people with disabilities.

Text on screen: Why aren't the current video players accessible?

We've tested over 100 web sites in the last year and approximately eighty per cent of

those websites had a video player of some sort. Every single video player that we tested

was inaccessible in some form. Some contained keyboard traps, others couldn't be operated

via the keyboard, others allowed some operation via the keyboard but really important features

like captions and audio descriptions couldn't be activated via the keyboard. There are other

issues such as videos starting automatically and the lack of audio descriptions and captions.

So our clients kept asking us what video player they should use and we decided that we had

to build our own in order to meet this need.

Text on screen: How do inaccessible videos impact end users?

Text on screen: 1) Keyboard traps

Some videos contain keyboard traps and this is a known bug of Flash features within Firefox.

When a video contains a keyboard trap, the user essentially needs to close the browser

window entirely and start again therefore rendering the content completely inaccessible

to the user.

Text on screen: 2) Keyboard inaccessibility

When a video is inaccessible to the keyboard, then users with physical disabilities such

as Parkinson's disease can't access the video content. We found in a number of video players

that video controls such as play and pause could be activated via the keyboard, but other

controls such as volume or activating captions or audio descriptions could not be activated

by the keyboard rendering these players inaccessible.

Text on screen: 3) Starting automatically

When videos start automatically they can be extremely disorientating to the end user.

This is when a video starts as soon as you open the page and this can be specifically

problematic to screen reader users. Screen reader users have a aural version of the page

spoken aloud to them and as you can imagine, if a video starts playing as soon as you load

a page then a screen reader user isn't going to be able to hear the contents of their screen

reader and be able to navigate the page - even to the point of being able to turn off that

video. So starting automatically, which YouTube does, is a serious accessibility issue.

Text on screen: How is OzPlayer different from other video players?

OzPlayer is fully keyboard accessible. You can turn captions on and off, you can move

the slider controls up and down, you can change the volume using the keyboard only. We also

have a unique feature in skip links at the top of the video allowing users to skip straight

to the transcript or skip the video entirely. We have native keyboard controls and one of

the things that is unique within OzPlayer is the use of HTML5. We've used a variety

of HTML5 features such as the VIDEO and AUDIO elements. There are a number of features that

we haven't used such as the native Text Track API because it's not very well supported but

as the browsers change, we will of course be including these issues.

Text on screen: What other issues make video players inaccessible?

Of course video content can be made inaccessible at the source. So containing flickering or

flashing content can trigger epilepsy and migraines in some people. In fact I've actually

had migraine triggered myself when watching some videos. There are other issues such as

colour contrast and the use of colour. But of course the most important issues are the

use of captions and audio descriptions. It is absolutely essential that any videos that

are created are created with captions and with audio descriptions. A text transcript,

although not specifically required by WCAG2 is also an absolutely essential part of making

any video accessible.

Text on screen: There are more features in development

We are really proud of OzPlayer but of course we are working to include new features in

our next version. These features include interactive media elements, sign language support and

extended audio descriptions.

Text on screen: What features would you like to see?

At AccessibilityOz we're continually iterating and we would love to improve our video player

for all users. So please let us know if there is anything you would like to see in the next

version of OzPlayer

Image on screen: Epic Photograpy & Video logo and URL, www.epicphotography.com.au, [email protected]

Text on screen: Directed by Charlotte Brentnall and Mark Fitzgerald

Editing by Mark Fitzgerald

Filmed by Mark Fitzgerald

Starring Gian Wild

Written by Charlotte Brentnall and Gian Wild

Image on screen: OzPlayer logo


More demos


  • HTML5 video and audio
  • Stream content from your web server or CDN, or play video from Youtube
  • Flash fallback for older browsers
  • Synchronised audio descriptions
  • Captions
  • Interactive transcript with a text fallback - moves along in-sync with the video
  • Fully keyboard accessible, no keyboard traps
  • Skip links
  • Can be skinned in seven different colours (from the logo colours)


OzPlayer supports all modern desktop and mobile browsers using HTML5 video and audio wherever possible, with fallback to a Flash-based player for older browsers.

View the support matrix


Using OzPlayer is as simple as can be. Include the HTML5 VIDEO and AUDIO elements on your page, include the OzPlayer JavaScript library, and find somewhere to host your video files.

Transcripts, captions and audio descriptions

We can develop transcripts, captions and audio descriptions for your video - even if you aren't using OzPlayer. We charge $25 (Australian dollars) per minute per feature. If you have a three minute video that requires all three features (transcripts, captions and audio descriptions), that will be $225. We charge GST for Australian customers. We take credit cards.

Test your video

We can also test your video, transcript, captions and audio descriptions and give you a list of any accessibility errors that exist. We charge $100 per ten minutes of video. We charge GST for Australian customers. We take credit cards.

Contact Us