Legal

Accessibility Statement

Last updated: 19 April 2026 · Pilot release

Our commitment

EverywhereX is built for children with special educational needs and disabilities, so accessibility is not a bolt-on. Our target is WCAG 2.2 Level AAacross the entire service, with specific attention to dyslexia, ADHD, autism, dyscalculia and dyspraxia. This statement tells you what we do well today, what we don’t yet, and how to get help if you’re stuck.

Built-in accessibility features

Every account has access to these settings from Settings. For student accounts they follow the child across devices.

  • OpenDyslexic / Lexend font — a dyslexia-friendly typeface applied site-wide.
  • Text-to-speech — read-aloud for lesson content and AI tutor replies, with word-level highlighting.
  • Extended time — doubles or removes quiz timers so there is no time pressure.
  • Reduced text density — tighter line count per screen, more whitespace, shorter paragraphs.
  • High-contrast theme — a 7:1 contrast pair that exceeds the WCAG 2.2 AAA threshold for normal text.
  • Voice tutor — your child can talk to the AI tutor out loud and hear the response, useful for learners who find reading or typing tiring. Push-to-talk mode (touch-and-hold the mic, or hold the spacebar) is available alongside always-listening mode. A live transcript is always visible.
  • Microsoft Immersive Reader — built into every lesson; provides text-to-speech, syllable splitting, picture dictionary, line focus, and translation into 100+ languages.
  • Mastery-based progression — opt-in per-child setting that gates lesson completion at 90%, with friendly retry framing rather than punitive scoring.
  • Mobile-first responsive layouts — all interactive elements are at least 48×48 CSS px on mobile (Apple/Material standard); safe-area handling for notched devices; iOS Safari WebRTC support for the voice tutor.

Separately, our AI tutor adapts its tone and structure to each child based on their SEND profile: shorter sentences for dyslexic learners, explicit and literal language for autistic learners, patient multi-step responses for dyspraxic learners, and so on.

Standard we aim for

The Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Level AA is the benchmark referenced by the Equality Act 2010 and by UK public-sector accessibility law. Specific 2.2 additions we’ve prioritised:

  • Focus appearance (2.4.11) — every interactive element has a visible, high-contrast focus ring.
  • Target size (2.5.8) — touch targets are at least 24×24 CSS pixels, usually more.
  • Consistent help (3.2.6) — the help-centre link is in the same place on every page.
  • Accessible authentication (3.3.8) — we support password managers and magic-link sign-in; no cognitive test is required to log in.

Keyboard and screen reader support

Every core journey — sign up, intake, lesson player, AI tutor, settings — can be completed with a keyboard alone. We test with Apple VoiceOver on macOS/iOS and with NVDA on Windows. Focus order follows visual order, form controls have labels and descriptions, and dynamic content updates are announced via ARIA live regions.

Known limitations

We’re a small team in pilot. These are the areas where we know we fall short of WCAG 2.2 AA today. We’re working on each of them.

  • Read-aloud voice selection — we currently use the default browser voice. Custom voice picking is planned.
  • Animation-intensity toggle— our celebration animations don’t yet respect prefers-reduced-motion everywhere. We’re adding a dedicated sensory-intensity setting in the next release.
  • Mathematical notation— some maths content is rendered as images without MathML alt text. We’re migrating to native MathML.
  • Third-party embeds — a small number of lessons link out to external video content whose captions and transcripts we do not control. We surface this in the lesson metadata.
  • Signed BSL — we do not yet offer a British Sign Language video track on any lesson. This is on the roadmap.

Getting unstuck

If anything on EverywhereX isn’t working for you or your child, please tell us. We treat every accessibility report as a priority bug and aim to respond within two working days.

Enforcement

If you’re not satisfied with how we respond to an accessibility complaint, you can contact the Equality Advisory and Support Service (EASS), who advise on Equality Act 2010 matters.

How this statement was prepared

This statement was prepared on 14 April 2026 based on an internal audit of the platform against the WCAG 2.2 AA criteria. It will be revisited after every significant release and formally re-audited by an external specialist before the service moves out of pilot.