Extension Pro
Dark Patterns Detector
Identify manipulative consent banner designs that nudge users into accepting non-essential cookies.
A consent banner can make acceptance easy and rejection hard even when both choices technically exist. ConsentScope Pro checks supported interface signals, such as the presence and presentation of likely accept and reject controls, to identify designs that deserve review.
The detector uses DOM and text heuristics. It can misidentify a button, miss a translated label or fail to inspect an embedded interface. A finding is a prompt to test the real interaction, not proof of the designer's intent or a legal decision.
Keep interface fairness and technical enforcement in the same audit. A clear Reject button is useful only if the implementation also respects the resulting choice.
Start with the actual visitor path
Open a fresh session at the viewport you want to test. Record whether the banner is fully visible, whether the page scrolls behind it and whether another popup covers part of the choice. Desktop screenshots cannot establish how the same interface behaves on a narrow phone screen.
Use the keyboard as well as a pointer. Can you reach Reject and preferences in a sensible order? Is the focused control visible? These are manual checks that should accompany the automated result, not capabilities you should assume the detector has already verified.
Turn a visual flag into an observable finding
| Potential issue | Manual check | Evidence to retain |
|---|---|---|
| Reject not detected | Look for a translated label, link or second-layer control | The actual path and number of steps |
| Uneven visual prominence | Compare controls in the tested viewport | A screenshot and the relevant styling |
| Unexpected preselection | Open preferences and inspect optional choices | State before the visitor changes anything |
| Choice changes but tracking continues | Compare requests and storage after saving | Consent action and subsequent browser activity |
A missing detector match does not necessarily mean a missing control. For example, a custom label may not match the supported vocabulary. Conversely, finding a button with 'Reject' in its text does not prove that it rejects all optional purposes. Click through the actual flow and record the outcome.
Illustrative case: a visible link with a hidden consequence
Imagine a banner with a large Accept button and a small preferences link. The preferences panel contains rejection, but opening it also starts an optional analytics service. There are two separate issues to investigate: the effort needed to refuse and the code path that starts collection. This is a hypothetical review scenario, not a claim about a particular CMP.
Give the interface issue to the design owner and the loading issue to the implementation owner, with linked evidence. Fixing the button styling would not resolve the analytics behavior. Use the DevTools panel to preserve the sequence while you test the redesign.
Review the correction in the same conditions
Repeat the original viewport, language and session state. Then test another likely visitor environment where the layout could differ. A fix that exposes Reject on desktop but leaves it below the fold on mobile is incomplete for the mobile scenario.
The cookie banner review guide covers wording and choices in more depth. Pair that review with the passive cookie audit and manual interaction checks. Present the results as documented observations, without claiming the tool can infer manipulation or certify consent.
How it works
Open the banner in the exact viewport and language you want to review.
Run the detector and inspect the controls associated with each finding.
Test the identified accept, reject and preference paths manually.
Check the resulting cookies and requests, then repeat the review after the interface changes.
Key benefits
Visible design signals
Spot choices that may be hard to find or distinguish.
Focused UX review
Use observations to guide a real interaction test.
Document a specific issue
Describe the control, viewport and steps needed to reproduce it.
Who is it for
UX designers
Review whether accepting, rejecting and changing preferences are understandable.
Legal teams
Use flagged interface observations as inputs to a separate legal assessment.
Compliance officers
Add banner interaction checks to a pre-launch review.
Frequently asked questions
Does the detector judge whether consent is legally valid?
Will it recognize every language and custom banner?
Does an accessible Reject button prove tracking is blocked?
Unlock Dark Patterns Detector with ConsentScope Pro
Extension Pro provides lifetime access to the paid browser features. Monitor and Agency are separate subscriptions for cloud monitoring. Compare the plans for your workflow.
View Extension Pro