Skip to main content
Cookie Gate
Category: Consent Principles

Equal Prominence

Simply put

Equal prominence is a design principle requiring that the options presented to users in a cookie consent interface be displayed with comparable visual weight, so that no choice is made harder to find or use than another. In practice, this typically means a button to reject cookies should be as easy to see and click as a button to accept them. The available evidence does not provide authoritative sources defining this term in the cookie consent context, so this description reflects the general concept rather than a sourced definition.

Formal definition

In the context of cookie consent, equal prominence refers to the presentation of consent choices (for example, accept and reject controls) with equivalent visual and interactive salience, such that a user is not steered toward a particular option through design asymmetries in size, color, contrast, placement, or the number of clicks required. It is generally invoked in relation to the requirement under EU and UK frameworks that consent be freely given and unambiguous, where certain data protection authorities have taken the position that making acceptance markedly easier than refusal may undermine the validity of consent. The precise expectations attached to this principle vary by jurisdiction and by evolving regulatory guidance, and no single design pattern guarantees compliance; legal assessment of a specific interface remains necessary. Note: the evidence packet provided does not contain sources addressing equal prominence in the cookie consent or data protection sense, and this definition should be validated against applicable regulatory guidance before reliance.

Why it matters

Equal prominence sits at the heart of the debate over whether cookie consent is genuinely freely given. Under EU and UK frameworks, consent must be freely given, specific, informed, and unambiguous, and design choices that steer users toward acceptance can undermine that validity. When a prominent, brightly coloured accept button sits alongside a faint, buried, or multi-click path to reject, the resulting agreement may not reflect a real choice, and certain data protection authorities have taken the position that such asymmetries can call the lawfulness of the consent into question.

For organizations operating consent interfaces, the principle matters because it is one of the practical touchstones regulators and complainants use when assessing whether a banner nudges users through so-called dark patterns. An interface that technically offers a reject option but makes it markedly harder to find or use than the accept option may be treated as non-compliant in some EU jurisdictions, even if a refusal control exists. Because expectations vary by jurisdiction and by evolving guidance, equal prominence is best understood as a risk-reduction design norm rather than a fixed rule with a single correct implementation.

It is important to be clear about the limits of what can be stated here. The evidence available does not include authoritative sources defining equal prominence in the cookie consent or data protection sense, and no specific enforcement decisions, fines, or figures can be attributed on the basis of this material. Any interface should be assessed against the applicable regulatory guidance for the relevant jurisdiction before relying on a particular design as compliant.

Who it's relevant to

Web developers and UX designers
Those building consent banners and preference centres implement equal prominence in concrete design decisions about button size, colour, contrast, placement, and click count. Because the principle is about comparable salience rather than a fixed pattern, developers typically work alongside legal or privacy teams to translate the norm into a specific interface.
Privacy officers and data protection professionals
These practitioners assess whether an organization's consent interface supports valid, freely given consent under EU and UK frameworks. Equal prominence is one of the practical criteria they use when reviewing banners for design asymmetries that could be characterised as steering or dark patterns, while recognising that requirements vary by jurisdiction.
Legal counsel and compliance teams
Counsel advising on cookie consent may treat equal prominence as a risk factor in evaluating whether consent is unambiguous and freely given. Because expectations depend on evolving regulatory guidance and no design guarantees compliance, legal assessment of the specific interface against applicable authority remains necessary.
Marketing compliance teams
Marketing teams that rely on analytics and advertising cookies have an interest in maximising valid consent, but designs that make acceptance markedly easier than refusal may undermine the lawfulness of the consent they obtain in EU jurisdictions. Equal prominence helps balance measurement goals against the requirement for a genuine user choice.

Inside Equal Prominence

Symmetry of choice
The principle that the option to accept cookies and the option to reject them should be presented with comparable visual weight, so that neither choice is unfairly favoured. In most EU and UK guidance, an 'Accept All' button should not be more prominent, easier to find, or require fewer clicks than a 'Reject All' equivalent.
Visual and design parity
Covers factors such as button size, colour, contrast, positioning, and font. Equal prominence is generally assessed by whether the design nudges users toward consent. Note that this is a matter of regulatory interpretation and design review rather than a fixed technical specification.
Interaction cost parity
The number of steps or clicks required to reject cookies should typically be no greater than the number required to accept them. Burying the reject option behind additional layers or settings menus is widely viewed as undermining freely given consent under the GDPR.
Link to valid consent
Equal prominence supports the GDPR requirement that consent be freely given and unambiguous. It is relevant to the ePrivacy rules on placing cookies and to the GDPR standard for any subsequent processing of personal data, but satisfying equal prominence alone does not establish that all consent conditions are met.
Jurisdictional scope
Equal prominence expectations are most developed in the EU and UK, where regulators have addressed deceptive interface design. Under US state frameworks such as the CCPA/CPRA, which often rely on opt-out mechanisms and signals like Global Privacy Control, the emphasis and requirements differ.

Common questions

Answers to the questions practitioners most commonly ask about Equal Prominence.

Does equal prominence mean the 'Accept' and 'Reject' buttons have to look absolutely identical?
No. Equal prominence is generally understood to mean that declining consent should be as easy and accessible as accepting it, not that the two options must be pixel-for-pixel identical. Regulators in several EU jurisdictions have focused on whether design choices, such as colour, size, placement, or the number of clicks required, make rejecting materially harder than accepting. Minor stylistic differences may be acceptable provided they do not nudge users toward consent or create a meaningful imbalance. Because guidance and enforcement positions vary between authorities and continue to evolve, you should treat this as a design principle to apply in context rather than a fixed rule about button appearance.
If I offer a clearly visible 'Accept All' button and put the reject option behind a 'Manage settings' or second layer, does that satisfy equal prominence?
Often it does not. A common concern raised by data protection authorities in the EU is that requiring users to open a settings menu or navigate additional layers to decline, while consent can be given in a single click, can undermine the requirement that consent be freely given and can be seen as a form of dark pattern. In several EU jurisdictions the expectation is that a reject option be available at the same layer and with comparable ease to the accept option. That said, interpretations differ between regulators, so whether a particular multi-layer design is acceptable depends on the specific facts and the applicable national guidance. This entry does not resolve those contested points; it describes the general direction of concern.
Where should the reject option be placed relative to the accept option on a consent banner?
As a general implementation approach in EU-facing designs, placing accept and reject options together on the same layer of the banner, with similar visibility and requiring a comparable number of interactions, tends to align with the equal prominence principle. Practices such as hiding the reject option below the fold, in a less noticeable location, or only within a secondary menu are more likely to attract scrutiny. Exact expectations can differ between the EU, the UK, and other regimes, and between individual data protection authorities, so confirm against the guidance applicable to your users' jurisdictions and seek legal review for borderline designs.
Can I use colour and contrast to make the accept button stand out more than the reject button?
Using colour, contrast, or emphasis to make accepting more visually attractive than rejecting is one of the design patterns that regulators in several EU jurisdictions have flagged as potentially undermining freely given consent. The safer general practice is to avoid styling that steers users toward acceptance, for example by giving both options comparable visual weight. Because there is no universal, quantified standard for what counts as an impermissible difference, and because interpretations evolve, treat conservative, balanced styling as risk-reducing rather than as a guaranteed safe harbour. Legal judgment remains necessary; a design tool or CMP setting alone does not establish compliance.
How should I configure a consent management platform (CMP) to support equal prominence?
Many CMPs offer configuration options that let you present accept and reject controls at the same layer with comparable prominence, adjust styling, and set the number of clicks required for each choice. When configuring your CMP, you can generally use these settings to align the interface with the equal prominence principle, and you should retain consent logs that reflect the choices offered. However, a CMP supports compliance but does not replace legal judgment: the default templates provided by a vendor may not match the expectations of every jurisdiction, so review the resulting user experience against the guidance applicable to your audiences.
Does equal prominence apply differently under US state privacy laws than under EU law?
Yes, the context differs. The equal prominence concept is most closely associated with EU-style consent, which relies on prior opt-in consent that must be freely given, specific, informed, and unambiguous under the GDPR, with the placing of cookies governed by the ePrivacy regime. Several US state frameworks, such as those in California, instead rely substantially on opt-out mechanisms and recognition of signals like Global Privacy Control, so the design questions there often centre on making opt-out choices clear and honouring those signals rather than on balancing accept-and-reject buttons in the same way. Because obligations vary between the EU, the UK, and individual US states, apply equal prominence according to the framework governing the relevant users rather than as a single universal standard. The precise requirements of each US state law are outside the scope of this entry.

Common misconceptions

Equal prominence only means the accept and reject buttons must be the same colour.
Colour is one factor, but equal prominence is generally assessed holistically, including button size, positioning, wording, contrast, and the number of clicks required. A reject option that matches colour but is hidden behind extra layers may still be considered non-compliant in EU and UK practice.
Providing a reject option somewhere in the settings satisfies equal prominence.
In most EU jurisdictions, requiring users to open a secondary settings menu to reject while offering one-click acceptance is widely regarded as failing the standard, because it increases the interaction cost of refusing and may undermine freely given consent.
Achieving equal prominence makes a consent banner fully compliant.
Equal prominence is one element of valid consent, not a guarantee of compliance. Consent must also be specific, informed, and unambiguous, cookies should generally not be set before consent, and non-essential technologies such as pixels, SDKs, and fingerprinting fall within the same rules. A CMP or design pattern supports compliance but does not replace legal judgment.

Best practices

Present 'Accept All' and 'Reject All' options at the same interface layer, with comparable size, colour, contrast, and positioning, so neither choice is visually favoured.
Ensure rejecting cookies requires no more clicks or steps than accepting, avoiding designs that bury the reject option in secondary menus.
Review banner design against relevant EU and UK regulatory guidance on deceptive patterns, and document the design rationale as part of your consent records.
Confirm that non-essential cookies and similar technologies (pixels, local storage, SDKs, fingerprinting) are not set until a clear affirmative action is taken, since equal prominence supports but does not by itself establish valid consent.
Adapt your approach to the applicable jurisdiction, recognising that opt-in prominence expectations in the EU and UK differ from opt-out and signal-based mechanisms under US state laws such as the CCPA/CPRA.
Treat CMP templates and defaults as a starting point only, and validate their design and behaviour with qualified privacy or legal review rather than assuming any tool guarantees compliance.