Dark patterns in cookie banners: 7 design choices worth fixing

Dark patterns are interface choices that steer people towards a decision they might not otherwise make. In a cookie banner, that can mean hiding rejection, preselecting optional purposes or making the wording difficult to understand. A high acceptance rate does not tell you whether visitors understood the choice.

For teams serving European visitors, a useful starting point is the EDPB Cookie Banner Taskforce report. It identifies recurring problems with consent interfaces. The practical fixes below apply those concerns to everyday design decisions; they are not a claim that every layout is assessed identically in every country.

1. The rejection option is hard to find

A large “Accept all” button sits in the middle. The alternative is a faint link inside a paragraph. Visitors can technically refuse, but the interface makes them work for it.

Put acceptance and rejection where people can see both. Test the banner on a phone, where a link that looked obvious on a large monitor may disappear into the text. A colleague should be able to find the refusal route without a hint.

2. Optional categories start switched on

A visitor opens preferences and finds marketing already enabled. Saving the screen could preserve a choice they never made.

Start optional categories off where opt-in consent is required. Keep the explanation beside each control, so visitors understand what enabling it does. The EDPB report specifically rejects preticked opt-in boxes as a basis for valid consent.

3. “Accept” is a button; “reject” is a maze

Count the actions. If acceptance takes one tap but refusal takes a settings panel, several toggles and another confirmation, the two routes are doing very different jobs.

Our design recommendation is simple: offer an immediate way to reject optional cookies alongside acceptance. Keep preferences for people who want a more specific choice. Do not make preferences the obstacle everyone else has to clear.

4. Colour makes one choice almost invisible

Brand colours are fine. Disappearing controls are not. A pale grey refusal label on white can be difficult to read even when someone actively looks for it.

Use readable contrast for all choices and check keyboard focus. You can match the website without making “yes” the only obvious action. The CNIL's practical cookie recommendations discuss misleading visual emphasis in consent interfaces.

5. The words hide the purpose

“Improve your experience” could mean remembering a language preference, measuring visits or building an advertising audience. Those are different activities.

Name the purpose. For example: “We use optional analytics cookies to understand which pages people visit.” Then explain advertising separately if you use it. Only describe tools and purposes your website actually uses; a polished sentence can still be inaccurate.

6. Refusal comes with a guilt trip

“No thanks, I don't want a better website” is not a useful consent label. It attaches an argument to a choice that should be understandable on its own.

Use neutral wording such as “Reject optional” or “Manage preferences”. Keep sales language in the parts of your website where visitors expect to be persuaded.

7. Changing a choice is harder than making it

The banner disappears after acceptance. Now the visitor has to search your policy or contact support to withdraw.

Provide a persistent, clearly labelled cookie-settings control. Under GDPR Article 7, withdrawing consent must be as easy as giving it. Test the actual result after withdrawal, not just whether the settings window opens.

A better review than “did acceptance go up?”

Ask someone outside the project to complete three tasks: reject optional cookies, allow analytics only and later withdraw that permission. Watch where they hesitate. Then run the technical rejection test to check that the site follows their choices.

For styling ideas, see six cookie-banner design examples. The examples preserve clear choices while changing the visual treatment.