Accessibility

We run accessibility checks as a standard part of how we build every course, so a deliverable starts from a stronger baseline than most training content gets by default. This page describes exactly what's covered today (and, just as importantly, what it doesn't cover), so you can plan any additional review your compliance requirements call for.

What we check on every build

• Image alt text: every content image is checked for missing or non-descriptive alt text; we draft alt text as part of production so images aren't delivered undescribed.
• Heading order: the document outline is checked so headings never skip a level (e.g. an h1 followed directly by an h3), which is what lets screen-reader users navigate by heading.
• Color contrast: your brand's text/background color pairs are checked against WCAG AA thresholds (4.5:1 for normal text, 3:1 for large text) before a course ships.
• Assessment controls: knowledge-check questions and answer options are checked to ensure every control has a real, readable label for assistive technology.

Built into every course we deliver

• Keyboard operability: interactive blocks (knowledge checks, matching, drag-and-drop, quizzes) are operable via keyboard, not pointer-only.
• Reduced motion: animation and entrance effects honor your learners' operating-system "reduce motion" setting; disabling it never blocks content or functionality.
• Captions: video and audio blocks can be captioned, giving deaf and hard-of-hearing learners a text alternative.

What this is and isn't

These checks are a strong floor, not a substitute for a full accessibility audit. They catch the most common and highest-impact gaps, but no checklist verifies every WCAG success criterion: things like the accuracy of drafted alt text, the logical reading order of complex layouts, or full screen-reader walkthroughs still benefit from dedicated human review. We flag anything we find before delivery; for content that must meet a specific compliance standard (e.g. WCAG 2.1 AA, Section 508), tell us up front so we can scope the additional review that calls for.

Reporting an issue

If you or your learners encounter an accessibility barrier in something we built, contact us at hello@script2learn.com and we'll work with you to address it.