Accessibility

Our aim

We want everyone to be able to check their website and read their results, whether they use a keyboard, a screen reader, magnification or voice control. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across consentscan.io, including the dashboard and the PDF reports.

What we’ve done

• Every page can be used with a keyboard, with a clearly visible focus outline, and a “Skip to content” link as the first stop.
• Text and controls meet the WCAG AA contrast ratio (4.5:1 for normal text).
• Grades are always shown as a letter, never by colour alone.
• While a scan runs, screen readers hear each stage once, and the result is announced when it’s ready.
• Animations stop when your device asks for reduced motion.
• Pages are checked automatically with axe-core on every change we make, and by hand with a keyboard.

Known issues

• Cookie banner. Our consent banner is provided by Cookiebot. When it opens, keyboard focus doesn’t move into it, so keyboard and screen-reader users have to find it at the end of the page. We’re changing its settings to fix this.
• Dashboard. The signed-in dashboard has been checked with a keyboard but not yet fully tested with screen readers. If something doesn’t work for you, please tell us.
• Intro video. The walkthrough video on the homepage is hosted on YouTube and loads only when you press play, so captions depend on YouTube’s player. If you’d like a written walkthrough instead, email us.

Tell us about a problem

If you find something on consentscan.io that you can’t use, or you need a report in a different format, email info@consentscan.io with the page and what happened. We’ll get back to you and fix what we can.

How we checked

This statement is based on our own review in October 2026: automated testing with axe-core against WCAG 2.2 A and AA on our public pages, plus manual keyboard and contrast checks. We’ll review it whenever we make significant changes to the site.