Accessibility statement

RepStax is committed to making this platform usable by everyone, regardless of how they navigate it.

Conformance status

We target WCAG 2.2 Level AA across the marketing website and the web application, and consider ourselves partially conformant — meaning most of the standard is met, and some content has not yet been fully assessed against it. Accessibility defects are treated with the same severity as a failed save.

How we test

• axe-core runs against every page of the marketing site and every screen of the application. Serious or critical violations fail the build, so they cannot be merged.
• Application screens are scanned twice: signed out and empty, and again signed in with real data — charts, populated tables, message threads and the booking diary, which are different documents to their empty states and are where most real problems live.
• Keyboard operation is covered by tests for the parts most likely to break it: focus trapping and return in dialogs, reordering exercises without a pointer, and completing a live session.
• Automated tooling catches a minority of real problems — the rest needs a person, so testing with assistive technology is an ongoing part of how this product is maintained rather than a one-off exercise.

Known issues

None currently open. This section lists defects as they are found, and an empty list means none are outstanding — not that none have ever existed. The most recent was a message thread whose list contained an element that was not a list item, which changes how a conversation is announced; it was caught by the populated scans described above and fixed the same day.

Reporting a problem

If something here blocks you, tell us and we will treat it as a bug. Email accessibility@repstax.app. We aim to acknowledge within two working days.

Enforcement

If you contact us about an accessibility problem and are not satisfied with our response, you can raise it with the Equality Advisory and Support Service.