Dev.to WebDev 🛠 Dev 👁 0 📖 4 min read

What EU regulators actually look at in a cookie banner

I spent the last few weeks looking at cookie banners on a lot of small business websites. Almost all of them had one. Very few would survive a careful look. The good news: you don't have to guess what "careful" means. I

I spent the last few weeks looking at cookie banners on a lot of small
business websites. Almost all of them had one. Very few would survive a
careful look.

The good news: you don't have to guess what "careful" means. In January
2023 the European Data Protection Board published the report of its Cookie
Banner Taskforce, where the national authorities wrote down which banner
designs they look at and how they see them. It's short and readable. Below
are the points from it you can actually check on your own site, plus a
couple from the EDPB consent guidelines. For each one: what it means and
how to look for it in five minutes.

Quick disclaimer: I'm a developer, not a lawyer. The report itself says
the authorities decide case by case. Treat this as a list of things to
look at, not a verdict.

1. Is there a way to say no on the first screen?

If the banner offers "Accept all" and the only way to refuse is hidden
behind "Settings", that's the first thing the report talks about (paras 6
to 8). The vast majority of authorities saw a banner with no reject option
on any layer as not giving valid consent. Whether reject has to be on the
very first layer is where they differ, but "Reject all" next to "Accept
all" is the safe and common answer.

Check: open your site in a private window. Can you refuse with one click,
without opening anything else?

2. Does "reject" look like a button?

A big coloured "Accept all" button next to a small grey "continue without
accepting" link in the text is the classic. The report names a reject
option that only exists as a link inside the banner text, without enough
visual weight, as an example where consent isn't valid (paras 13 and 14).
Same if reject sits outside the banner, for example only in the footer.

Check: squint at the banner. Do both choices look like things you can
click, with roughly the same visual weight?

3. Can you read it?

Colours and contrast are judged case by case (paras 15 to 19), but the
report calls out the obvious case: a reject button whose text barely
stands out from the background. A handy yardstick is WCAG: 4.5:1 for
normal text, 3:1 for large text.

Check: right-click the reject button, Inspect, and look at the contrast
ratio Chrome shows in the colour picker. Most banner tools let you set
the button colours; giving reject the same style as accept fixes this and
point 2 at once.

4. Are any boxes ticked by default?

Open the settings layer. If "Statistics" or "Marketing" is already
switched on, that's a pre-ticked box, and pre-ticked boxes don't count as
consent (paras 9 and 10, and the CJEU Planet49 ruling). Only strictly
necessary cookies can be on by default, usually shown as a locked switch.

Check: click "Settings" and look at every toggle before touching anything.

5. Does it say "legitimate interest" anywhere?

Common in banners that use the IAB framework: next to each purpose
there's a second toggle labelled "legitimate interest", switched on. For
setting or reading cookies, legitimate interest isn't a basis you can use,
consent is (paras 20 to 25, Art. 5(3) of the ePrivacy Directive).

Check: in the settings, look for the words "legitimate interest" or
"berechtigtes Interesse". If they're there, your banner tool usually has a
switch to turn them off for cookie purposes.

6. Can people change their mind later?

After clicking "Accept all", the banner disappears. Now try to undo that.
The report expects an easy way to withdraw, like a small floating icon or
a link at a place people know, such as the footer (paras 31 to 35), and
the GDPR says withdrawing must be as easy as giving consent (Art. 7(3)).

Check: accept everything, go to another page, and try to reopen the
cookie settings without clearing your browser data. If you have to dig
through the privacy policy, it's probably not "as easy".

7. "By continuing to browse, you agree..."

Still around more than you'd think. Scrolling or simply using the site is
not a clear affirmative action, so it can't be consent (EDPB consent
guidelines 05/2020, para 86). The same goes for wording that suggests the
site can only be used if you accept (para 13 of the report).

Check: read your banner text out loud. If it says or implies that using
the site means agreeing, rewrite that sentence.

8. Does it say what the cookies are for?

Consent has to be informed. A banner that just says "We use cookies" and
nothing else doesn't tell anyone what they're agreeing to (paras 12 and
13). It doesn't need to be long, "for statistics and advertising" already
answers the question.

Check: could someone tell from the first layer alone what happens if they
click accept?

9. And the boring part: does reject actually block anything?

All of the above is about how the banner looks. None of it matters if
the analytics tag fires before anyone clicks, or keeps firing after
"Reject". That's Art. 5(3) of the ePrivacy Directive, and it's the most
common problem I see.

Check: private window, DevTools, Network tab, reload, don't touch the
banner. Anything going to google-analytics, facebook, tiktok and friends
at this point loads without consent. Then click reject and reload again.

One thing this list can't do

From the outside you can't tell whether a cookie is really "strictly
necessary" or just labelled that way (paras 26 to 30). That part needs
someone who knows what each cookie does.

If you'd rather not click through this by hand

Doing these checks on one site takes maybe ten minutes. Doing them again
after every plugin update is the annoying part. I built a scanner that
goes through all of the points above automatically, including opening the
settings and coming back after accepting, and shows the exact setting to
change. The list of what it checks, with the paragraph numbers, is here
if you want to compare notes:
https://konformia.at/en/guides/cookie-banner-requirements

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.