StoryAudit

← Back to storyaudit.app

Storyline QA checklist: what to check before a course goes to the LMS

Most Storyline QA is done by clicking through the published course. That finds what a learner would see. This list is the rest.

The checklist

The manual pass

Publish, open the output, click every path, keep a spreadsheet. It works for what is on screen. It cannot see a write-only variable, a duplicate media file or a completion setting, and it has to be repeated in full after every fix, because the fix may have moved something. For a compliance course that goes through six review rounds, that is six full passes.

Run it in StoryAudit

Drop the .story file into Health Check. It reads the project file in your browser, nothing uploads, and runs the list above as nine check sections with a findings rail that keeps counts and severity in view. No Storyline license needed.

Findings can be waived with a reviewer name and timestamp, exported as a review record PDF, and shared with a team so nobody re-reviews a known exception. Exports: text, JSON, self-contained HTML, PDF or email, plus a separate CSV of accessibility gaps.

Run the checklist on the bundled sample course. No sign-up, no file of your own needed.

Open the live demo →

Whole libraries

Batch Check runs the same Health Check across a folder of courses into one sortable table, with pass/fail policy rules you set once (quiz scoring, accessibility, media size, broken references, style guide) and a settings-consistency check that flags any course whose completion tracking, quiz defaults or player settings differ from the majority.

↑ Back to top