Before anyone reads your headline, your value proposition or your company name, they will see a banner asking permission to use cookies. It is the real first impression of your website, and yet it is almost always designed as a mere formality: a generic rectangle, colours that clash with the brand, a big "Accept all" button and a tiny grey "Reject" one hidden on purpose to nudge people towards the easy click. That asymmetry, besides being a poor experience, is illegal under several interpretations of European data protection rules: rejecting must be just as easy as accepting.
What the regulation actually requires (no jargon)
The core idea is simple: the user must be able to say no with the same effort as saying yes, without having to navigate several menus to find the reject button. Accepting all cookies cannot be the only visible option, nor the most visually prominent one over the rest.
How to design it so it does not feel like an obstacle
Banners that generate the least visual friction tend to be modest in size, consistent with the rest of the site's colours and typography (not a generic element slapped on top), with the two main buttons ("accept" and "reject" or "customise") carrying equal visual weight. A banner that blends with the design signals the brand took the trouble to care even about that mandatory detail.
The mistake of blocking the whole screen unnecessarily
Many websites darken and block the entire background until the user decides, preventing them from even reading the page headline to decide whether to stay. A smaller banner, at the bottom, that does not block reading the content while deciding, tends to create a better first impression while still meeting the same legal requirements.
What happens technically when someone rejects
Rejecting should not simply mean hiding the banner: analytics and advertising tools must genuinely stop loading, not keep running in the background ignoring the decision. Checking this with the browser's developer tools, watching what network requests fire after clicking "reject", is the only reliable way to confirm the rejection is respected technically and not just visually.
Frequently asked questions
Can I simply skip the cookie banner if my website is small?
No, the obligation does not depend on business size but on whether non-essential cookies are used (analytics, advertising, social media); if you use them, you need consent regardless of your size.
Does the banner have to appear on every visit?
Not if the user has already given consent previously and that consent is stored correctly; it should only reappear if the validity period expires or the third-party services used change.
Can I customise the design with my brand colour without a legal problem?
Yes, as long as the visual balance between accepting and rejecting is kept; the brand colour is not the problem, the uneven visual hierarchy between the two options is.