Skip to content
TagSentry
Blog

Guide · Consent

Cookie banner accessibility: screen readers and keyboards

We tested 90 European cookie banners with a keyboard and read what they tell a screen reader. What fails most, a checklist, and a 10-minute test.

The TagSentry team · September 8, 2026 · updated November 5, 2026 · 7 min read

The short answer

A screen reader user needs the banner announced as a dialog with a name, focus moved into it when it opens, and both buttons reachable and labelled. A keyboard user needs to reach "Reject all" with Tab, see where focus is, and close the banner with Enter. We tested 90 European banners: 36 weren't marked as a dialog at all, and on 14 a keyboard never reached a consent button. Since June 2025 the European Accessibility Act has made this a legal question for many businesses selling in the EU.

What a screen reader needs from a banner

When a banner appears, a screen reader only knows what the markup tells it. Whether a blind visitor can make a real choice comes down to these:

  • A role. The banner is a <dialog>, or an element with role="dialog" (or alertdialog). Without it, the banner is just more text somewhere on the page.
  • A name. aria-labelledby pointing at the banner's heading, or an aria-label, so the reader says something like "Your privacy choices, dialog".
  • Focus moves in. When the banner opens, focus goes to the dialog or its heading. Otherwise the visitor starts at the top of the page, with no hint that a banner is waiting.
  • Real buttons with words. "Reject all" and "Accept all" are <button> elements with visible text, not icons or clickable <div>s.

If the banner dims the page behind it, it should say so with aria-modal="true" and keep focus inside until the visitor chooses. W3C's dialog pattern covers this in detail. A bar at the bottom of a page people can still use shouldn't trap focus, though: trapping someone in a box they can see past is its own failure.

What we found on 90 banners

We took the 92 sites from our cookie consent banner test that showed a banner with an Accept button: random European and UK sites, outside the biggest brands.

On 5 November we loaded each one in Chromium and read the banner's markup. Then we put the mouse away, pressed Tab up to 120 times, noted when each consent button got focus, checked whether the focus could be seen, and pressed Enter. 90 banners loaded.

What we checkedBanners
Marked up as a dialog54 of 90
A dialog with a name a screen reader can read out50 of 90
Focus already in the banner before any key press27 of 90
A consent button reached with Tab76 of 90
No consent button reached in 120 presses14 of 90
Focus visible on the first button reached70 of 76
Enter on that button closed the banner70 of 76
The whole keyboard path worked65 of 90

Where a button could be reached, it usually took four presses. On nine sites, reaching Accept took more than 20 presses, usually because the banner came after the page's links in the tab order. On some of the 14 failures, Tab went round every link on the page and back to the start without landing on a banner button.

For screen reader users the markup matters most. On 36 of 90 sites nothing told a screen reader that a dialog had opened. On 63, focus wasn't in the banner when it opened, so a screen reader user starts at the top of the page and has to go looking for it.

One load per site, from a US address, in a desktop browser. We read the markup a screen reader gets; we didn't run one. We don't name the sites.

A focus ring drawn on a wrapper around the button would count as not visible, and a change too small to see would count as visible, so the 70 could be a little off either way.

The European Accessibility Act has applied since 28 June 2025. It covers e-commerce services such as online shops and other consumer services. Very small service businesses (fewer than 10 staff, and €2 million a year or less) are exempt.

Websites are measured against WCAG level AA. The European standard, EN 301 549, includes WCAG 2.1 AA, and W3C's summary of the Act lists WCAG 2.2, so aim for 2.2.

The checklist

Choices

  • Reject and Accept look the same. Same size, colour and weight, and both on the first screen. A tiny grey "Reject" next to a big "Accept" is a common complaint about banners, and European regulators treat a harder-to-find reject as a problem in its own right.
  • One click to say no. "Reject all" shouldn't be behind "Settings" or "More options".
  • Plain labels. "Reject all" and "Accept all" beat "OK" and "Manage".

Keyboard

  • Focus moves into the banner when it opens, so a keyboard user doesn't have to tab through the whole page first.
  • Every control is reachable with Tab and works with Enter or Space (WCAG 2.1.1).
  • Focus is visible (WCAG 2.4.7). The focused button has a clear outline, and your CSS doesn't remove it.
  • The banner doesn't hide what's focused. A bar fixed to the bottom of the screen can completely hide the link a visitor has just tabbed to (WCAG 2.4.11, Focus Not Obscured).
  • Focus returns to something sensible when the banner closes.
  • Escape does something predictable, and it doesn't count as "Accept".

Seeing it

  • Text contrast of at least 4.5:1 against the banner background (WCAG 1.4.3), button text included.
  • Buttons at least 24 by 24 pixels, or 44 if you can, so they're easy to hit on a phone (WCAG 2.5.8).
  • Works at 200% zoom and on a 320-pixel-wide screen without cutting off buttons.
  • Doesn't rely on colour alone to show which option is which.

Hearing it

  • It's announced. A dialog role with a name, as above.
  • Buttons have real text, not just icons.
  • The language is marked. If the banner is in German on an English page, mark it with lang="de" so the screen reader pronounces it correctly (WCAG 3.1.2).
  • A blocking banner is modal. If it dims the page, aria-modal="true" tells a screen reader the page behind is out of reach, and focus stays in the banner.

Coming back

  • Visitors can change their mind from a link or button that stays available, like a small "Privacy choices" launcher.
  • That launcher is accessible too, with a label and a large enough hit area.

Test yours in ten minutes

  1. Open your site in a private window. Don't touch the mouse.
  2. Press Tab. Does focus land in the banner? Can you see where it is?
  3. Reach "Reject all" and press Enter. Did it work, in the same number of steps as Accept?
  4. Zoom the browser to 200%. Are both buttons still visible without scrolling sideways?
  5. Turn on a screen reader (VoiceOver on a Mac, Narrator or the free NVDA on Windows) and reload. Is the banner announced as a dialog, with a name? Are the buttons read with their names?
  6. Check the contrast of the button text with any contrast checker.

If any of those fail, fix that before you worry about anything else on the banner. If your banner comes from a plugin or a consent tool, send the failing step to the vendor.

Where our own banner stands

We hold TagSentry's own banner to this list and publish the result. Our accessibility statement says the banner is partially conformant with WCAG 2.2 level AA, based on our own testing.

What the TagSentry banner does today:

  • A screen reader hears it as a dialog, named by its heading and described by its text. Focus moves to the dialog when it opens, so the heading is read before the buttons.
  • Every control is a real button, and the focus ring always shows.
  • The banner's language is marked, so it's read in the right voice.
  • Over a dimmed page it is modal: screen readers are told the page behind is out of reach, and focus stays inside. As a bar on a page people can still use, it leaves the page alone.
  • Reject all and Accept all sit side by side on the first screen, with the same look. On that first screen Escape leaves the banner in place, so a key meant for the page isn't taken as a choice. In the detailed choices, Escape goes back one screen and stores nothing.
  • Every colour you publish passes a contrast check first.

Sources

  1. Bird & Bird: The European Accessibility Act comes into force (28 June 2025)
  2. Business.gov.nl (Netherlands government): European Accessibility Act for products and services
  3. W3C WAI: Web accessibility laws and policies, European Union
  4. W3C: Web Content Accessibility Guidelines (WCAG) 2.2
  5. W3C WAI-ARIA Authoring Practices: Dialog (modal) pattern
  6. W3C: Understanding Success Criterion 2.4.7, Focus Visible
  7. Tranco: a research-oriented top sites ranking