Skip to main contentSkip to content
IncluTrain

Accessibility

IncluTrain is built for special-education professionals, so accessibility is a baseline requirement, not an afterthought. This statement describes what we have built, where we currently stand against the recognized standard, and the limitations we are still working on. It is a living document, last reviewed June 15, 2026.

Our commitment

We design and build IncluTrain to meet Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, the standard adopted under the Americans with Disabilities Act (ADA) Title II web rule. We aim for Level AAA on the surfaces educators use most. Accessibility is part of how we judge a feature “done,” and every change is reviewed across desktop and tablet (landscape) layouts.

Conformance status

IncluTrain targets WCAG 2.2 Level AA and is partially conformant: most of the standard is met, and the gaps below are being addressed. IncluTrain has not yet completed an independent third-party audit (no formal VPAT/ACR is published). We therefore describe a conformance target and an honest status here, rather than claiming unqualified conformance.

What we have built

  • Full keyboard navigation, a skip-to-content link, and visible focus indicators on interactive elements.
  • Buttons, response options, and form controls are at least 48 px high (exceeding the WCAG 2.2 target-size minimum), with generous spacing. Inline text links in the page header and footer are sized by the surrounding line height, which the standard treats as an exception.
  • Learner-paced content: the practice demonstrations advance one step at a time (no autoplay), and respect reduced-motion preferences by design. Nothing flashes or moves on its own.
  • Text-to-speech read-aloud for scenario narratives, adjustable text size, and a high-contrast option.
  • Screen-reader labels on controls, semantic landmarks and headings, and captions/transcripts for any step-through demonstration.
  • A warm, low-saturation palette and off-white backgrounds chosen to reduce visual fatigue and pattern glare.

Known limitations

We are actively working on the following:

  • An independent accessibility audit and a published VPAT/ACR are not yet complete.
  • Read-aloud uses your browser's built-in text-to-speech voice, so the exact voice and pronunciation vary by device and browser.
  • A small number of duplicate or redundant navigation aids are being consolidated.
  • The scenario simulation uses a side-by-side layout best suited to desktop and tablet (landscape); on a narrow phone screen it gracefully falls back to a single column.

Report a barrier

If you encounter an accessibility barrier in IncluTrain, please tell us. Your report helps us prioritize fixes. Email support@inclushift.com with the page, what you were trying to do, and the assistive technology you were using. District users may also raise it through their administrator. We aim to acknowledge reports promptly and to offer an accessible alternative while a fix is in progress.

Standards & legal basis

  • WCAG 2.2 — W3C Recommendation (12 December 2024). w3.org/TR/WCAG22 (opens in a new tab)
  • ADA Title II web rule — 28 C.F.R. §§ 35.200–35.205 (adopts WCAG 2.1 Level AA). Compliance dates: April 26, 2027 (public entities serving 50,000+) and April 26, 2028 (smaller entities), per the U.S. Department of Justice 2026 interim final rule.

This statement reflects our current understanding and is updated as we improve. It describes IncluTrain's web application at train.inclushift.com.