HighChecked on every planEU
No “Reject” on the first layer
Does a cookie banner need a “Reject all” button?
In practice, yes. EU regulators expect saying no to be as easy as saying yes. Put “Reject all” on the first screen, next to “Accept all”. Hiding it behind “Settings” has led to fines.
18%of 168 European shops did this (30)
No. 1most common high problem in the study
Why it matters
European regulators consider consent invalid when refusing is harder than accepting. This exact pattern has triggered some of the largest cookie fines on record.
How to fix it
- Add a “Reject all” (or “Only necessary”) button next to “Accept all”.
- Give it the same size, weight and contrast as the accept button.
- Keep “Customize” as a third option, not a replacement for rejecting.
Steps for OneTrust
- Open Cookie Consent, then Setup, then Templates, and edit your banner.
- Turn on “Show Reject All Button”.
- Use Button layout to put it next to Accept, and give it the same look.
- Republish the script.
Steps for Cookiebot
- In Cookiebot Admin, open the Dialog tab.
- Pick the “Multilevel” type and the “Reject all / Selection / Allow all” option.
- Give Reject the same size and contrast as Allow all.
Steps for Usercentrics
- In the Usercentrics admin, open Appearance.
- On the first layer, keep the “Deny All” button on.
- Give it the same style as “Accept All”.
Steps for Didomi
- In the Didomi Console, open Consent notices and edit your notice.
- Show the Disagree button as a main button, next to Agree.
- If you cannot see that setting, use the code below.
Steps for CookieYes
- Open Content, then Cookie Notice, and turn on the “Reject All” button.
- Open Colours, then Customise colours, then Cookie Notice. Give Reject All the same colours as Accept All.
- Save and publish.