Accessibility Statement

We aim to meet WCAG 2.1 Level AA. Accessibility is treated as part of building a screen rather than a pass at the end — several of the conventions below are enforced in our design system, so a new screen inherits them by default rather than having to remember them.

• Contrast is measured, not estimated. Every text colour in both light and dark themes is contrast-checked against the surface it sits on, and the measured ratio is recorded alongside the colour’s definition. Body text exceeds AA at every level, and most primary text clears AAA.
• Status is never carried by colour alone. Anything shown in a colour that means something — at risk, on track, overdue — also states it in words, so it survives colour blindness and greyscale.
• Focus is always visible. We replace the browser’s focus ring with a stronger one rather than removing it. Every interactive element is reachable and operable by keyboard.
• Motion respects your system setting. When your operating system requests reduced motion, animations and transitions are disabled throughout the app.
• Icons are not information. Decorative icons are hidden from assistive technology, and any control that shows only an icon carries a text label for screen readers.
• Charts are readable as text. Our charts are built by hand rather than pulled from a library so that values are printed beside the bars and each chart carries a meaningful description — a screen reader user gets the numbers, not “image”.
• Numbers do not jitter. Figures that update use tabular figures so columns stay aligned and are easier to scan.
• Zoom is never blocked. We do not disable pinch-zoom; students read dense tables on small screens.
• Both themes are first-class. Light and dark are a full token swap, each independently contrast-checked — not a filter over the other.

Areas we know need more work:

• Our screen-reader testing has been broader on some screens than others. The dashboard, task list and gradebook have had the most attention; the calendar and analytics views have had the least.
• Content you upload — a syllabus PDF, a course document — is presented as its author wrote it. If the source file is not accessible, we cannot make it so.
• AI-generated text is not reviewed for reading level and may be denser than some readers want. The tutor can be asked to explain more simply.
• Some dense data tables scroll horizontally on narrow screens. They are keyboard-scrollable, but a wider viewport is more comfortable.

If any part of StudentOS AI is difficult or impossible for you to use, tell us — it is the fastest way for us to find what our own testing missed.

Email [TODO: [email protected]] and, if you can, include:

• The page or feature involved.
• What you were trying to do and what happened instead.
• Your browser and any assistive technology you use, including version numbers if you know them.

We aim to acknowledge within 3 business days and to give you a plan or a fix within 10. If something blocks you entirely, say so — we will prioritise it and look for a workaround in the meantime.

If you cannot access information in StudentOS AI and need it another way, contact us at [TODO: [email protected]] and we will provide it in a reasonable alternative format at no cost.

We review this statement when we make significant changes to the app, and at least once a year. The “Last updated” date above reflects the most recent review.