Accessibility at Twilva

We are working towards WCAG 2.2 Level AA. We are not claiming to have reached it. This page says where we are, including the parts that are not finished.

Our episodes carry captions in the picture itself, so they are always visible and need nothing switched on. They cannot be turned off, resized, or sent to a braille display, because they are part of the video image rather than a separate text track.

A selectable caption track is not available yet. We generated one and withdrew it: the automatic transcription placed lines before they were spoken, put text on screen during silences, and broke sentences into blocks too long to read comfortably. Publishing that would have been worse than publishing nothing, so we are rebuilding it properly rather than leaving it up.

If you need captions as a text track — to read them on a braille display, or at the caption size you have set on your device — tell us and we will prioritise the episodes you want. That is a real request we can act on, not a queue.

• Audio description. We do not provide audio description of on-screen action. This is a WCAG 2.2 Level AA requirement (1.2.5) and we have not met it.
• Captions in languages other than English. Our catalogue is English-language and we currently caption English only.
• A selectable caption track. See above — withdrawn rather than shipped inaccurate, and being rebuilt.
• Transcripts as a separate document. We do not publish standalone transcripts.

The player supports keyboard control and works with screen readers. Videos are vertical. Where your browser allows it, playback starts with sound; where it does not, the video starts muted and a control appears so you can turn sound on.

If you have reduced motion enabled in your operating system, we honour it and suppress non-essential animation.

If something on Twilva does not work with your assistive technology, or an episode's captions are wrong, we want the specific detail — the page or episode, what you were using, and what happened.

Contact us and we will reply. Accessibility reports are not a low-priority queue.