⚠️ Draft for review — not legal advice.
This is a working draft. It must be reviewed and approved by a qualified data-protection / education-law professional and the responsible Data Protection Officer before it is published or relied upon. Placeholders in [square brackets] need real values.
Accessibility Statement
Last updated: Draft — not yet published
Storyjar should be usable by every child and adult. Accessibility is part of keeping children included and safe.
Our commitment
We aim to meet WCAG 2.2 level AA and to be usable by young children and by adults with a range of needs.
What we do
- Dyslexia-friendly type: body text uses Atkinson Hyperlegible, chosen for legibility.
- Big, clear targets for children: child touch targets are at least 64px; one obvious action per screen.
- Colour & contrast: text meets AA contrast; colour is never the only way to convey meaning.
- Keyboard & focus: interactive elements are keyboard-reachable with a visible focus outline.
- Reduced motion: animations respect
prefers-reduced-motion; the interface still works fully with motion off. - Semantic structure & alt text for assistive technologies.
Known limitations
[List any known issues here as they are found, with target fix dates.]
Feedback
If you have trouble using any part of Storyjar, tell us at [accessibility@storyjar.co.uk] and we will help and fix it. We welcome feedback that helps us do better.