Redesigning your cookie banner after the ICO's 2026 guidance

Laptop on a café table showing a blurred website with a small panel at the bottom of the screen

Cookie banners are one of the most disliked pieces of design on the web, and in 2026 the rules behind them moved. The Information Commissioner's Office finalised its guidance on storage and access technologies on 29 April 2026, reflecting changes made by the Data (Use and Access) Act 2025. The headline change for designers is a new exception for analytics: if a site only collects aggregate statistics to improve itself, it may not need consent for that, as long as visitors are told clearly and can object easily. Advertising and tracking of individuals still need consent. So some banners can become simpler, and many cannot.

What actually changed

The ICO's storage and access technologies guidance replaces its older cookie guidance and covers cookies along with pixels, local storage and similar techniques. It sets out five situations where you can store or read information on someone's device without consent. The ICO calls them the communication, strictly necessary, statistical purposes, appearance and emergency assistance exceptions.

Two of these matter most for a typical business website. The statistical purposes exception covers collecting information about how the site is used with a view to improving it. The appearance exception covers remembering a visitor's choices about how the site looks or works, such as a text size or a dark theme. For both, the ICO says you must give people clear and comprehensive information about the technology and a simple, free way to object.

Which analytics fit the exception

This is where the design conversation really starts, because the exception is narrower than the word "analytics" suggests. The ICO's page on the exceptions gives examples of activities likely to qualify when you use aggregate information: page-by-page visit totals, average scroll depth, coarse location at city or region level, page loading speeds and bounce rates. It also lists things that do not: logs or recordings of individual visitors and what they did, and using the data to make inferences or decisions about people.

Two conditions catch people out. The purpose has to be the sole purpose, so a tool that measures traffic and also feeds an advertising platform does not qualify. And you cannot keep individual-level information once it has been aggregated. If you use session replay, heatmaps tied to individual visits, or analytics linked to ad accounts, plan on keeping consent for those.

Three banner patterns for three kinds of site

Aggregate analytics only, no advertising

If your audit shows only strictly necessary cookies plus analytics that genuinely fit the statistics exception, you may not need a consent pop-up at all. You still need two things on screen: clear information, and an objection route. A short, persistent notice linking to a plain-English page, with a visible "Turn off analytics" control, can do both without blocking content. Make the control work on the first click and remember the choice using the appearance or strictly necessary exceptions.

Analytics plus optional extras

Embedded video, maps and social widgets often set their own cookies for analytics or advertising. The ICO notes you can ask for consent on the pages where such content appears, or link out instead of embedding. A click-to-load placeholder ("This video is hosted by an external platform. Load video?") is often cleaner than adding another toggle to a site-wide banner.

Advertising and remarketing

If you run ad pixels, retargeting or cross-site measurement, you still need a proper consent mechanism. The design principles have not softened: no pre-ticked boxes, no hiding the refusal behind extra screens, and enough information for people to understand what they are agreeing to.

Wording that respects the reader

Most banners fail on language before they fail on law. Write the notice the way you would explain it to a customer at the counter:

  • Say what you measure and why in one sentence. "We count visits to each page so we know which guides are useful" beats a paragraph about "enhancing your experience".
  • Name the choice in the button. "Turn off analytics" or "Allow advertising cookies" is clearer than "Manage" or "OK".
  • Keep the objection or refusal as visible as the acceptance. Same size, same weight, same position on mobile.
  • Link to a full explanation for people who want detail, and keep that page up to date when tools change.

Good contrast and readable type matter here too. A grey-on-grey refusal link is a design choice that tells visitors something about the business. Our article on colour contrast and accessible design has practical checks you can apply to any notice or button.

Run a tag audit before you redesign

Do not change the banner until you know what the site actually loads. Open the site in a private window, use the browser's developer tools to list cookies and network requests, and repeat after clicking through a few key pages. Make a simple table: tool name, what it stores, who receives the data, purpose, and which exception (if any) applies. Marketing teams often discover tags from old campaigns or plug-ins nobody remembers installing.

Then agree a rule with whoever manages the site: no new tag goes live without a line in that table. The banner design is only as accurate as the list behind it.

Where to get proper advice

This is general information about design and wording, not legal advice. If your site processes data in more complex ways, or you are unsure whether a tool fits an exception, read the ICO guidance in full and speak to a data protection professional. The goal is a notice people can understand in a few seconds, backed by settings that do exactly what the notice says.

Enjoyed this? See more in the blog, or write for us.