Accessibility statement

What we are aiming for

Split Index aims to meet WCAG 2.2 level AA. We are not there yet. This page says where we are, honestly, and is updated when we re-audit rather than when we change the wording.

Current status

Partially conformant with WCAG 2.2 AA. Parts of the app meet the standard and parts do not; the specific gaps are listed below.

What we have fixed

• Colour contrast.Every brand colour pairing is now measured against the 4.5:1 text and 3:1 non-text thresholds, and the measurement runs as an automated test so the palette cannot drift back. The blue used on our light “Engine” screens measured 2.50:1 — below both thresholds — and now has a tuned variant at 5.26:1 for text and 3.52:1 for icons and borders. The label on primary buttons in that mode measured 2.60:1 against its own button and is now 5.47:1.
• Locked premium panels. These used to render the real numbers behind a blur, which meant a screen reader read them out. They now render nothing — a shaped placeholder and the reason it is locked.
• Charts now carry their figures. Every graph is followed by a one-sentence summary and a data table, both readable by a screen reader and hidden from the page. A trend chart says which way the number went and by how much; a breakdown reads its bands largest share first; a comparison says who is ahead and whether the gap is opening. Long series list their first 40 rows, and the summary covers the whole period. (WCAG 1.1.1.)
• Skip link.A “Skip to main content” link is the first thing you reach with the keyboard on every page, so you do not have to tab through the whole navigation.
• Reduced motion.Animations, page transitions and the loading screens respect your system’s prefers-reduced-motion setting.

Known issues

These do not currently meet WCAG 2.2 AA. We have listed them specifically rather than generally so you can tell whether one affects you.

• Some states are still signalled by colour alone. Parts of the interface distinguish the strength and endurance sides of the app, and some status indicators, using colour without a matching label or icon. (WCAG 1.4.1.)
• A full keyboard-only and screen-reader walkthrough has not been completed. We have audited colour contrast thoroughly and run automated checks, but automated tooling finds roughly a third of real problems. Until a manual pass over onboarding, logging a session, the dashboard, the leaderboard, the analytics page and checkout is done, we cannot claim those journeys are fully operable without a mouse.
• Four form errors are still not tied to their field. Most now are: reach an input that has been rejected and your screen reader will read the reason. The four that remain describe a group of controls rather than a single box — needing at least one exercise, the exercise picker, the weight-unit buttons, and the set list — so there is no one input to attach them to. Tying those correctly changes how the whole form is announced, which we want to get right against a real screen reader rather than by guesswork, so they are waiting on the manual pass described above. (WCAG 3.3.1.)

Telling us about a problem

If something here stops you doing what you came to do, we want to know — including if it is not on the list above.

Email accessibility@splitindex.co.uk. We aim to reply within 5 working days. Please say what you were trying to do, what happened, and what you were using — browser, phone, and any assistive technology.

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

How this was assessed

Self-assessed. Colour contrast was measured programmatically against every brand pairing the product renders, and those measurements run as part of our automated test suite on every change. The remaining checks were a code review against WCAG 2.2 AA. No external audit has been carried out.