Test the cookie choices a visitor actually sees.
Use a controlled browser journey to record banner presentation, choice paths and visible confirmation behaviour with structured answers and screenshots.
Move from written expectation to observable evidence.
A policy page alone does not show how a banner behaves on a specific journey. Repeatable observation makes it easier to compare pages, brands, regions or releases against the test framework you define.
Run the work as a controlled assessment programme.
1. Specify the pages, devices and decision paths to observe.
Specify the pages, devices and decision paths to observe.
2. Record visible banner states, preference options and resulting confirmations in a fixed questionnaire.
Record visible banner states, preference options and resulting confirmations in a fixed questionnaire.
3. Attach screenshots as evidence and route the submission through QA before release.
Attach screenshots as evidence and route the submission through QA before release.
Brief → fieldwork → review → controlled release.
1. Define the authorised site, viewport and cookie-choice scenario.
Define the authorised site, viewport and cookie-choice scenario.
2. Assessor follows the scripted choices and captures the required screenshots.
Assessor follows the scripted choices and captures the required screenshots.
3. Reviewer verifies the submission and releases the result for investigation or re-test.
Reviewer verifies the submission and releases the result for investigation or re-test.
Keep the evidence attached to the result.
The test records observable website behaviour. It does not inspect hidden browser storage unless that is separately supported and authorised, and it does not certify legal compliance.
Cookie choice journey
This diagram explains the operating sequence only; it is not a product screenshot.