Accessibility Statement

Current position

ClassLens has not undergone a formal accessibility audit (e.g. against WCAG 2.1/2.2), and this page does not claim compliance with any particular standard. This is an honest statement of where things actually stand, not a target already met — please get in touch if something is genuinely blocking you from using the product.

What's actually in place

• Built with standard semantic HTML and a small, consistent set of components (buttons, labelled form inputs) rather than custom-drawn controls, which generally behave better with screen readers and keyboard navigation than bespoke ones — this hasn’t been independently tested with real assistive technology, though.
• The RAG (red/amber/green) colour system used throughout the product has deliberately verified contrast ratios, not just chosen to look right: the desk-fill colours pass WCAG AA against white text (red 6.47:1, amber 5.02:1, green 5.02:1 — computed via the WCAG relative-luminance contrast formula).
• Text throughout the product uses relative sizing and standard browser zoom works as expected — no fixed-pixel layouts that break when text is enlarged.

Known gaps

• A real colour-dependency gap in RAG mode: a pupil’s current red/amber/green status is shown only as the desk’s background colour — there is no text/letter indicator on the desk itself. The three small R/A/G buttons used to set a status are always labelled, but which one reflects the pupil’s currentstatus is distinguished only by that button being in colour versus the other two being dimmed grey — not by any non-colour signal (bold, underline, a mark). This is a genuine gap for colour-blind users, not yet addressed.
• The seating-plan grid and Progress data view are dense, visual layouts built for a teacher’s own use during a lesson — they have not been evaluated for screen-reader use, and likely need work there.
• No dedicated accessibility testing (automated or manual) has been run against any page yet.

Feedback

If anything about using ClassLens is genuinely inaccessible to you, please use the Feedback widget in the app, or see /security for how to get in touch. This statement will be updated as real testing happens, not left to go stale.