Accessibility Statement
Last updated July 25, 2026
Qoollege exists to make the path to college legible for students who find the standard version of it overwhelming. That goal is worth very little if the product itself is hard to use, so accessibility is treated as part of the work rather than a retrofit.
This page describes where we actually are — including the parts that aren’t done. We’d rather be useful than impressive.
Our approach
We design following the Web Content Accessibility Guidelines (WCAG) 2.2, with particular attention to the cognitive-accessibility guidance — reducing memory load, keeping language plain, making the next action obvious, and never punishing someone for taking a break.
We do not currently claim conformance to WCAG 2.2 Level AA. A formal third-party audit is planned; until it passes and we have fixed what it finds, saying otherwise would be a marketing claim rather than a fact. This page will be updated when that changes.
What’s implemented today
- Comfort settings. Every signed-in student can reduce motion, scale text to 112% or 125%, and switch on the Atkinson Hyperlegible reading font — designed by the Braille Institute so similar letters can’t be confused. Settings apply across the app and persist on that device.
- Reduced motion is honoured system-wide. If your operating system is set to reduce motion, we respect it — animations, transitions and celebration effects (including confetti) are suppressed without you changing anything.
- Light and dark themes, either chosen explicitly or following your device setting.
- One clear next step. Our roadmap’s “Focus Now” view surfaces what to do today instead of presenting an undifferentiated list. Nothing is ever locked behind a completed task — we recommend, you choose.
- Reminders across email, in-app and push, so remembering deadlines isn’t a prerequisite for using the product.
- Progress is saved as you go. Onboarding resumes where you left off rather than restarting, and we warn you before navigation would discard unsaved edits.
- Keyboard and screen-reader basics. A skip-to-content link, landmark regions, labelled navigation, and accessible-name coverage on interactive controls via our component library.
- No diagnosis required — ever. We never ask for a diagnosis, an evaluation date, or clinical documentation. Anything we ask about support needs is functional (“what helps you”), optional, and skippable.
Known limitations
These are gaps we know about and are working through. Listing them is not a substitute for fixing them.
- No independent WCAG 2.2 AA audit has been completed, so there are very likely issues we have not found yet.
- Comfort settings are stored per device. They do not yet follow you to another browser, another computer, or the mobile app.
- There is no read-aloud (text-to-speech) feature yet for long-form content such as roadmap items and scholarship descriptions.
- Notification timing and frequency are not yet configurable — there are no quiet hours or per-channel controls.
- Tasks are single-level; you cannot yet break a task into sub-steps inside the product.
- Some third-party embeds we rely on (scheduling, payments, chat) are outside our control, and their accessibility may differ from the rest of the site.
- Colour contrast and focus visibility have been checked informally, not exhaustively, across every component state.
Tell us what isn’t working
If something on Qoollege is hard or impossible for you to use, we want to hear about it — including the small things. Email info@qoollege.com with “Accessibility” in the subject line and, if you can, the page you were on and what you were trying to do.
We aim to acknowledge accessibility reports within five business days. If a fix will take longer, we’ll tell you what we’re doing and offer a way around it in the meantime.