QA is more than proofreading
A course can contain perfect grammar and still fail learners because a button is unreachable, feedback is wrong, mobile text clips or the LMS never records completion. Treat QA as several layers: content, learning design, interface, accessibility, technical behaviour and tracking.
1. Content and learning-design checks
- Outcomes still match the final course
- Facts, policy references and dates are current
- Examples are realistic for the audience
- Required content is distinguishable from optional detail
- Assessment samples the stated outcomes
- Feedback explains why, not only correct/incorrect
2. Navigation and interaction checks
- Every button and link works
- Back/next behaviour is consistent
- Branching routes reach the correct consequence
- Required interactions can actually be completed
- Retry/reset behaviour works
- External links open as intended
Test wrong choices deliberately. Happy-path testing misses many real defects.
3. Visual and responsive checks
Check representative desktop, tablet and mobile widths. Look for clipped text, overlapping controls, unreadable diagrams, excessive scrolling, media that overflows and interactions that assume a mouse or wide screen.
4. Accessibility checks
- Keyboard-only completion is possible
- Focus order and focus visibility make sense
- Headings and reading order are logical
- Meaning is not conveyed by colour alone
- Text/background contrast is sufficient
- Informative images have useful alternatives
- Video has captions and audio information is available appropriately
- Zoom/reflow does not destroy functionality
Use the full eLearning accessibility checklist for a deeper review.
5. Assessment checks
Test pass, fail, retry, partial score and boundary scores around the pass mark. Confirm randomisation does not create impossible or duplicate combinations and that question feedback remains accurate after edits.
6. LMS and SCORM checks
- Package imports successfully
- Launch works in learner view
- Completion is recorded
- Pass/fail is correct
- Score is correct
- Exit/resume works
- Retake behaviour matches policy
Follow the SCORM testing guide for a repeatable matrix.
7. Final release control
Record the approved source version, exported package, reviewer approval, QA date and known limitations. Keep the exact package that was tested. Re-exporting after approval creates a new artefact that should be smoke-tested again.
Put the guidance into practice
Build a real course in Lumeo, preview it in the browser, and export it to SCORM, standalone HTML or PDF. The free plan does not require a payment card.