--- name: verify-install description: Verify a Cookie Compliance consent banner actually blocks trackers before consent on a site that already has it. Use after installing a banner, when asked "is the banner working", "check the consent banner", "verify the cookie banner blocks trackers", or before reporting any Cookie Compliance install as done. --- # Verify the Cookie Compliance banner is actually blocking A banner that is merely visible has not been verified. Verification means proving trackers do not run before the visitor consents, then proving they do run once the visitor allows them. Use a fresh browser profile or private window. If you drive a browser with automation, **hide `navigator.webdriver` and use a normal desktop user agent**, because the widget deliberately doesn't run for automated or headless browsers, and you'd wrongly conclude the banner is missing. **Location matters:** with region rules on, the visitor's region decides whether the banner shows and whether it blocks. Test from a region under the strictest rule (for example the EU), or confirm region rules are off. Otherwise a missing banner may be correct, and a pass may not hold for EU visitors. | # | Check | Pass | |---|---|---| | 1 | **Screenshot** the page on first load (desktop and mobile width) | The banner is visible. No badge reading "Hu-manity PREVIEW — not active consent management". | | 2 | **Page source** | The snippet is the first script in ``, without `async`/`defer`, on the homepage **and** an inner page. No `previewMode` anywhere. For a v2 app, the script `src` contains `/v2/hu-banner.min.js`. | | 3 | **Before any click** | No tracking cookies (for example `_ga`, `_gcl_au`, `_fbp`) and no data hits (for example `google-analytics.com/g/collect`, `facebook.com/tr`). A tracker's script **file** in the HTML may still download (the browser starts fetching `