Applies to: A programme title is not displayed legibly in one view.

The useful distinctions

  • Written text and its visual presentation are different evidence.
  • A screenshot can show a symptom without establishing its technical cause.
  • Account details around a title can create unnecessary disclosure in a support image.

Preserve what remains identifiable

A row of boxes may make a title hard to recognise, but other context can still identify the item. Save the supplied programme or edition identifier and any readable surrounding title text. If copying produces a text string, keep that string separately from the screenshot. State whether it is readable in the copied form. This gives support two kinds of evidence without assuming that the visible marks reveal the exact underlying cause.

Report the symptom without guessing

Describe which view shows the problem and whether another view displays the same title differently. Avoid labelling it a translation error, missing font or corrupted source until evidence supports that explanation. A screenshot should focus on the title area, with account names, tokens and unrelated programmes excluded. A carefully bounded report can preserve the display problem while avoiding the much larger disclosure created by sharing an entire signed-in page.

Hypothetical worked example

A fictional programme with ID TX-12 displays several square marks in a search row. The viewer copies the title into a private support note and records that the copied string is readable there. They attach a cropped image of the affected row if needed. Their report names the two observations but does not claim a tested font diagnosis or share the account panel that happened to surround the search result.

A focused way to proceed

  1. Copy the title text if the interface allows it and retain the identifier.
  2. Record where the illegible characters appeared.
  3. Share a narrowly cropped image only after removing unrelated account context.

When to stop or ask for help

Send the copied text, identifier and display-context observation through a verified route, leaving the technical cause open.