Check explainer
Consent simulation
The deep scan drives the cookie banner automatically and compares the accept state with the reject state.
- note
- ok
What we check
Drives the cookie banner automatically (Accept-all and Reject-all) and compares both states.
Why it matters
The deep scan drives the cookie banner automatically and compares the accept state with the reject state.
Common causes
- The CMP renders the banner in an iframe or shadow root the scanner cannot reach (some Sourcepoint and custom builds).
- The buttons carry neither known selectors nor unambiguous labels, custom UIs without standard wording stay undriveable.
- Bot protection (a Cloudflare challenge, for instance) stops the headless browser before the banner appears.
- The page loads slower than the scan's time budget, the simulation aborts in a controlled way.
How to fix it
If "not possible": check whether an interactive CMP exists, otherwise rely on the static-scan findings.
What does a failing Consent simulation finding mean?
The deep scan drives the cookie banner automatically and compares the accept state with the reject state. If "not possible": check whether an interactive CMP exists, otherwise rely on the static-scan findings.
How do you fix Consent simulation?
If "not possible": check whether an interactive CMP exists, otherwise rely on the static-scan findings.