What "Equal" Means for Accept and Reject Buttons, Per the ICO
A big green "Accept all" next to a small grey "Manage options" link is not two equal choices. The ICO's cookie guidance says that where you offer an "accept all" button, you should offer a "reject all" button, or equivalent, with the same prominence. That is guidance, not statute, so it is worth being clear about what "same" is being asked to mean.
Where the rule comes from
The legal base is regulation 6 of PECR: storing or reading information on a device needs consent, unless an exemption applies. PECR borrows its definition of consent from UK GDPR, so it must be freely given, specific, informed and unambiguous, with a clear affirmative act.
The "equal buttons" part is the ICO's interpretation of that standard. It is regulator guidance, not a court ruling. You can read it on the ICO cookies and similar technologies page.
My reading: consent that is easy to give and awkward to refuse is not really freely given. Whether a particular banner crosses the line depends on the whole design, so treat what follows as a checklist, not a verdict.
What equal prominence means in practice
"Prominence" is a design word, so it breaks down into measurable things. A banner can fail on any one of them while looking fine at a glance.
- Size: the same width, height, padding and font size.
- Styling: the same fill, border and contrast. One solid, one outline-only is a nudge.
- Position: both on the first layer, side by side, in the same visual group.
- Effort: one click to accept means one click to reject.
- Wording: "Reject all" is clear; "Continue without accepting" in tiny text is not.
Notice what is not on that list: a requirement that the banner exists at all. If you only set strictly necessary cookies, you need no consent and no banner.
A markup version of "equal"
The simplest way to guarantee equal styling is to make it impossible to style them differently: one class, one rule.
<div role="dialog" aria-labelledby="cb-title" class="cb">
<h2 id="cb-title">Cookies on this site</h2>
<p>We would like to set analytics cookies. Your choice is stored for 6 months.</p>
<div class="cb-actions">
<button type="button" class="cb-btn" data-consent="all">Accept all</button>
<button type="button" class="cb-btn" data-consent="none">Reject all</button>
</div>
</div>
.cb-actions { display: flex; gap: 1rem; }
.cb-btn {
flex: 1 1 0;
padding: 0.75rem 1rem;
font: inherit;
font-weight: 600;
background: #ffffff;
border: 2px solid #1a1a1a;
}
Both buttons share .cb-btn, so there is nothing to drift apart in a later redesign. The flex: 1 1 0 forces equal width whatever the label length.
The detour: why the "default" button is a trap
Quick aside, because it catches people out. Many consent tools ship a "primary" button style and a "secondary" one, and the accept button gets primary by default.
Nobody decided to nudge anyone; a theme variable did it. So the fix is a test, not good intentions. Render the banner in a headless browser, read the computed styles of both buttons, and fail the build if they differ.
const props = ["width", "height", "backgroundColor", "borderWidth", "fontSize"];
const style = (el) => getComputedStyle(el);
const [a, b] = document.querySelectorAll(".cb-btn");
for (const p of props) {
if (style(a)[p] !== style(b)[p]) throw new Error("buttons differ on " + p);
}
It will not catch everything, such as a faded label, but it catches the accidental drift that causes most real failures.
Things that quietly undo the buttons
Even with matching buttons, the surrounding design can tilt the choice. Check these:
- Pre-ticked toggles on a second layer. Consent needs an affirmative act, so defaults must be off.
- A banner that blocks the page for "Reject" but lets "Accept" dismiss quickly, for example by an extra confirmation step.
- Cookies set before the user clicks anything. No amount of button design fixes that.
- Reject that reappears on every page load while Accept is remembered for a year.
- Withdrawal that is harder than giving consent. A persistent "Cookie settings" link in the footer is the usual answer.
Is a "Reject all" button strictly mandatory?
Not in so many words. The guidance describes the reject option as something you should provide alongside "accept all", and says the alternative is giving the user an equally easy way to refuse. If your first layer has no "accept all" at all, just per-category choices with all off by default, the symmetry problem largely disappears.
In practice, two plain buttons is the least arguable design, and it is cheap to build. I would not spend effort looking for a cleverer layout that a regulator might read differently.
What I would check before shipping
- Open the site in a clean profile and check the network tab: nothing non-essential should be set before a choice.
- Click "Reject all" and confirm those cookies still never appear.
- Compare the two buttons side by side at phone width, where layouts often collapse unevenly.
- Find the withdrawal route, and count the clicks.
Enforcement and the exact exemptions have moved since the Data (Use and Access) Act 2025, so check the current ICO page before relying on any detail here. This is general information, not legal advice.