Start a viewing evaluation with the accessibility feature you need

Begin with the feature the viewer depends on

An evaluation should start with the function that makes viewing usable for the person involved. That may be captions, a particular subtitle language, audio description, readable controls or reliable remote navigation. Do not leave the essential feature until after a long tour of picture quality and logos.

Describe the need as a task. Can the viewer select the required text track from their normal seat? Can they identify and choose the spoken track? Can they navigate the actual television interface with the control they use? These questions are more precise than asking whether an app is accessible in general.

Distinguish the available tracks

Dialogue subtitles and captions can serve different needs. Audio description is also a different track choice from a translated dub. The exact programme and version determine which tracks are supplied, while the player determines which controls are available.

A menu translated into a preferred language does not prove that a programme has the required audio or captions. A title with one accessible version does not establish every other edition. Keep programme identity, language and track type together when asking about availability.

Use a viewer-led worksheet

Need	Task on the actual setup	Observation to retain
Readable text	Select the required track and view from the normal seat	Size/contrast controls actually offered and whether the text is usable
Timing	Check clear lines near the start and later	Steady offset, changing mismatch or a usable result
Audio requirement	Choose the exact spoken or description track	Track label and what is actually heard
Navigation	Reach and change the controls with the intended remote	Any control that cannot be found or operated

Evaluate more than the presence of a button

A subtitle button establishes that an interface exposes a control; it does not establish the track’s correctness, timing or readability. Try the feature on the item that matters. If a label appears wrong, record the label and actual result instead of assuming all language settings are interchangeable.

Some text may be encoded into the picture rather than supplied as a selectable track. That distinction affects whether a player’s display and timing controls can change it. Desktop support should not be assumed for another television application.

Make the result specific

A useful evaluation says that a required feature was usable on a named programme, app and device, or explains exactly what prevented use. If the feature remains unanswered, keep it as an unresolved requirement before purchasing a longer term.

A short successful session does not certify formal accessibility conformance or service-wide track coverage. It can still answer the practical question that matters to the viewer. Put that question first and preserve the scope of the observation when discussing the next step.

Questions answered

Does a subtitle button prove the captions meet my needs?

No. Check the actual track, timing, readability and operation on the programme and device you intend to use.

Is audio description the same as a dubbed language track?

No. State the required track type explicitly and check it for the actual programme version.

Sources & further reading

Official references for the subjects discussed. Service terms and device software can change.