Hear your course the way a screen reader user hears it

Paste a course URL or drop a published SCORM zip. The scan reads the package itself — every screen, including the ones behind branching — and takes about three seconds. No account: your file is uploaded for scanning only and deleted immediately; never kept.

…or drop a published .zip here (Storyline and Rise are fully supported; other SCORM packages get a best-effort scan)

What the scan checks

The accessibility scan reads a published SCORM, cmi5, xAPI or AICC package itself — every screen, including those behind branching — rather than crawling the course in a browser.

It reports against six WCAG 2.1 success criteria a machine can be certain about: 1.1.1 Non-text Content (missing or filename alt text), 1.2.2 Captions, 1.3.1 Info and Relationships (heading order), 2.1.1 Keyboard, 2.4.6 Headings and Labels (unnamed controls and hotspots) and 3.1.1 Language of Page.

Each finding quotes what a screen reader actually announces, and the report includes a transcript of the worst screen read aloud.

No automated scan proves WCAG conformance; the report finds problems, and a human review with assistive technology is still needed.