Accessibility Statement

Everyone should be able to read a cookie banner and make a choice, including people who use a keyboard, a screen reader, magnification or high-contrast settings. This statement covers the consent banner that CookieBeam customers embed on their websites: the first layer, the preferences dialog, the floating settings button and the US privacy choices panel.

Conformance target

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the level referenced by the European Accessibility Act through EN 301 549. With its default styles and built-in theme presets, the banner passes our automated WCAG 2.2 AA checks. It has not yet been audited by an independent third party, so we describe it as partially conformant until that audit is done.

How we test

  • Automated axe-core checks against the WCAG 2.0, 2.1 and 2.2 level A and AA rules run in continuous integration on every change to the banner: structure and ARIA for every banner surface, and colour contrast and target size in a real Chromium browser for every layout and theme preset.
  • Automated keyboard and layout checks: every control can be reached with Tab and shows a visible focus indicator, the banner reflows at a width of 320 CSS pixels, and text stays readable with increased text spacing.
  • Manual review of banner code changes against a keyboard and screen-reader checklist: dialog roles and names, switch states, language and reading direction, focus order and focus return.

What the banner does

  • All controls work with a keyboard. A banner that leaves the page usable does not trap focus; the preferences dialog and blocking banners keep focus inside, close with Escape where closing is allowed, and return focus to where you were.
  • Dialogs are named by their heading and described by their text. Consent toggles are announced as switches with their name and on/off state.
  • The banner declares the language it is shown in and switches to right-to-left layout for languages such as Arabic and Hebrew.
  • Animations are turned off when your system asks for reduced motion, links inside banner text are underlined, and interactive targets meet the WCAG 2.2 minimum target size.

Known limitations

  • Website owners can change the banner colours, fonts and CSS. Our banner designer warns when a colour pair falls below 4.5:1 for text or 3:1 for controls, but it does not block saving, so a customised banner may not meet WCAG contrast requirements.
  • Banner wording, link text and translations are written by each website owner, so their clarity is outside our control.
  • A few secondary labels, such as "Show more" and parts of the IAB TCF vendor list, are only available in English. They are marked as English so screen readers pronounce them correctly.
  • Some fixes reach existing banners only after the website owner saves the theme and publishes the banner again: colour corrections for themes based on a dark preset, and all fixes for banners pinned to an earlier runtime version.
  • This statement covers the embeddable consent banner. It does not cover the CookieBeam dashboard or this website.

Feedback and contact

If you run into a barrier in a CookieBeam banner, please tell us. Email [email protected] with the address of the website, your browser and any assistive technology you use, or use our contact form.

This statement was prepared on 24 September 2026.