Video Localization: Captions & Spoken-Word
🚧 ExpandingVideo localization is how you make video content reach people who don’t share your language or can’t hear the audio. It splits into two broad families: text on screen (captions, which include sound cues like [door slams] for deaf and hard-of-hearing viewers, and subtitles, which assume you can hear but translate the words) and replacing the spoken audio (dubbing or voiceover in another language). It matters for the same two reasons as accessibility and i18n combined — reach and inclusion — and it’s worth knowing because a huge share of people watch video with the sound off regardless of ability.
When this page is filled in, it’ll cover the caption-versus-subtitle distinction, the WebVTT format you’ll most often implement on the web, the trade-offs of dubbing versus subtitling (cost, speed, authenticity), open versus closed captions, and the workflow questions — do you translate from a transcript, who reviews quality, how do you sync timing. Until then, the Go Deeper links carry it.
📚 Go Deeper
Tools
- MDN — WebVTT APIThe format you'll most likely implement for web captions and subtitles, explained with real cue syntax and examples.
- W3C Internationalization (i18n) ActivityWhere the standards bodies work through the cross-language and text-direction questions that subtitle work runs straight into.
- MDN — Adding captions and subtitles to HTML videoA concrete, copy-along guide to attaching caption tracks to a video element.