Hi Bjarne,
It is possible that is a false positive. With backend testing (rather than testing on the front end of a webpage like WAVE does), it is more challenging to get an accurate color contrast check. This is something we’re working to improve.
We can try to run the HTML from your page through our tester and see if there is anything we can do to improve the accuracy of contrast for your specific site. In the meantime, if you have Accessibility Checker Pro, you can create a global ignore that will apply to all current and future pages that have a specific code snippet that is a false positive. You would go to /wp-admin/admin.php?page=accessibility_checker_issues&tab=fast_track (adding your website at the beginning) to review open issues in bulk and create global ignores.
Thanks for using our plugin and we’re glad you find it helpful! I’ll let you know what we think about the color contrast.
Thank you so much for your quick reply. Regarding “We can try to run the HTML from your page through our tester and see if there is anything we can do to improve the accuracy of contrast for your specific site” – that would be appreciated. Having the checks right at hand at content creation times, could be very valuable, especially if all issues are “legit” and I don’t start on ignoring them.
Let me know if I can assist is testing, eg with a different theme or browser.
Kind regards
Bjarne
Hi Bjarne,
I believe that the issue here is that Accessibility Checker is not able to parse through the CSS variables for these particular elements in order to determine if there is a contrast issue or not and as a result a contrast error has been flagged in so that you can manually check it.
Since we’re doing a backend test that does not require a full front-end page load, color contrast is a lot harder for us to assess with 100% accuracy (especially if JavaScript is changing anything on the front end). CSS variables are particularly difficult to parse through and gather the exact color codes + font sizes. We’re planning to continue working on this and possibly add a front end test to Pro in the future.
I actually looked at this same page on your website in axe (Deque’s accessibility testing browser extension that is very popular) and it looks like it couldn’t figure out any of the contrast at all, marking 78 items for manual review.
In this instance, the best solution is to confirm that the color contrast is correct and then just “Ignore” the errors. You can either do this on every page in the free version or can create a global ignore in Pro.
