Identify the supplied track
Confirm the selected caption or subtitle and the exact programme edition. A WebVTT extension identifies a timed-text format, not a guarantee of accurate words, complete accessibility information or a specific player implementation.
W3C's May 2026 candidate recommendation draft describes cue timing and placement. Its draft status and real implementation differences should remain clear in technical claims.
Read placement as authored information
Cue settings can influence line, position, size and writing direction. A player can therefore show text in different locations rather than one fixed bottom band. Placement may help associate a speaker or avoid onscreen information.
Do not force every cue into one location simply because the first unfamiliar position looks unusual. First identify whether the placement obscures something or serves a useful purpose.
Test readability with the actual interface
Use a known cue and normal seating or screen size. Open and dismiss playback controls to see whether they overlap the caption. Check a long cue and a position near an edge.
A fullscreen comparison is a different layout condition from a small browser window. Record both dimensions or presentation states when a placement changes.
Separate source settings from player overrides
Inspect any documented user caption styling. Record whether an override changes size, background or position. The app may use native browser rendering or its own text renderer, so another app need not behave identically.
If a cue is clipped only in one implementation, report that scope. Do not change its timing to compensate for a placement defect.
Provide a cue-specific report
Give the player developer the programme, approximate time, track and visible overlap, without distributing unnecessary protected text. A few descriptive details often identify the failing layout.
This guide explains standard capabilities and a proposed assessment. It is not an accessibility conformance test, a guarantee of IPTV Canada captions or a claim that every browser implements every draft feature.
Do not flatten translated writing systems
A cue's writing direction can change how placement information is interpreted. A vertical text example should not be forced into assumptions drawn from horizontal English captions. Describe the actual language, direction and viewport when reporting clipping. The aim is a readable authored presentation, not making every track look identical to one familiar subtitle template.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- W3C WebVTT candidate recommendation draft, May 2026 — Official versioned standard excerpt: timed text cues, placement and multiple track kinds. Draft status and implementation differences retained.
- W3C WAI captions guidance — Official current accessibility guidance excerpt: captions, transcription and WebVTT context; not an accessibility conformance audit.
