A caption that covers essential action needs a concrete segment report
A caption that covers an essential action creates an information conflict that needs a specific scene report.
Guide topics
Guide, language & time
Keep programme IDs, language components, dates, time zones and shared information clear.
135 focused articles. Examples are illustrative; applicability and primary references appear on each guide.
Accessibility Needs
A caption-timing report should identify the exact programme edition
A caption-timing complaint needs the exact edition and a reference moment before it can support a useful correction.
A control that cannot be reached needs a navigation-path report
A control that cannot be reached needs a report of the navigation path and missing function, not a screenshot of its appearance alone.
A dense scene may need a described edition rather than ordinary narration
A dense scene may need a specifically prepared described edition when essential visual information cannot fit comfortably into ordinary audio gaps.
A descriptive transcript can meet a different need from dialogue text
A descriptive transcript adds essential visual information that a dialogue-only text record may leave out.
A live caption correction should be recorded as a sequence
A live caption correction is a sequence of observations, so the first displayed words and their later correction should be recorded separately.
A timeout can interrupt an accessibility task without proving an account failure
A timeout can interrupt a reading or input task without establishing that the account itself has failed.
A transcript request should identify live or completed content
A transcript request should say whether the viewer needs text during the live occurrence or can use a completed record later.
An animated row needs an available way to stop its motion
An automatically moving row can interrupt reading, so a useful report identifies the motion and the task it prevents.
An audio-only programme needs a text alternative rather than visual description
An audio-only programme calls for access to its sound information; asking for visual description does not address that information gap.
An error needs readable words rather than only a colour cue
An error needs readable words identifying the problem; a colour change alone can leave the viewer unable to decide what to do next.
Ask whether essential on-screen text is conveyed in the accessible edition
Essential on-screen words need to be conveyed in the access format a viewer actually uses, rather than merely existing somewhere in the picture.
Speaker identification can matter when the speaker is off screen
Speaker identification can carry essential meaning when a voice comes from outside the picture.
Epg Matching
A changed event listing needs a new source time
An organiser’s revised announcement should be compared as a new source time, not treated automatically as a clock error.
A channel number is not its programme-guide identity
The number used to find a channel in a list does not establish its guide identity.
A different household profile changes the comparison context
A household comparison needs the profile context without revealing the person behind it.
A double episode can occupy one listing or two
A double episode can occupy one guide slot or two without those presentations alone identifying a fault.
A familiar logo is weak evidence for the current guide match
A familiar channel logo should support, not replace, a check of the current service and schedule.
A favourite can retain an older service reference
A saved favourite should be compared with the current service entry before its guide problem is generalised.
A guide ends halfway through the viewing day
A guide that stops midday should be reported as a coverage boundary, not automatically as a broken clock.
A guide filter can hide records that still exist
An empty filtered view should be distinguished from absence of the underlying programme records.
A live overrun can displace the next listed programme
A live overrun can make the next listing look wrong without establishing a timezone fault.
A matching series title can still identify the wrong episode
A series-title match should be followed by an episode check when the story or description differs.
A missing synopsis is different from a missing programme
A missing synopsis should be reported as a missing detail when the programme title and time are still present.
A newly visible description is not proof of full-day coverage
One newly visible programme description is a narrow success, not proof that every expected listing has arrived.
A plus-one service needs its own schedule comparison
A time-shifted service should not be repaired by moving the schedule of every unrelated channel.
A programme badge does not prove the selected track exists
A programme badge is useful context, but it should be checked against the specific accessible or language edition needed.
A regional edition shares its parent network name
Keep the regional edition attached to the network name when a local bulletin is the programme you need.
A remembered identifier now points to a different service
A remembered identifier should be checked against the current service instead of treated as permanent proof.
A repeat label does not establish replay availability
A repeat indicator describes programme history, not a promise that an earlier transmission can be replayed.
A special episode does not establish ordinary season numbering
A special episode should keep its explicit label instead of being forced into an assumed season sequence.
Accents and punctuation can mislead a suggested channel match
Removing accents or punctuation can turn a convenient suggestion into the wrong service match.
An age category is not a programme identifier
An age or category label can help describe a programme, but it does not uniquely identify the work or edition.
An original series and a remake can share a translated title
Keep the year or distinguishing edition when an original series and a remake share a translated title.
Changing title case is not a reason to alter an identifier
A cosmetic title-case change should not trigger an unverified change to an opaque reference.
Compare two consecutive programme boundaries before accepting a match
Two consecutive programme boundaries provide a stronger identity check than one familiar title.
Copied identifiers contain invisible surrounding spaces
When a copied reference looks right, preserve its exact form before testing a carefully scoped correction.
Future programmes exist while the current window is empty
An empty current slot can coexist with valid future listings, so identify the gap rather than calling the whole guide absent.
Keep the approved guide source with the mapping evidence
Keep the approved guide source with the matching evidence without exposing its private address.
One channel shows the wrong programme throughout the day
A consistently wrong schedule on one service is a reason to verify identity before adjusting the clock.
Only part of a channel group has programme information
When only some channels lack listings, preserve the pattern instead of describing an all-channel failure.
Record a service change before discarding an old mapping
Record a known service change before discarding the association that previously worked.
Removing duplicate logos can erase genuine regional choices
Repeated artwork should not be used as the only rule for removing apparently duplicate channel entries.
Resolve two conflicting schedule records before applying an offset
Two conflicting schedule records need source reconciliation before their difference becomes a guide offset.
Several translated names describe one guide identity
Different translated display names can describe one guide identity without becoming separate services.
The display name changed but the guide identifier did not
A renamed display label does not automatically require a new guide association.
The same short identifier can occur in different guide sources
A short identifier can be meaningful in one guide source without identifying the same service in another.
Translated guide titles do not choose the programme audio
The language of a guide title does not tell you which audio track the programme supplies.
Two picture variants need their schedule identity checked
Two picture-variant labels may share a schedule, but the label alone cannot prove that they do.
Two playlist groups can refer to the same channel identity
A service appearing in two groups does not automatically need two independent guide identities.
Two services showing one event do not prove a shared guide
A shared event is too little evidence to decide that two services use the same schedule.
Yesterday is populated but today has no programmes
Yesterday’s populated guide proves past coverage, not that today’s window has also been supplied.
Language And Tracks
A broad language name may need a more precise programme-track label
A broad language name can leave an important programme-track distinction unresolved.
A forced subtitle segment is not the full dialogue track
A few translated signs or foreign-language lines do not establish that full dialogue subtitles are available.
A hearing-access caption label does not mean audio description
A caption track aimed at hearing access does not establish that the programme also describes essential visual information.
A language handover inside one programme needs a precise segment reference
When a programme changes spoken language mid-scene, the report needs the exact handover segment rather than a whole-programme language guess.
A live edition can differ from a later subtitled programme
A later subtitled edition does not establish what text was available during the live occurrence.
A localised title and an original title can identify one work
A localised title and an original title can identify the same work, so a title difference alone does not prove a duplicate programme.
A muted preview does not establish caption availability for a full programme
A muted preview with visible words does not establish the caption options supplied with the full programme.
A regional language tag does not establish territorial access
A regional language tag describes a language variant; it does not grant access in the region named by that tag.
A romanised title should remain attached to the original spelling
A romanised search title is most useful when it remains attached to the original spelling and programme identity.
A trailer’s language choices do not establish the feature’s choices
A trailer’s spoken and written language choices do not establish the choices offered with the feature it promotes.
An automatic language preference needs a programme-level check
An automatic language preference needs a check on the current programme because a saved preference is not a track inventory.
An original-language track and a dub are different editions
An original-language performance and a dub are different audio choices, even when both are associated with the same film title.
An undetermined language label needs observation rather than guessing
An undetermined language label records uncertainty; it is not an invitation to guess a language from a flag or programme title.
Audio description is different from ordinary commentary
A spoken commentary label does not establish that essential visual information is described for a viewer who cannot see the scene.
Automatic text needs a specific accuracy check
Automatically produced text needs a specific accuracy check where an error would change the viewer’s understanding.
Dialogue translation and accessibility captions serve different needs
Dialogue translation and accessibility captions can look similar while supplying different information to the viewer.
Keep the household profile with a language-preference observation
A language-preference observation needs the relevant household profile context without exposing the people behind the profiles.
One episode’s tracks do not establish the whole season’s tracks
One episode’s language options are evidence for that episode, not a complete inventory for the season.
Preserve accents when recording an original title
Preserving the original title’s accents and punctuation helps support distinguish a copied label from a viewer’s approximate search spelling.
Reading needs can differ even when the subtitle language is correct
Correct subtitle language is only one part of a usable reading experience.
Right-to-left programme titles should be copied without rearranging them
Copy right-to-left titles as supplied; manually rearranging letters or numbers can change the text that support needs to identify.
Sign-language interpretation is not a substitute label for captions
Sign-language interpretation and written captions are different access formats; a caption label does not establish that an interpreted edition exists.
Sound descriptions need checking beyond the spoken dialogue
A dialogue check cannot establish that a caption track also conveys meaningful sounds elsewhere in the programme.
Text already inside the picture differs from selectable captions
Text already embedded in the picture is a different observation from a selectable caption track.
The same programme on two feeds can have different language editions
The same programme on two feeds can carry different language editions, so a successful check on one feed does not settle the other.
The subtitle language can be right while the programme cut is wrong
Subtitles can be in the right language yet belong to a different programme cut or occurrence.
Two commentary tracks can share the same language label
Two commentary tracks can use the same spoken language while serving different audiences or editorial purposes.
Two scripts can represent the same spoken-language request
A spoken-language request may still need a script choice when the viewer plans to read subtitles or titles.
Unrendered title characters need a text record before a screenshot is shared
When title characters appear as boxes or replacement marks, preserve a copied text record before a screenshot becomes the only evidence.
Privacy Safe Records
A device identifier should not be posted as a public diagnostic label
A device identifier is account-related context, so a public symptom report should use a neutral device label instead of posting the full identifier.
A lost-device enquiry should ask about account actions without sharing its secrets
A lost-device enquiry should ask what account actions are available without posting the missing device’s access values in public.
A playlist address can contain more than a harmless website name
A playlist address can contain credentials or tokens beyond its recognisable domain name.
A QR code can carry account access information
A QR code is encoded data, so an account or activation QR image should not be treated as harmless decoration in a screenshot.
A relevant activation date is different from a personal identity date
A relevant activation or incident date is different from a personal identity date and should be labelled clearly in a support record.
A shared support file needs deliberate access and an end point
A support file needs a deliberate audience and a clear end to access, rather than an indefinitely public link by default.
A useful error excerpt is smaller than an entire diagnostic log
A short, reviewed error excerpt can be more useful for support than an unfiltered diagnostic log containing unrelated activity and secrets.
An accessibility request can omit sensitive health history
An accessibility enquiry can explain the function needed without including sensitive health history or another household member’s diagnosis.
An incident needs a timezone but rarely an exact home location
An incident usually needs a dated clock context for diagnosis, not an exact home address or GPS position.
An order reference is different from a checkout session address
An order reference identifies a transaction context; a checkout session address may carry access information and should not be posted as its public substitute.
Check the filename and surrounding page as well as the visible image
A safe-looking image can still disclose personal context through its filename, surrounding page or the message used to share it.
Crop a support image to the actual diagnostic area
A useful support image shows the diagnostic area with the least unrelated account or household information needed.
Keep two order enquiries distinct without exposing customer records
Two order enquiries need separate reference and status records so information from one transaction is not accidentally applied to the other.
Record the full USD total without sharing payment credentials
A billing enquiry can retain the full USD total and purchase date while excluding the credentials used to pay.
Separate a public incident summary from a private account conversation
A public incident summary and a private account conversation should contain different levels of detail.
Share one neutral reproduction case rather than the full account catalogue
A neutral reproduction case can explain a catalogue or guide problem without exposing the household’s full viewing list.
Verify the support route before answering a request for secrets
Verify the support route independently before responding to a request for account secrets or urgent payment-related action.
Time And Dates
A calendar date is not an elapsed viewing duration
A calendar date and an elapsed duration answer different questions about a viewing window.
A calendar week number needs its year and convention
A week number needs a year and a stated calendar convention before it can identify a programme date.
A calendar-month label is not a universal thirty-day interval
A calendar-month label should not be silently rewritten as a universal thirty-day interval.
A country flag cannot select a single timezone
A flag can identify a country without selecting the timezone needed for one viewer’s schedule.
A current clock comparison does not establish the historical offset
A clock comparison made today does not establish the offset that applied to an archived programme.
A half-hour offset should not be rounded to the nearest hour
A half-hour component should remain intact when an event is converted into local time.
A leap-day example needs a year that actually contains the date
A leap-day listing needs a year that actually contains 29 February before any timezone conversion can help.
A manual offset can apply an existing conversion twice
Adding a manual offset after a correct automatic conversion can create the very error being investigated.
A named timezone is more useful than today’s offset for a future event
Today’s UTC offset should not be used as a permanent rule for a future event in a named location.
A numeric day and month can be read in two orders
An ambiguous numeric date should be clarified before its programme is searched or converted.
A numeric timestamp needs its unit before it can be interpreted
A numeric timestamp needs its unit and origin before it can be treated as a programme date.
A quarter-hour component can disappear in a limited clock selector
A forty-five-minute component can reveal that a clock selector is too coarse for the intended location.
A recurring local programme and a fixed UTC event need different comparisons
A weekly local programme and a one-off UTC event express different scheduling intentions.
A reminder time does not prove that a replay will exist
A reminder schedules a viewer’s attention; it does not establish that a replay or recording will be available later.
A small live delay is not usually a whole-hour clock offset
A small difference between live pictures should be measured as observed delay before it is treated as a clock offset.
A spring clock change can make a local time nonexistent
A local clock time inside a spring-forward gap needs clarification instead of an invented conversion.
A support reply time is not the original incident time
The time a support reply arrives is separate from the time the viewing problem occurred.
A timezone abbreviation can refer to more than one place
A three-letter timezone abbreviation is a clue, not enough information to place a programme on the viewer’s calendar.
A timezone alias does not necessarily mean a second local clock
Two timezone names can refer to the same IANA rules through a compatibility link.
A UTC label and the same local clock number are different claims
The same clock number can describe different instants when one label is UTC and another is local time.
An autumn clock change can repeat the same local time
When an autumn clock repeats an hour, the local time alone may identify two possible instants.
An event time without a timezone needs clarification
A start time without a timezone is an unanswered source question, not a value that should be guessed into a conversion.
An event venue clock is not automatically the viewer clock
The clock used at an event venue is not automatically the clock a remote viewer should put in a reminder.
An impossible month-end date needs source correction rather than an offset
An impossible month-end date is a source-data problem, not a reason to add or subtract a timezone offset.
An offset sign changes the direction of a conversion
The sign in a stated numeric offset changes which instant a local clock value represents.
An overnight programme can cross a clock change
An overnight programme crossing a clock change can last longer or shorter than its wall-clock labels suggest.
Elapsed minutes can differ from the subtraction of wall-clock labels
A later instant can carry an earlier-looking local clock label during an autumn clock change.
Noon and midnight need explicit twenty-four-hour notation
Noon and midnight are clearer when recorded as explicit twenty-four-hour times with a date.
Several location records can share the current UTC offset
Several IANA location records can currently show the same offset without being redundant evidence.
Some Etc GMT names use a counterintuitive sign convention
An Etc/GMT identifier can use a sign convention that differs from an ordinary numeric timestamp offset.
The device clock can be right while the programme guide is wrong
A correct device clock does not prove that every programme listing has been interpreted in the right context.
The same city name needs its country or zone identifier
A city label without a country or recognised timezone identifier can be too vague for a reliable conversion.
Timezone conversions can move a programme to the previous or next date
Convert the date and time together: the same event can fall on the previous or following local calendar day.
Tomorrow needs the announcement’s original date
Tomorrow belongs to the announcement’s original calendar context, which may differ from the reader’s local date.
Tonight loses its meaning when a screenshot is forwarded later
The word tonight stops being a reliable date when an announcement is forwarded or reopened later.
Travelling can change the viewer clock without moving the event
Travelling can change the clock shown to a viewer while the scheduled event remains at the same instant.
Two household members can see different times for the same instant
Two household members can have different local start labels for one shared event without either schedule being wrong.