Accessibility
Accessibility statement
Our commitment
Our audience is teachers, and a good proportion of them are reading this on a phone at the end of a long day. We aim to meet WCAG 2.2 level AA, and we test against it rather than assuming.
What we have done
- Every piece of text meets AA contrast against the background it actually sits on, checked by measurement rather than by eye.
- Body text is 18px, rising to 20px on larger screens. Nothing on the site is smaller than 14px.
- Interactive targets are at least 24×24px, and most are 44×44px.
- The menu is fully keyboard operable: Tab is trapped inside it while open, Escape closes it, and focus returns to the button that opened it.
- A skip link takes you straight to the main content.
- Animation is switched off for anyone who has asked their device to reduce motion.
- Pages do not scroll sideways at any width from 320px up.
- Headings run in order, and decorative images are hidden from screen readers rather than given meaningless names.
What we measured
Checked across every page at 320, 375, 640, 834, 1024 and 1440 pixels wide:
| Check | Standard | Result |
|---|---|---|
| Text contrast | 4.5:1 body, 3:1 large | 0 failures |
| Smallest text | no minimum in WCAG; ours is 14px | 14px |
| Target size | 24×24px (2.5.8) | 0 below |
| Horizontal scroll | none at 320px (1.4.10) | 0 pages |
| Line length | readability, not WCAG | max 70 characters |
Known problems
We would rather list these than pretend they are not there.
- The drag-and-drop cube activity has not been tested for keyboard or touch use. It is decorative rather than essential — nothing on the site depends on completing it — but it is not currently operable without a mouse. This is the item we are fixing first.
- Videos do not yet have captions or transcripts.
- Downloadable PDFs have not been checked for screen-reader tagging.
Before publication
Captions and PDF tagging both need a decision and a date. Under the public sector accessibility regulations these would be required; as a private supplier to schools they are strongly expected rather than mandated, and schools increasingly ask. Add target dates here, or remove the claim.
How we test
Contrast, target size, text size, heading order and horizontal overflow are checked automatically on every page at six widths before it goes live. Keyboard behaviour for the menu is tested with real key presses rather than simulated events.Automated testing catches perhaps a third of accessibility problems — we do not claim it is sufficient on its own.
Worth doing
A screen-reader pass (VoiceOver or NVDA) on the key journeys, and ideally a test with a real user. Neither has been done yet, and neither is replaceable by automation.
Tell us if something is wrong
If any part of this site stops you doing something you need to do, tell us and we will fix it. Say what you were trying to do and what got in the way — that is usually enough for us to reproduce it.
Needed
The email address for accessibility reports, and the response time you are willing to commit to.