Check that a language choice opens the approved subtitle track
A video can have correctly reviewed language files and still show the wrong one when a visitor makes a choice. The menu label, the track's language declaration and the file it loads are separate pieces of the published experience. Checking the wording in a translation document does not establish that those pieces are connected correctly.
This guide follows a fictional New Zealand visitor-information video. The organisation has commissioned an English subtitle file and a te reo Māori subtitle file for the same approved cut. Its language reviewers have assessed those complete files. The problem is in their association with the player, not in a newly discovered translation requirement.
Establish which assets have actually been approved
The video, V-17, explains where an arriving group should meet its host. The release record identifies cut C-4 and two subtitle assets: E-7 for English and M-7 for te reo Māori. Both contain the approved cues for that cut. A separate captioning and accessibility review has its own scope; a translated subtitle track should not automatically be described as a complete captioning solution.
The visitor chooses “Te reo Māori” but sees English text. Selecting “English” produces the other language. Neither file is missing, and the menu is not merely retaining a previous selection.
Before changing any language content, the reviewer checks the delivered page's track configuration and the exact files associated with it. Asset names are clues, but the approved file identity and contents are the evidence.
Follow the choice to its file
The inspected configuration in this example is:
| Visible choice | Declared track language | File actually loaded | Approved identity |
|---|---|---|---|
| Te reo Māori | mi |
arrival-en-r7.vtt |
E-7, English |
| English | en |
arrival-mi-r7.vtt |
M-7, te reo Māori |
The two file references are crossed. The language declaration and label describe the intended track, while the referenced resource contains the other approved language. The defect can be explained without asking the translator to rewrite either file.
The HTML standard's track definition distinguishes the source URL, the language of the track data and the user-readable label. That distinction is useful during review: a correct label does not verify the resource behind it.
In the fictional inspection, the cue associated with the meeting-point explanation comes from E-7 after selecting the Māori-labelled track. The file identity agrees with the observed English cue. Checking another cue later in the same track confirms that this is a crossed resource association, rather than a single untranslated line.
Correct the association without altering approved meaning
The selected correction binds the Māori-labelled track to M-7 and the English-labelled track to E-7. The approved video cut and both subtitle files remain unchanged. The organisation retains its chosen track kinds and labels; no new translation or claim about staff language capability is introduced.
This is a narrow correction. It does not change the default language policy, introduce automatic geolocation or choose a language from the visitor's name. Visitors retain a meaningful choice, and the organisation remains responsible for the review and maintenance of each version.
The implementation should keep the relationship explicit enough that a future asset update is reviewable. An editor replacing a file needs to know its cut, language and approval identity. A folder containing several similarly named files is not a sufficient release record.
Review both directions after the change
The corrected example is assessed through the actual selection task, using the intended player arrangement:
| Review task | Result required and obtained in the fictional review |
|---|---|
| Select Te reo Māori for V-17 | The loaded resource is M-7; its meeting-point cue and later sample cue match the approved Māori file |
| Select English for V-17 | The loaded resource is E-7 and the corresponding English cues remain correct |
| Turn subtitles off | The selected text track stops displaying; the video itself is unchanged |
| Open independent video V-18 | Its existing language-to-file associations remain intact |
| Inspect the delivered release record | C-4, E-7 and M-7 still identify the approved assets; only the two bindings changed |
These are the stipulated outcomes of the worked example, not a claim that every player renders controls identically. A real implementation must use its actual player, supported browsers and intended access methods. The language reviewer should see the published task as well as the source files.
Keep the other review questions visible
Correct selection does not establish that the wording is culturally appropriate, that every cue is readable at its displayed speed or that the video is accessible to every intended visitor. Those questions require their own review. Captions may need information about speakers and meaningful sounds in addition to spoken words. A transcript or other alternative can serve another task.
The distinction matters when scoping a project. Technical work can establish which approved file is loaded. It cannot turn an unreviewed translation into approved language merely by assigning a mi tag. Nor does a Māori subtitle option imply that project discussions or customer support will be available in te reo Māori.
Prepare a small release record
For each relevant video, record the cut, the approved language assets, the intended labels and the person responsible for reviewing changes. Include the route where the video appears and one meaningful selection task for each language.
When the video changes, return the affected subtitle and caption assets to the appropriate review process. A previously correct binding can still lead to content for an older cut. Keep that content-version question separate from the crossed-file defect demonstrated here.
Business website work can include this publishing journey. Bring the current video page, the approved assets and the choice a visitor needs to make to the project conversation.