A Recording Regenerated Its Caption-Cue Map After Accessible Player Release: Remap Every Cue and Link

A changed cue map can make a recording look unchanged while its accessible use has changed. WebVTT is built from text segments associated with time intervals called cues, and the format can also carry chapters and time-aligned metadata. W3C WebVTT, May 20, 2026

Start with the media hash and transcript hash. If both match the prior release, the problem is bounded to timing and the systems that consume it. That does not make the change harmless. Captions are synchronized with audio, and interactive transcripts can use caption files to highlight phrases and seek to a selected point in the recording. W3C WAI captions

Which dependencies can break when caption cues move?

Check the player before checking the page around it. HTML track elements attach timed text tracks to audio and video, including all supported timed-text tracks and metadata. A changed VTT file can therefore affect more than the caption overlay. MDN, April 24, 2026

Inventory every accessible player release that points to the changed track. Include every dependent resource or entry point that uses the media at a time position.

Accessible players may expose captions to screen readers and braille devices, provide interactive transcripts, and let users select transcript text to move playback. Those functions depend on the caption file and should be tested after timing changes. W3C WAI media players

• A caption toggle can still appear while cues display at the wrong moment.
• A transcript phrase can still match the text while its seek target lands before or after that phrase.
• A review note can still contain a valid timestamp while pointing at the wrong spoken passage.
• A chapter or metadata cue can still load while its navigation target has shifted.

How do you remap each cue to unchanged media?

Build the crosswalk from the old and new caption files, not from memory. Match each cue by its text, using speaker labels where present and neighboring transcript context. For every cue, record the old and new start-and-end boundaries plus the reviewer decision.

Do not assume a constant offset fixes the file. A regeneration can alter individual cue boundaries, content, or identifiers. WebVTT permits cue identifiers and timing settings as well as cue text, so a text match alone is not enough to preserve every dependency. W3C WebVTT, May 20, 2026

Where one old cue maps to several new cues, map the old deep link to the first new cue that contains the referenced phrase, then record that choice. Where several old cues merge, retain the earliest old reference and test the new landing point against the reviewer note.

• Freeze the pre-release VTT, transcript, player configuration, and dependent links.
• Calculate and record hashes for the recording and transcript versions under review.
• Perform a complete old-to-new cue diff.
• Assign each old cue a new target or an explicit no-match ruling.

• Have a reviewer validate sampled and high-risk mappings in the player.

When can the accessible derivative stay live?

Keep the derivative live only when the impact file shows that caption synchronization is intact and all known destinations resolve correctly. This is a release decision, not a claim that the new timing is safe because the media bytes are unchanged.

For prerecorded synchronized media with audio content that is needed to understand the recording, W3C's explanation of WCAG 2.2 Success Criterion 1.2.2 calls for captions. It describes captions as synchronized text that includes dialogue and relevant non-speech audio information. W3C WCAG 2.2 guidance

Reissue when the player loads the new track but any accessibility function or referenced timestamp has materially changed. Recall or temporarily remove the derivative when the affected population cannot reliably reach the intended audio or text while the replacement is being verified.

How should you test reading order and player behavior?

Test the released player, not only the VTT file. Use the same browser and player route a visitor uses, then fully test all supported controls and navigation. Record the player version and test environment in the impact file.

W3C describes accessible media-player functions that include keyboard support, visible focus, clear labels, sufficient contrast, caption display controls, screen-reader and braille access to captions, and interactive transcripts. W3C WAI media players

Check the transcript's reading order separately from visual highlight timing. A transcript can appear correct on screen while a keyboard user encounters controls or text in an unexpected sequence. Record actual results and failures, rather than marking a generic accessibility check complete.

• Open every timestamped link from outside the player and confirm the intended phrase or event is reached.
• Turn captions on and off, then seek through changed cue boundaries.
• Use keyboard-only navigation through controls and transcript items.
• Use the project's supported screen-reader test route where one exists.
• Confirm captions include required speech and relevant non-speech audio information after regeneration.

What should the closure record prove?

Closure should let another reviewer reproduce the decision without reopening the entire incident. Keep the before and after VTT files, hashes, cue crosswalk, player inventory, deep-link results, reviewer name, release ruling, and the final public URLs.

Do not close based on a successful upload. The record should show that each affected dependency was documented as remapped and tested or deliberately replaced; otherwise, rule it out with evidence.

If a player has no interactive transcript, descriptions, chapters, or metadata track, record that absence after checking its configuration. Do not infer that one player's clean result covers another player's implementation.