Fixing accessibility in a course you can't open
Content problems can be patched. Player problems can't. Scan first, then decide.
Last reviewed
Start by scanning the published course to see what fails. Problems in the content — missing alt text, uncaptioned audio, low-contrast colors — can be fixed in the original tool if you have the source file. Problems that come from the player — fixed-size slides that do not reflow, mouse-only interactions, focus order — usually cannot be patched, so the faster fix is to migrate the content into an accessible format.
Scormbusters does both steps: a free scan with no account, and an import from the published package into lessons made of blocks designed for WCAG 2.1 AA, with a checker that flags contrast, alt text and structure as you edit. Your content and a human review decide conformance (what’s tested).
- Many WCAG failures in legacy courses come from the authoring tool's player — fixed slide sizes (1.4.10 Reflow), mouse-only interactions (2.1.1 Keyboard) — and cannot be fixed by editing the published package.
- Fixing a course in its original tool requires the source file and a license for that tool.
- The free Scormbusters scan checks a published course zip or URL, lists findings by severity and shows what a screen reader announces; it needs no account.
- No automated tool proves WCAG conformance; a human review with assistive technology is still needed.
Patch, fix at source, or migrate?
- Patch the package. Editing files inside the zip, or using a package editor, can fix text and images. It cannot change the player, so reflow, keyboard and focus problems stay.
- Fix at source.With the .story or .cptx and a current license, fix the content, use the tool’s accessible player settings and republish. Best when the source exists and the library is small.
- Remediation vendor. Specialist agencies remediate courses in their original tools, working from the source files.
- Migrate. Import the course into a tool whose output is accessible by construction. With Scormbusters the source file is not needed; interactions are rebuilt with keyboard-operable questions and a select-then-place alternative to drag-and-drop.
A plan for a library
- Inventory every course learners are still assigned, with its tool and whether the source exists.
- Run each through the free scan and sort by severity and audience.
- Retire what nobody needs; fix at source or migrate the rest.
- Test the results with a keyboard and a screen reader, then replace the packages in your LMS.
If you are a US public entity, the ADA Title II deadlines (April 26, 2027 or April 26, 2028) set the schedule. This page is general information, not legal advice.
Frequently asked questions
Can I make a published SCORM course accessible without the source file?
Only partly by patching it. You can add some alt text or fix captions inside the package, but failures that come from the player — a fixed slide that does not reflow, mouse-only interactions, a scrambled focus order — cannot be patched. Migrating the content into an accessible format fixes those at the root, and Scormbusters can do that from the published package alone.
Which WCAG failures are most common in legacy eLearning?
Text baked into images (1.1.1), slides that do not reflow at 400% zoom or on a phone (1.4.10), click boxes and drag-and-drop that need a mouse (2.1.1), confusing focus order (2.4.3), narration without captions (1.2.2), low contrast (1.4.3) and controls with no accessible name (4.1.2).
Is fixing the course in Storyline or Captivate an option?
Yes, if you have the source file and a current license. Both tools have improved their accessibility features, and fixing in place keeps the course's look. It is slow across a large library, and older player versions may still need a republish to pick up fixes.
How do I know which courses to fix first?
Scan them. The free Scormbusters scan reads a published course zip or URL, lists findings by severity, shows what a screen reader announces, and says what it could not check. Start with courses people are still assigned.
Does an automated scan prove WCAG 2.1 AA conformance?
No automated tool can. Scans find a large share of problems; conformance still needs a human review with a keyboard and a screen reader.
See what your course looks like to a screen reader first
The free scan reads a published course zip or URL and reports accessibility problems, with a transcript of what a screen reader announces. No account; your course is uploaded for scanning only and deleted immediately, never kept.