-
Two things, wouldn’t it be nice have a category about Accessibility on this community?
-
And concerning this accessibility I found that the close button is not a button so it is not focusable. Is it possible to make this a button? Or is this a bug and should I post this somewhere else?
Hi Joost,
thank you for your comments. We will have a closer look at the accessibility of our product.
When it comes to the close button on the consent bar - let me speak with the respective team of developers to have a look.
Tymek
Having the button would be a great first step. I’ll try to create some code for it in the meantime to make the span work as a button but let me know if the button is implemented.
And let me know if you need help testing the banner and modal on accessibility issues. I would be glad to help.
All right, stay in touch @svds!
I’m not able to add js to fix this issue because there are to many options to work with. Any news on this? Shouldn’t be to much work to change a span in to a button. I really want to use Piwik but without this my accessible website is not accessible any more.
Hi there!
I am also struggling with several WCAG issues of the consent bar.
- The X for closing the bar or the popup should have an aria label “Close” for screen readers.
- The X for closing does not get focus when tabbing by keyboard through the page
- When navigating by keyboard through the page, the cookiebanner should get focus first, before all the links on the page.
How can I solve these issues?
Thanks in advance!
Hi Bernard,
First off all it’s to bad to hear these problems are still present. I’ve send an e-mail with all improvements to them about a year ago. @pp.support can you please fix these problems, this makes it easier and better for governments to use your tool.
I have a fully working and accessible version of the piwik consent message. I use custom html, js and css to manage this. And load the html part before all other content on the page to get it to be focussed first.
My code is not suitable for everybody so I made a none tested version to use: Transfer - Dropbox
Hi Joost,
thanks a lot! I am working on a Drupal site as well, what a coincidence…
Oops did I leave Drupal traces…
.
Let me know if you need help with anything.
Hi Joost, hi Tymek,
so far I did not get the custom code running. And I am indeed disappointed that there are serious accessibility gaps in the standard consent bar, like the option to navigate by keyboard with the focus for the buttons, the aria labels and the use of headers where appropriate.
I think I will switch to Drupal’s cookies management instead, which is accessible by default.
Hi Bernard, Hi Joost,
I apologize for the lack of response. We have revisited this issue. I have shared the information (including that from last week) with the development team, and we are exploring the possibility of implementing improvements.
1 Like
As a government agency, we would also like to make full use of the cookie bar. An accessibility test conducted by a certified testing company found some accessibility findings. For example, the cookie bar is (still) not fully accessible with the keyboard. Just like @BernhardK mentioned.
Is there a prospect of an accessible cookie bar in the near future?
1 Like
Hi All, thanks for the info sofar, @pp.support is there any progress on this issue? It seems the solution is there and only needs to be implemented?
Seconding @Webredactie and @BernhardK , one of my clients recently had an accessibility test done on their website, and several issues arose from the cookie bar concerning accessibility. Their findings were:
- No text alternative for the close button, language switch or switch buttons. They also lack an explicit role.
- The buttons are not focusable with the tab button.
- No UL/LI elements were used to make up the list.
- The checkboxes under ‘hide consent details’ are not focusable, nor do they give a status when they have been checked/unchecked.
- The default styling on the buttons and links lacks sufficient contrast.
Any update on this would be much appreciated.
Any updates on this issue?
@Tymek, @Maciej_Kowcun and colleagues, the clock is ticking. In six weeks (June 28, 2025) the German accessibility act BFSG becomes law for all German companies (your Piwik PRO GmbH included). On that date, any German companies using your consent manager will become legally liable and must ensure that privacy settings are fully accessible according to WCAG 2.1. It’s no longer limited to government services. What are your plans and when can we expect these changes for the Piwik Consent Manager?
Hi, we’re not planning any product-side changes related to accessibility.
If you need to meet specific accessibility requirements, you have two main options:
- Customize the consent experience using a custom consent form .
- Consider migrating to Cookie Information CMP , which offers seamless integration with Piwik PRO and is actively maintained with WCAG accessibility .
Cookie Information has a free plan and also includes an automatic cookie scanner and supports consent form translations in 50+ languages , making it a strong option for international and accessibility-conscious implementations.
1 Like
- Visiting the website of Cookie Information I see their own Cookie Consent Pop-up isn’t even accessible. So I have hard hopes this will work.
- What’s the reason to not just deliver an accessible product? You are great developers so it must be a peace of cake to do this.
1 Like
Hi @svds,
Long time no see — great to hear from you again 
You’re right, our team is doing a fantastic job — not just thanks to their skill set, but also their focus on delivering the right solution, not just any solution.
As we speak, adjustments to the Cookie Information platform are underway. We’re fully aware of the deadline and committed to delivering on time.
A quick word on Piwik PRO Consent Manager — while it was built to simplify legal compliance for our users, the merger with Cookie Information brought in a far more advanced and specialized toolset for consent collection. Rather than maintain two parallel products that solve the same challenge, we’re consolidating our efforts around the Cookie Information CMP.
Why? Because it’s simply the better fit — robust, feature-rich, and scalable. We believe it’s the smarter, more sustainable choice for the future, and that you’ll find it meets your current and future needs more effectively. What’s important: integration with Piwik PRO takes literally minutes.
Try out CI CMP, you can register your account here. Please note, currently the offer stands for 80% discount for the first 6 months for Piwik PRO customers, later it’s €15 monthly. If you happen to be on the Core Upgraded plan (you purchased more actions) you already have the CI CMP subscription included, you just need to register your account a different way.
Hope my answer gives you all answers.
Cheers!
1 Like
Thanks for the full explanation. Is the Piwik PRO consent manager going to be phased out then? Because when this is still available, it will be used and it will be inaccessible still.
1 Like