A valid text resource has a defined shape
MDN describes UTF-8 content, a WEBVTT header and cue or other permitted blocks. WebVTT allows an optional byte order mark, which differs from the HLS playlist rule. A publisher should therefore validate each format by its own requirements rather than apply one generic text-cleanup recipe.
Imagine a caption export is saved as a formatted document while retaining a .vtt-looking filename. The suffix does not transform its bytes into timed text. A player can retrieve the resource successfully and still have no valid cues to present.
Keep transport and track state separate
The server's representation type should match the actual resource. A returned login page or a missing caption request is different from valid cues that remain disabled. Changing font colour cannot repair a response that never supplied usable timed text.
A developer can inspect the resource response, parser outcome and selected track state. A viewer can report the programme, language choice and content position through the supported interface. Both records should preserve what succeeded rather than collapsing every caption issue into a single availability complaint.
Check representative content positions
An opening scene can contain no dialogue, so checking only its first seconds may miss correctly timed later captions. Use a known spoken passage where captions are expected, then compare a later passage for alignment. Do not infer translation completeness from one correct line.
For a publisher quality record, retain the media edition, caption export identity, delivery response, selected track and observed rendering. These are separate acceptance steps. This guide does not claim that IPTV Australia supplies a particular subtitle track or tested a caption renderer. It explains how to isolate an invalid text dependency while preserving exact-format differences and the viewer's actual accessibility task.
Questions about this guide
Does WebVTT use exactly the same BOMrule as HLS?
No. WebVTT permits an optional BOM; HLS playlists under RFC 8216 exclude it.
Can a .vttfilename still contain the wrong resource?
Yes. Inspect the actual representation and valid structure.