What makes a cookie notice understandable?

Start with the decision visitors face

A cookie notice interrupts a visitor who may be trying to read an article, request a quote or book an appointment. The first screen should answer a practical question: what will happen if I allow these optional technologies, and what happens if I do not? Long legal wording before that answer creates uncertainty rather than informed choice.

Use a short heading and plain summary. Say that the website uses necessary technologies to operate and may ask permission for optional analytics, preferences or marketing. Explain that visitors can accept, reject or change their choice. Do not imply that every cookie is harmless or that refusing optional tracking prevents normal access unless that is genuinely true.

Match the language to the website and audience. Avoid unexplained abbreviations, vendor names and technical descriptions on the first layer. Details can follow for people who want them. The first decision should be understandable without a law degree.

Explain categories and purposes

Categories should describe purpose, not merely technical storage. Necessary technologies may support security, shopping baskets, login or remembering a consent choice. Analytics may help understand page use. Preference tools may remember language or display choices. Marketing technologies may measure campaigns or personalise advertising.

Be accurate about what is active. If an analytics tool runs only after consent, say so. If a service places technologies through an embedded video, map, chat or payment component, include that purpose or provide a clear detail layer. Do not use “necessary” as a broad category for everything the business would like to measure.

Explain consequences in practical language. Rejecting analytics may mean the organisation learns less about page performance; it should not normally prevent reading or contacting the business. A preference choice may reset when it is refused. These details help people decide without pressure.

Make choices genuinely equal

The notice should make accept, reject and manage settings visible and understandable. A large colourful accept button beside a faint text link for rejection is not a balanced choice. Use labels that state the action, such as “Accept optional cookies”, “Reject optional cookies” and “Choose settings”.

Do not use confusing double negatives, preselected optional categories or a settings panel designed to exhaust visitors. If a choice has several layers, keep the path reversible. Someone should be able to withdraw or change optional consent without searching through the entire website.

Avoid asking for consent again on every page. Store the choice for an appropriate period, explain how it can be revisited and respect a refusal. If the website has multiple domains or embedded services, check that the setting behaves as visitors expect.

Design an accessible notice

The notice is part of the website, so keyboard and screen magnifier users must be able to operate it. Check focus order, visible focus, headings, button labels and error-free movement between the banner and settings panel. Do not trap focus or place the close button before the explanation in a way that hides the decision.

Use readable text, sufficient contrast and controls large enough for touch. Keep the first layer short enough to scan on a phone. If a banner covers content, ensure it does not obscure the only route to information or create a control that cannot be reached.

Make the state clear. A category should show whether it is on, off or unavailable, and the state must not be communicated by colour alone. Labels should remain understandable when read without surrounding decoration.

Connect notice, tools and records

The wording must match the technology behind it. Make an inventory of cookies, local storage, pixels, tags, embedded services and consent signals. Record provider, purpose, category, duration and whether data leaves the organisation’s expected region. Remove old tools that no longer serve a purpose.

Test what happens before and after a choice. Use browser storage tools or network information to see whether optional requests occur before consent. Check reject, accept and change flows separately. A polished banner is not meaningful if analytics or marketing tags load before the decision.

Keep a record of the consent state and the notice version where required by the organisation’s process. Make sure a later change to tools triggers content review and, where necessary, a new choice. Coordinate marketing, development, analytics and privacy ownership.

Help people revisit the choice

Place a persistent “Cookie settings” or privacy control in a predictable location. It should open the same settings interface and explain what changing a choice will do. Do not make withdrawal more difficult than acceptance.

Link from the notice to a readable cookie page with purposes, providers, retention and choices. Separate essential information from technical detail. Include a contact route for questions and explain how someone can raise a concern.

Review the notice after redesigns, new embeds, campaign changes and analytics migrations. Ask a person unfamiliar with the business to explain what optional cookies do, reject them and later change the choice.

Sources

• Online privacy: how to use cookies on your website · Your Europe
• Guidelines 05/2020 on consent · European Data Protection Board
• Forms Tutorial · W3C

Frequently asked

What should a cookie notice explain first?

Explain what optional technologies do, why they are used, whether they affect the visitor and which choices are available. Technical detail can follow.

Should accept and reject be equally visible?

Yes. People should be able to accept optional technologies, reject them or manage settings without being steered toward one answer.

What cookie categories are useful?

Use meaningful purpose categories such as necessary, analytics, preferences and marketing, but only when they accurately describe the tools in use.

How can visitors change their cookie choice?

Provide a persistent settings link that opens the same controls and makes withdrawal or changes no harder than the original choice.