What it means
A dark pattern review tests whether interface structure, language, defaults, repetition, friction, or visual emphasis steers people away from a free and informed privacy choice.
Why it matters
Manipulative design can invalidate consent, undermine rights, and create distrust even when every required control is technically available.
Practical focus
- Compare accept and decline paths for prominence, steps, language, timing, reversibility, and consequences.
- Review defaults, bundling, urgency, nagging, obstruction, confirmshaming, hidden information, and account-deletion friction.
- Use independent design review, usability evidence, telemetry, complaint trends, and post-launch testing to identify actual effects.
- Preserve this evidence: Retain annotated screens, decision rationale, legal and design reviews, usability findings, telemetry, complaints, remediation, and retest results.
- Exercise this failure scenario: The interface presents “accept all” immediately but buries equivalent refusal behind multiple screens and emotionally loaded language.
Common mistakes
- Using the label Dark Pattern Review without defining scope, ownership, decision authority, and the exact data, systems, people, or process affected.
- Treating a policy, contract, diagram, dashboard, or tool demonstration as proof that Dark Pattern Review operates consistently in production.
- Closing work without retaining the evidence needed to reconstruct the decision and verify the intended control outcome.
- Testing only the normal path and never rehearsing the failure condition: The interface presents “accept all” immediately but buries equivalent refusal behind multiple screens and emotionally loaded language.
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: