Why Does My Product Video Not Expose Both English Caption Tracks?

Different files do not necessarily define different tracks

HTML text tracks have more identity information than their filenames. Each track element can declare a kind, srclang, label and src. MDN documents a constraint that a media element cannot contain multiple track elements with the same combination of kind, language and label.

This matters when a merchant wants two English caption treatments, such as a standard transcript and a separately reviewed simplified-language version. They may be different editorial assets, but if both are declared as kind="captions", srclang="en" and label="English", the track definitions are not adequately distinguished.

The problem is not solved by changing standard-en.vtt to alternate-en.vtt. The file paths differ already. The relevant collision is in the track metadata presented to the media element.

Inspect every attribute in the rendered player

Ask the developer to inspect the final video element and list all track elements in their rendered order. For each, record the actual source URL, kind, language, label and default state. Verify that each file is reachable and contains the approved content for the current video revision.

If two tracks have identical kind-language-label combinations, correct the metadata so the intended choices are distinguishable. Labels should truthfully describe the difference. Do not invent a different language code merely to avoid a collision: both English versions remain English.

If the combinations are already distinct but the player displays only one option, investigate its supported track-selection interface, application logic and browser behavior. A valid HTML declaration does not guarantee that every custom player exposes every alternative in the same way.

Also distinguish a duplicate metadata definition from duplicated on-screen captions. Two simultaneously visible caption layers can result from burned-in text plus player captions, which is a separate problem.

Hypothetical case: two English versions share one label

Hypothetical illustration, not a playback test: A fictional product tutorial has two approved English WebVTT files. The first contains standard captions; the second contains an alternative simplified-language rendering. Both are assigned kind="captions", srclang="en" and label="English".

The metadata duplicates the same combination even though the files differ. A proposed correction retains the real English language code and gives the alternatives distinguishable labels, such as English — Standard and English — Simplified, subject to the publisher's approved naming policy.

That correction addresses the HTML metadata conflict. It does not establish that the destination player supports the desired alternative-caption experience. The next step is an actual player test that selects each option and confirms the correct text appears at the correct time.

The worksheet records the proposed metadata states and leaves deployment verification unresolved.

Approve both the technical choice and the caption meaning

Test the final video in the destination. Select each alternative separately, inspect the opening, a product-name cue and the ending, and confirm that the chosen file matches its label. Check that switching tracks does not leave two conflicting visible caption streams.

Keep the two text files attached to the same approved video revision. If the video is recut, review cue timing in both. If one version simplifies language, ensure that essential product qualifications remain accurate and that its purpose is not confused with a translation.

The existing subtitle export guide covers independently delivering different language files. This article isolates a same-language metadata collision in HTML. External player implementation and caption review remain the publisher's responsibility.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• MDN — track HTML element: Documents the restriction on duplicate kind, srclang and label combinations, alongside track attributes and their roles.
• MDN — TextTrackList interface: Documents the collection of text tracks associated with a media element, supporting inspection of the actual available tracks.