What we have built
Each feature says how we check it and where it falls short.
Reading and understanding
-
The AI is told to write simply
The chat and the report are told to write for a reading age of 12, and the report's opening summary for 9. A test checks the instruction, but we do not yet measure what the AI writes.
-
A glossary where the words are
Some words in your child's profile and report open to show a plain meaning. The glossary is still small, and short forms are not spelled out yet.
Using it your way
-
Your own display settings
In the app you can choose light or dark mode, bigger text, less motion and less see-through layering. The website offers the same, but its theme follows your device. There is no high-contrast option yet.
-
Windows contrast themes
Focus outlines and your chosen answers stay visible in forced colour themes, such as Windows high contrast. Our tests for this cannot stop a change going in. For the app, a failure stops that change reaching the live app unless we override it and record why.
-
Printing comes out light
Pages print as dark text on light paper, even in dark mode. A test fails if that stops working.
Forms and signing in
-
No passwords, no puzzles
You sign in to the app with a link or a code sent to your email: no password, and no puzzle (CAPTCHA). A test fails if either comes back.
-
Errors that say where they are
A form's error message is linked to its field, so a screen reader reads them together. A test checks this on the app and the website. The app's messages do not always say how to fix the problem yet.
-
Your browser can fill it in
Name, email and organisation fields carry standard hints, so your browser can fill them in. A test fails if one goes missing.
-
The questionnaire works without JavaScript
In the app you can answer every question, add a child and make the sharing consent choice with JavaScript off. A test checks each kind of question this way before any change can go in. Browser tests check adding a child, comments and the sharing choice once a change is in. A failure stops that change reaching the live app unless we override it and record why. The website's forms still need JavaScript.
Moving through the questionnaire
-
Focus follows you
When the next question appears, your keyboard and screen reader move to it. A test checks this in the questionnaire. We have not checked the rest of the app this way yet.
-
You choose the pace
Questions move on by themselves once you answer. The Keep moving on switch on every question turns this off. With a keyboard, nothing moves on until you press Enter.
-
Nothing flashes, any input works
Nothing flashes, and touch, mouse and keyboard all reach the same controls. A test fails if code that could break either of these is added.
How we check
-
Every component, on its own
Each building block of the app is tested on its own by an automated accessibility checker, contrast included. That test has to pass before any change can go in.
-
Reading order, written down
Each app screen has a written record of the order a screen reader meets its content. An AI agent has read them all once, but no person has listened to them yet.