Cookiebot isn't up to date with standards WCAG 2.1
Hello,
I noticed that Cookiebot unfortunately isn’t WCAG valid, but you do say in several post it is WCAG valid. I follow the WCAG rules 2.1, for reference I follow this guide: https://www.w3.org/TR/WCAG21/
- Success criterion 1.1.1 Non-text content
All non-text content that is presented to the user has a text alternative that server the equivalent purpose.
The logo from the customer has an alt text of “logo”. This doesn’t describe it enough. In my opinion it should be something like “Logo [companyname]”.
The logo from Cookiebot has an alt text of “logo”. This doesn’t describe it enough. In my opinion it should be something like “Powered by Cookiebot”.
- Success criterion 1.4.1 Use of color
Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Every link in the Cookiebot slightly changes of color. Because it is a link it should do more then just change of color. For example it should have an underline.
- Success Criterion 2.4.3 Focus Order
If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
If we just use the keyboard, and we are going to "Set preferences". I want to change the "Details" and click enter on the keyboard. I should go into the content of "Details", but instead my next tab goes to "About" that is located in the menu. It should go into the content of “Details”.
Also, I can't change the checkboxes/slider with the keyboard.
-
Official comment
Hi!
Thank you for providing feedback regarding the new Swift banner and the WCAG standards. We are working on some improvements already at the moment (although we are not sure on when these might be released yet).
I can see you also send an email with regards to this and we will make sure to keep you updated on any new releases there.
Best regards,
Hannah
-
Hello,
I was curious if there are any updates.
0 -
Hi!
Sadly, no new updates are available yet. The tasks is rather large as we are trying to tackle different aspects of the WCAG rules, which unfortunately also means longer waiting times before implementation. I can see the email you submitted is put on hold and we will provide any updates on this matter as a response to that as soon as we have them available.
0 -
Hi,
Do you have any estimate for supporting WCAG 2.1 standards?
Task is obviously large, but you have had plenty of time, as it was released more than three years ago.
I have customers interested in this, but WCAG 2.1 support is an issue.
At least there should be an estimate so that we could be able to start using this.
0 -
Hello,
In the meantime we are almost 2 months further since my first post, sadly nothing has been changed. But you still advertise that Cookiebot is WCAG valid, see this post: https://www.cookiebot.com/en/cookie-banner/. Clearly it isn’t. Also, this issue has a priority: “High”, I doubt that.
We are not the only ones complaining about it. I’m disappointed on how things are handled right now. I understand that it’s a big job to fix this, but you could have thought about this before you start advertising. And maybe also change the articles where you say you are WCAG valid.
So let me ask again, are there any updates? Are you guys even working on it? Is there any estimate or deadline picked so we know what we can expect?0 -
Hello,
Just curious if there are any updates. Last time I heard anything was at the end of 2021.
0 -
Hi,
We recently released 3 banner updates, related to this;
- Set the focus to the tab when switching tab in Swift banner
- Screen reader: Resolve issue where text is not pronounced as the correct language
- Accessibility: Change accessibility text "Logo" to "Powered by Cookiebot" for the Cookiebot logo
The rest of the task items are still ongoing and are planned to be released in different timeframes.
0
Please sign in to leave a comment.
Comments
7 comments