Short version: We're building Cloak to the WCAG 2.2 AA accessibility standard. We haven't finished formal testing yet, so this is a live commitment rather than a finished box we've ticked. If something doesn't work for you, please tell us — it genuinely helps us improve, and we'll fix it.
1. Our commitment
Cloak is built for every teenager, including those who use assistive technology such as screen readers, keyboard-only navigation, screen magnification or captions. We're committed to meeting the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA — the same standard the UK public sector works to — across the Cloak website, the free classroom activities, and the schools platform we're building for 2026/27.
2. What this statement covers
This statement applies to the Cloak website at getcloak.tech, including the free classroom activities (the games and quizzes you can use without logging in).
- The Cloak for Schools student platform is still in build. Its accessibility is covered by the same commitment, and we'll update this statement with its specific conformance status before it launches.
- The Cloak Check browser extension is covered in our privacy policy.
3. How we design for accessibility
Accessibility is something we build in as we go, not something we bolt on at the end. In practice, that means we aim to:
- use clear, structured HTML with proper headings and labels, so screen readers can make sense of each page;
- keep pages usable with a keyboard alone, with a visible focus indicator;
- choose text and colour combinations that meet the AA contrast standard against their background;
- let text resize and pages reflow without breaking, so people can zoom in;
- write in plain English — the same principle behind everything Cloak does; and
- design the activities to be understandable and completable, with the information conveyed in more than one way where we can.
4. Where we are today
We check our own pages against WCAG 2.2 AA as we build them, but we have not yet completed a full, independent accessibility audit. That means some parts may not fully meet the standard yet. In particular, the interactive games are something we're still testing with assistive technology, and fast-paced or timed activities can be harder to use with some tools.
We're treating accessibility as an ongoing commitment rather than a one-off exercise. As our testing progresses, we'll publish a fuller conformance status here — including any known issues and the dates we reviewed them.
5. The schools platform
A student-facing platform only works if every student can use it, so accessibility is part of how Cloak for Schools is being built from the start. It's being designed to meet WCAG 2.2 AA, so students who rely on screen readers, keyboard navigation, captions or larger text can take part in the same activities as everyone else.
That supports schools in making the reasonable adjustments expected under the Equality Act 2010. If your school has specific access needs, tell us when you register interest and we'll factor them into the build.
6. Tell us about a problem
If you use Cloak and something doesn't work for you — a page you can't navigate, text you can't read, or an activity you can't complete with your assistive technology — please let us know. Reports like this are one of the most useful things we get, and they directly shape what we fix next.
Email info@solidcodesolutions.co.uk with the page or activity, what you were trying to do, and what went wrong (and the assistive technology or browser you were using, if you can). We aim to reply within 5 working days.