WCAG 2.2 AA and your Passiro cookie banner
What the accessible banner covers, which banners have it and what you still need to check yourself.
1. Know what accessibility means for a banner
An accessible banner can be used with a keyboard, is announced correctly by screen readers, has readable contrast and visible focus, has controls that are large enough to use and keeps working when the page is zoomed or text is enlarged. WCAG 2.2 Level AA covers the applicable Level A and AA success criteria. Automated checks alone cannot prove conformance, and an accessible banner does not make the rest of your website accessible.
2. Check which banners have the accessible version
The accessible banner version applies to new domains added after its release, also when they are added to an existing account. Existing domains that do not use TCF keep their previous banner version, even if you edit the banner, publish it again or choose a template again.
Domains that use IAB TCF – Classic are the exception: existing and new domains with that banner receive the accessible version together with TCF 2.4. If you are unsure which version a domain uses, contact support.
For the TCF update, see TCF 2.3 vs TCF 2.4: what changes for your banner?
3. Know which templates are covered
The accessible version covers these templates:
- Standard (GDPR) – Default
- Standard (GDPR) – Stacked
- IAB TCF – Classic
- LGPD – Brazil
- POPIA – South Africa
- PDPA – Thailand
Other templates are not covered just because they run on Passiro. The standard configurations of these templates are designed to meet WCAG 2.2 AA; they are not certified or guaranteed to conform.
4. Know how the banner behaves
While the banner is open, the page behind it cannot be used with a pointer, a keyboard or a screen reader. This is how Passiro’s banner works, not a general WCAG requirement. Before a visitor has made a choice, pressing Escape or clicking outside the banner does not close it and is not consent.
When a visitor reopens the settings, Escape closes them without saving the changes and keeps the previous choice, and focus returns to the cookie settings button.
5. Keep your customizations accessible
You can change colors and styling freely, and the editor does not correct or block choices that reduce accessibility. For example, light grey text on a white background needs a contrast check, and a banner shown in English on a Danish page must be identified as English for screen readers, which does not require translating your website.
See Customize your cookie banner, and check the result with Check your banner on mobile and with a keyboard.
6. Know the limits
Choosing a template does not by itself meet every legal accessibility obligation of your website. For the success criteria, see the WCAG 2.2 standard from W3C.