Hi Radek,
It seems that this is a false positive. As you can see, this is the situation before consent: the script is blocked by changing it to ‘text-plan’. I believe that the scan would validate it after consent.
Kind regards,
Leon
Thanks for rapid answer Leon!
The case is WCAG 2.1 compliance – and this not passed the official audit – since I don’t want to delete GA I’m looking for any solution.
Best,
Radek
Plugin Author
Aert
(@aahulsebos)
Hi @rnd0mized,
Is the analytics code added with Complianz, or outside Complianz. I’m thinking of way to workaround W3C, this has zero effect on WCAG.
regards Aert
Hi Aert,
Added with Complianz.
Regarding WCAG (at least here in Poland, in specific practice areas), for full certification, HTML code has to be clean (0 errors sharp).
Best,
Radek
Plugin Author
Aert
(@aahulsebos)
Hi @rnd0mized,
Weird question, can you deselect the three checkboxes under ‘Statistics’ in the wizard, and try again?
It changes to ‘src’ only,
regards Aert
Hi Aert,
Nothing changed. Still data-cmplz-src.
Best,
Radek
Plugin Author
Aert
(@aahulsebos)
Hi @rnd0mized,
As long as Google Analytics is blocked, or controlled by Complianz we change the src=””.
I’m now trying to remove async before consent, as loading something that is blocked is less relevant and adding it afterwards. Just to remove the connect between src= and async.
I spoke to accessibility specialist earlier, who said HTML validation is throwing more false positives these days and there moving validation to screens readers themselves. That would at least solve the issue, until then a workaround might be needed.
regards Aert
Hello!
Is there any news about this?
I have tons of errors because of “data-cmplz-src” at W3C and even if it’s just a “cosmetic” problem, it makes it difficult to find other errors because EVERY page is marked as having errors.
Thanks
Hi @industriecontact,
Unfortunately there is little we can do on our end. As mentioned above, we work with accessibility specialists to comply with WCAG guidelines and using this data-attribute is not an issue. This scan triggers false positives, most likely because they don’t know the data attribute. In our opinion the scan should be improved to only show actual accessibility issues, not false positives.
What you could do to circumvent the issue, is to perform the scan with the cookie blocker disabled (Enable safe mode via Complianz -> Settings).
I hope this helps. Please open a new thread if you have any other questions. We are happy to help but we don’t actively monitor closed threads for new replies.
Kind regards,
Leon
