Our commitment
We want CaseConduit to be usable by everyone, including people using assistive technology, and we are working towards WCAG 2.1 level AA as our standard. We also know that institutions — especially UK universities, who carry a legal duty under the Public Sector Bodies Accessibility Regulations — need their suppliers to be straight about where they stand. So this page is written the way we'd want to read it: what's in place, what isn't yet, and what to do if something blocks you.
What's in place today
- Light and dark themes across the whole platform, switchable by the user at any time — including learners inside a live session.
- Text alongside audio — where simulations speak with synthesised voices, the same content appears as on-screen text, and play surfaces provide transcripts of what was said.
- Mostly self-paced interaction — simulations are largely turn-based: you read, think and respond in your own time rather than against a clock. (Some formats use time pressure as a deliberate mechanic; see limitations.)
- Responsive, zoomable layouts — pages reflow rather than clip when text is enlarged, and the marketing site and studios work across screen sizes.
- Semantic structure on the marketing and documentation pages — headings, lists and links that read correctly in a screen reader.
Known limitations — the honest list
- We have not yet been formally audited against WCAG 2.1 AA. The claims above are our own assessment, not an independent one, and parts of the platform will not yet meet AA.
- The protected case viewer is not screen-reader accessible by design tension: to protect authors' copyrighted material, learner-facing case documents render as protected images rather than selectable text — which is exactly what a screen reader cannot read. Where a learner needs it, we will provide the case in an accessible alternative format; the educator or institution can request this for any session.
- Simulations are rich, animated interfaces — character stages, dashboards, maps and games. Keyboard-only operation and screen-reader flow through these surfaces has not been systematically tested, and some game formats deliberately use time pressure (for example, the crisis-inbox format), which we don't yet offer an untimed alternative to.
- Charts and visual exhibits generated within cases and debriefs don't yet consistently carry text descriptions.
What we're doing about it
- Working towards WCAG 2.1 AA in each improvement pass across the studios — accessibility fixes ride the same continuous-improvement process everything else here gets.
- An independent accessibility audit is on our roadmap as the platform grows, after which this page will state conformance per component rather than in general terms.
- Alternative formats and accommodations on request, now: if you or your learners need case materials, debriefs or session content in another form, email us and we will sort it for that cohort — this is available at every tier, not as a paid extra.
Found a problem, or need an accommodation?
Email hello@caseconduit.io — it reaches the people who build the platform, and accessibility reports go to the front of the queue. Tell us the page or studio, what you were using (screen reader, keyboard only, magnification…), and what happened.