Everyone
Accessibility Statement
The standard we build to, how we test it, known limitations, and how to tell us about a barrier.
Effective · Last updated
1. Our standard
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, the standard referenced by EN 301 549 and by accessibility laws in the EU and Türkiye.
2. What we do
- Automated checks (axe-core, WCAG 2.1 A and AA rules) on new and changed screens, which must pass with zero violations before release.
- Full keyboard operation, a visible focus indicator, a skip-to-content link and page landmarks on every page.
- Light and dark themes built from contrast-checked colour tokens.
- Status changes (such as “reply sent” or “signing out”) announced to assistive technology, and errors linked to the fields they describe.
- Spatial (3-D) procedures can be walked through with the keyboard.
3. Known limitations
- 3-D spatial practice scenes are visual by nature. They can be operated by keyboard, but a full non-visual equivalent is not yet available for every scene.
- Session recordings are replayed visually; there is no text transcript of a recording yet. The learner's actions are also listed as a timeline of events.
- Some data-dense charts may be hard to use with a screen reader; the underlying figures are usually available in the tool's tables.
- The bot-protection check that sometimes appears at sign-up is provided by Cloudflare and outside our control.
- We have not yet completed an audit with people who use assistive technology every day. It is planned.
4. Tell us about a barrier
If something stops you from using ITSPracticing, email accessibility@itspracticing.com with the page and what happened. We aim to reply within 5 business days, and where we cannot fix it quickly, to give you the information in another way. Learners can also ask their Institution for reasonable adjustments, such as extra time.