← Back to The Digest

The Digest / Accessibility & Privacy

The cookie banner you can see might be difficult for somebody else to use

Research found that a cookie notice can be readable by a screen reader while still making it hard to understand or refuse a choice.

By SSC Digital6 min readViews loading…
Conceptual illustration of a cookie settings panel beside a speaker and sound waves.
Original conceptual artwork for SSC Digital.

Most business websites have something familiar in common: a notice asking visitors whether they want to accept cookies.

It's often a small box at the bottom of the screen. There may be two buttons, a short explanation and a link to more settings.

For somebody using a mouse, making a choice might take a second.

But what happens when a visitor cannot see that box and uses a screen reader instead?

New research suggests this is an overlooked weakness in the way many websites handle privacy.

The interesting part is that a cookie banner can technically be readable by assistive software and still fail to give somebody a clear, understandable choice.

For a small business, that raises a useful question: does its website work properly for everybody, or does it only appear to work properly?

What the new research found

On 31 October 2026, researchers James M. Clarke and Maryam Mehrnezhad released a study investigating the relationship between cookie consent, privacy and accessibility for blind and low-vision users.

Their research examined a sample of 3,000 domains from the global Tranco website-ranking dataset. Of those, 2,061 could be reached during the automated crawl, and 1,058 displayed detectable cookie notices.

The testing was carried out between 5 and 18 May 2026, using automated browser analysis, the NVDA screen reader and accessibility testing tools. 1

The results reveal a striking difference between making a notice readable and making it genuinely understandable.

In other words, most notices could be detected or read, but far fewer clearly identified their purpose, appeared early enough in the reading sequence or gave buttons sufficiently descriptive names.

Accessibility depends on whether a person can understand the notice and act on it.

Why button wording makes a difference

Consider a cookie notice with a button labelled "Accept".

For a sighted visitor, the surrounding box may make the meaning obvious. The person can see the text, heading, background and alternative choices together.

A screen-reader user may navigate through the page differently, sometimes moving directly between buttons rather than listening to every preceding paragraph.

A button that simply says "Accept" may not explain what is being accepted.

A more descriptive label, such as "Accept optional cookies", makes the decision clearer even when heard separately.

The same principle applies to rejecting cookies, opening settings and changing a previous choice.

The researchers also found that some notices appeared late in the screen reader's reading sequence. That means somebody could encounter much of the website before hearing that a consent decision was being requested.

SSC Digital's interpretation: these are not just technical presentation defects. They can affect whether somebody understands what they are agreeing to.

A privacy problem as well as an accessibility problem

The research also measured tracking-related network requests before and after visitors interacted with cookie notices.

On sites with notices, the researchers recorded an average of 43.4 tracker requests before interaction and 218.5 after acceptance — approximately five times as many.

That increase is not, by itself, evidence of wrongdoing. Some additional tracking may be precisely what the visitor agreed to.

The concern arises when somebody cannot properly understand, navigate or refuse the choice being presented. 1

UK guidance makes an important distinction here.

The Information Commissioner's Office (ICO) finalised its updated guidance on storage and access technologies on 29 April 2026, reflecting changes under the Data (Use and Access) Act 2025.

The rules now include limited exceptions for certain statistical and website appearance purposes. Where those exceptions apply, organisations may not need consent, but must meet conditions including clear information and a simple, free way to object.

Non-exempt activities, such as advertising tracking, still require valid consent. The ICO expects refusing consent to be as easy as accepting it. 2

Whether a site needs a consent banner depends on what technologies it uses and whether an exception applies. A banner is only one part of meeting the applicable requirements.

A hypothetical Scottish business example

Illustrative example only — not an SSC Digital client case or tested outcome.

Imagine an independent massage therapy business in Fife.

Its website displays treatment information, opening hours and a simple booking enquiry form. The business also uses an optional analytics service to understand which pages receive interest.

A third-party cookie plugin provides a polished consent box with coloured buttons and a settings panel.

The owner checks it on a laptop, clicks "Reject all", and everything appears to work.

However, a customer using a screen reader encounters the notice after much of the page content. The buttons are announced without clear descriptions, and keyboard navigation through the settings panel is confusing.

The booking form itself may be accessible, but the customer's first experience of the website is already difficult.

A review of the consent interface might reveal that its wording, focus order and button labels need improvement.

The business would not necessarily need a new website. It might only need to configure or replace the consent component and test it properly.

That is an important distinction for small businesses: useful improvements are not always large development projects.

What small businesses can do about it

The first step is to examine how the website behaves, not merely how it looks.

  • Try keyboard-only navigation. Open the website in a private browsing session and use Tab, Shift+Tab and Enter. Check whether every consent option can be reached and selected.
  • Read the buttons on their own. Would somebody understand each action without seeing the surrounding panel?
  • Check the opening behaviour. A modal notice should have a meaningful accessible name and sensible focus handling.
  • Test the actual tracking choices. Check whether non-exempt tracking stays disabled before consent and after rejection.
  • Ask for assistive-technology testing. Automated checks are useful, but a practical screen-reader test can expose problems they miss.

The World Wide Web Consortium provides guidance on accessible dialogs, including meaningful names, keyboard interaction and appropriate focus management. Its recommendations help developers test the behaviour of consent panels rather than simply their appearance. 3

What the research cannot tell us

There are limitations worth understanding before treating these findings as universal.

The paper is publicly available as a research preprint; its publication on arXiv does not itself establish peer review.

The study used a global website sample, not a representative survey of Scottish small businesses. Its automated screen-reader testing focused on desktop use with NVDA, rather than directly observing real users across different devices.

It also did not measure every possible combination of mobile browsers, iPhone VoiceOver, Android TalkBack and other accessibility software.

The researchers explicitly acknowledge these limitations. 1

The findings therefore indicate a significant design problem worth investigating, not a precise estimate of how many Scottish websites are inaccessible.

A small detail that deserves more attention

Website owners naturally focus on the things they can see: page design, photographs, colours, menus and enquiry forms.

But a website also has an underlying structure that influences how people using assistive technologies experience it.

Consent banners are a particularly useful reminder because they sit between the customer and the rest of the website.

Our view at SSC Digital is that accessibility and privacy should be considered together from the beginning. Both are ultimately about giving people information they can understand and choices they can genuinely make.

Sources and editorial notes

Checked 16 November 2026. Original SSC Digital explainer with AI-assisted research and drafting.

  1. Clarke and Mehrnezhad: A Large-Scale Evaluation of Cookie Notice Privacy and Accessibility for Blind and Low Vision Users

    Preprint submitted 31 October 2026.

  2. ICO guidance on storage and access technologies

    Final guidance published on 29 April 2026.

  3. W3C ARIA Authoring Practices Guide: Modal Dialog Pattern

    Keyboard interaction, accessible labelling and focus management.

Corrections: Send a correction or question.

Another useful read

Your next website visitor might bring an AI assistant →