Skip to content

Accessibility

Accessibility

What works today, and — more usefully — what does not yet.

Last reviewed August 2026

What works

  • The player is fully keyboard operable. Play, seek, volume, captions, speed, fullscreen and picture-in-picture all have shortcuts, and the scrub bar is a real slider with arrow-key support.
  • Shortcuts never steal your keys. Typing in a comment box or a search field behaves normally.
  • Reduced motion is respected. If your system asks for less animation, the hero stops rotating and transitions collapse.
  • Focus is always visible, in the brand blue, at a contrast that passes against our darkest background.
  • Subtitles where channels supply them, selectable per language, with your choice remembered between titles.
  • A skip-to-content link on every page, and pinch-zoom is never disabled.
  • Controls that do nothing are never shown. If a title cannot offer quality selection or downloads, the button is absent rather than present and inert.

What does not work yet

Listing these is more useful than claiming compliance we have not audited.

  • Audio description tracks are supported by the data model but no channel supplies them yet.
  • Caption appearance — size, colour, background — is not yet adjustable. It uses your browser and platform defaults.
  • The player has not been through a formal screen reader audit. Individual controls are labelled, but the experience of the whole surface has not been tested end to end with NVDA, JAWS or VoiceOver.
  • Automatic captions are not generated. A title has captions only if the channel provided them.
  • No formal WCAG 2.2 conformance statement. We have built to it, but we have not been audited against it, and saying otherwise would be dishonest.

Player shortcuts

Space or KPlay or pause
← / →Back or forward 10 seconds (Shift for 30)
J / LBack or forward 10 seconds
↑ / ↓Volume
MMute
FFullscreen
IPicture-in-picture
CSubtitles on or off
< / >Slower or faster
0–9Jump to 0–90% of the title

Tell us what is broken

If something here does not work for you, it is a bug and we want the report. Write to us with your device and assistive technology, and we will fix it rather than add it to a roadmap.