Skip to main content
BrightEleven

Accessibility statement · Prepared 17 September 2026

Accessibility at BrightEleven

This statement covers the website at www.brighteleven.co.uk, the parent dashboard and the child's app. It says what we aim for, what we have actually tested, what we know still falls short, and how to tell us when something does not work for you or your child.

What we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA across the whole product, and to go beyond it on the child's screens in two specific ways: every tap target on a child screen should be at least 48 by 48 pixels, and no text a child reads should be smaller than 16 pixels.

BrightEleven is run by a private company, so the Public Sector Bodies Accessibility Regulations do not apply to it. We use the same shape of statement because it is the clearest one we know: a target, the evidence, the gaps, and a way to reach us.

What has been tested

Automated scans

Every public page, the sign-in and sign-up pages, and a sample of parent and child screens are scanned with axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rule sets, in both the light and dark themes and with the high-contrast setting on. The scan runs as part of our end-to-end test suite and any violation fails it. An automated scan finds only a minority of real accessibility problems, so we treat a clean run as a floor, not a pass.

Tap-target size on child screens

A separate check drives the real child journey - sign-up, a child profile, the PIN unlock, then practice - and measures every pointer target on the child routes against our own 48-pixel promise, applying only the exceptions WCAG 2.2 itself allows for inline links and well-spaced small controls. It fails on any offender.

Text size on child screens

The 16-pixel floor is a design rule we hold ourselves to and check by review, not yet by an automated gate. It is not met everywhere - see the known limitations below.

Keyboard and structure

Every page has a skip link as its first focusable element and a proper main landmark; forms use real labels; the child's rough-work pad offers a tap-to-join-dots alternative to dragging. These are checked by unit tests and by hand, not by a person who relies on assistive technology - which is the gap named first below.

Settings a child (or their parent) can turn on

All of these are off by default and are changed from the child's own profile page or by the parent from the dashboard. None of them sends anything to a third party, with the one exception noted for read-aloud.

  • Text size - a larger-text mode that scales the whole child interface.
  • Reading font - four choices, including two designed for readers who find standard type hard: an easy-read face with distinct letter shapes and a high-legibility face with heavier strokes.
  • Spacing - wider letter, word and line spacing.
  • High contrast - a higher-contrast set of colours layered on whichever theme is active.
  • Colour overlays - a tinted overlay over the whole screen, in several colours, for readers who find white backgrounds glare.
  • Focus mode - offered on the question screens, hides the surrounding chrome so only the question and its answers remain.
  • Calmer visuals and break reminders - turns off celebratory animation, and offers a gentle prompt to pause during a long session.
  • Read-aloud - reads each question and its options using the browser's own built-in voice. A higher-quality neural voice is available as an option; it needs a one-time download of the voice files from two content-delivery hosts, which is the one setting that makes a child's browser contact anyone other than BrightEleven, and it is off unless a parent or child turns it on.
  • Sounds - the small interface click can be switched off.

The site also has light, dark, eye-comfort and greyscale themes, honours the operating system's reduced-motion and reduced-transparency preferences, and shows correctness with an icon and words as well as colour.

Known limitations

These are the gaps we know about today. We would rather list them than imply they do not exist.

  • No assistive-technology user pass yet. Nobody who relies on a screen reader, switch access or magnification has yet been through the child journey with us. Until that has happened we do not describe the product as meeting WCAG 2.2 AA; we describe it as aiming for it.
  • Diagram descriptions. Non-verbal reasoning questions, and some maths questions, are built around a picture. Those pictures are drawn as vector graphics and do not yet carry a written description, so a screen reader cannot convey what is in them. Read-aloud reads the words of the question, not the picture.
  • The neural read-aloud voice needs a download. The optional higher-quality voice is a sizeable one-time download and may be slow or unavailable on a poor connection; when it is not ready in time the browser's built-in voice is used instead.
  • The 16-pixel text floor is not met everywhere. A small label in the child's topic list and the numerals drawn inside badge icons are smaller than our own rule. Both are on our list to fix.
  • Interactive drawing. The rough-work pad is a drawing surface; it has a tap-to-join-dots alternative, but drawing itself is not something a keyboard alone can do well.

Tell us about a problem

If something on BrightEleven does not work for you or your child, or you need any of this in a different form, email hello@techrock.co.uk or use the contact page. Say which page or screen it was, what you were using (for example a screen reader and which one), and what happened. A person reads every message, and problems that stop a child practising are treated as bugs, not feedback.

If you are not happy with how we respond, the Equality Advisory and Support Service (EASS) can advise on your rights under the Equality Act 2010.

About this statement

Prepared on 17 September 2026 from the tests and settings in the codebase on that date. It will be updated when an assistive-technology review has taken place, when a limitation above is fixed, and whenever a new one is found.