Testing a QR landing page from a television distance

Test the whole path from the viewer’s seat: watch the finished ad on a television, scan its code with a phone, open the page and try the promised action. A code that scans in an artwork file may fail in the placement, and a successful scan may still land on a broken or unhelpful page.

Check the code as delivered

Request a preview that reflects the booked format and screen treatment. Establish whether the platform generates the code or it is part of the supplied creative.

For generated codes, check the preview to establish which devices are eligible and when the code appears. Confirm these details with the supplier.

From a normal seat, see whether the code and instruction can be found and read before they disappear. If the code is in the artwork, preserve its clear border: DENSO WAVE specifies a four-module quiet zone.

Scan the rendered version, because scaling or overlays can affect it. A test at one distance establishes only what worked in that setup; it cannot supply a universal TV code size or display time.

Follow the phone journey

Record each stage separately: code displayed, camera recognised it, browser prompt accepted, intended page loaded, promised action completed. Try ordinary phones under the viewing conditions relevant to the placement. If a redirect is involved, verify its final page and any campaign parameters.

The page should immediately confirm the advertised product or offer. Try its main action without prior site knowledge. For a form, check labels, required fields, errors and a clear completion state. For a product page, check that viewers can find the advertised item and important conditions.

Touch controls should be easy to use; WCAG 2.2’s target-size criterion sets a 24 by 24 CSS-pixel minimum for pointer targets, with specified exceptions. That criterion concerns web controls, not the QR symbol on the TV.

Key Accessibility and Design Guidelines

Compare experience with reporting

Verify that analytics receives the intended campaign parameters. Keep platform scans, page visits and completed actions as separate measures; a scan alone does not establish that the page loaded or an action was completed.

Record any failure by stage and note the device, preview version and viewing conditions. After a fix, repeat the affected journey. Approve the creative only after those checks pass.