If your organisation uses a consent mechanism before loading a third-party video, the resulting viewing journey needs its own acceptance test. A visitor who declines should understand what is unavailable and what other information they can use. A visitor who accepts should reach the film without a confusing second start or an unexplained blank area.
The web.dev guidance on third-party embeds explains that embedded services load resources from outside the page's own implementation. Which resources should be gated, and under what consent arrangement, is for your organisation's responsible privacy and technical owners to determine. This article concerns testing the behaviour they have approved.
Obtain the intended states in writing
Ask the website team to describe what appears before a choice, after acceptance and after refusal. Include a returning visitor whose earlier choice has been remembered. These states should be distinguishable enough that the reviewer knows whether the page is waiting for a decision or experiencing a technical failure.
Identify the material that remains available without the embed. A project description or transcript may provide a useful route, provided it accurately represents the film and is intentionally made available. Do not label a short promotional summary as an equivalent transcript merely to fill the blocked space.
Keep the wording specific. Explain that loading the video involves the identified external service if that is the approved message. Avoid vague instructions that ask visitors to enable everything or disable privacy protections just to discover what the film contains.
Follow the complete change of choice
Test accepting from the initial state, then use the approved preference controls to change the choice. Ask the implementer what should happen to an already loaded or playing video. The answer depends on the adopted policy and architecture, so record the demonstrated behaviour rather than inventing a universal technical rule.
Check whether the play control and consent control are separate. A visitor should not be left clicking a play triangle that silently waits for a decision elsewhere on the page. If two actions are required, their relationship should be clear.
Review keyboard focus and the return to the player after the consent panel closes. The visitor should be able to continue the intended task. This is especially important when the panel overlays the page or opens a new settings region.
A hypothetical blank project page
Imagine a builder's case-study page reserves a large space for a video. Visitors who decline the relevant consent option see an empty rectangle, while the team's test browser always shows the film because it already accepted.
The buyer requests a fresh-session test for each approved state. The web team supplies an explanatory placeholder and a maintained transcript link, then demonstrates acceptance leading to the playable film. The production file was not defective; the missing work was a coherent gated experience.
Accept the policy and the implementation separately
Have the responsible owner approve the consent approach and wording. Have the implementation team show that the page behaves accordingly. A functional test can confirm what happens, but it does not decide whether the chosen policy meets every applicable obligation.
Discuss the project film and companion assets with Live Images. Confirm which production deliverables are suitable, while leaving consent decisions and website implementation with the authorised specialists.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.