eLearning Quality Control Process (QC / QA)
Developing custom eLearning can be a highly collaborative and involved process. For courses that are fairly complex (Level 3 and higher) the QC process is more time intensive and complex. Following is a high-level overview of the major phases of the e-Learning QA (quality assurance) also know as QC (quality control) process. Note that while you may perform these QC phases at any time and in any order, we strongly recommend that the MediaQC™ be performed before the NavQC™, especially for courses that will be in compliance mode or otherwise restrict the learner’s ability to freely navigate the course. This way your QC reviewers are not unnecessarily slowed or burdened by complex and time consuming navigation issues.
The MediaQC™ is the first QC phase during which the course content is reviewed for quality and accuracy. The main focus is on the following items:
- Audio & Transcript:
- Verify that the quality of audio production is acceptable
- Confirm the voice talent read the storyboard accurately with proper inflection, speed, etc.
- If you have included a text transcript, perform a complete pass through the course listening to the audio and reading the transcript to confirm audio matches. Also, confirm that the text transcript is formatted to your liking.
- Visuals and Timing:
- Graphics are appropriate and conform to the approved storyboard (if applicable)
- On-screen text is formatted properly, checked for spelling and grammar, and conforms to the approved storyboard (if applicable)
- Visuals fade in/out in sync with the audio appropriately
- Be sure to include a test key that includes answers to all knowledge checks, activities, and quizzes. Users should be encouraged to fail and then pass all activities and test as many different use cases as possible in an attempt to identify any possible flaws/errors in programming.
- Confirm that activities function as described in the storyboard
- Confirm feedback functions properly (incorrect/correct)
- Ensure click-to reveal items function properly and check that audio does not overlap (when multiple audio tracks are layered on a single slide)
The NavQC™ is generally performed after the MediaQC™ is completed, although it can be done simultaneously. If a course is in “Compliance Mode” – for example, some pages are locked down and user is not allowed to advance until the audio completes and users cannot jump around in the course – then performing the MediaQC™ is unnecessarily complicated and time consuming.
- Main Menu:
- Page Titles: All titles should be spelled correctly and conform to the approved course outline/storyboard.
- Hidden Slides: Ensure that slides are hidden if/as requested. NOTE: it is best to show all slides in the menu during the MediaQC™ and only hide the slides in the menu after that phase is complete. This will make the MediaQC™ process easier.
- Next/Back Buttons:
- Confirm that the next and back buttons navigate to the appropriate location. This is especially important for branching courses. For example, let’s say you have a main home page in your course. Users can click Topic B to jump to that spot. The Back button on the first page should be programed to return back the Home page, otherwise it will go to the last page of Topic A by default. Similarly, the NEXT button on the last page of Topic B should return to the main Home screen, otherwise it may progress to Topic C.
- Compliance Mode:
- One or more screens can be programmed to require that the user listen to all audio pages before allowing the user to click NEXT. Confirm that compliance mode functions as designed.
- Auto Forward:
- Confirm that pages you wish to auto forward do so, and that other pages require user to click NEXT or take some other action.
The TechQC™ refers to testing back-end functionality that the average user will not see. This is where you confirm that the LMS publish settings are correct and that other technical items function appropriately.
- Test the course in the various browsers that you expect your learners to use. Major browsers include Internet Explorer, Firefox, Safari, Chrome.
- We recommend using a tool such as BrowserStack.com or manually test the course on a machine that includes all targeted browser versions.
- Player Menu Items:
- Test all player menu items to confirm that they function as desired including (if applicable) glossary, search, seek bar, volume control, etc.
- LMS Publishing:
- Version: Select the appropriate SCORM level supported by your LMS if applicable (e.g. SCORM 1.2 vs 2004)
- Course Title & Description: Many authoring tools allow you to insert the official course name and description as it is to be listed in the LMS. The LMS reads this information and displays it, so it should checked for completeness and accuracy.
- Completion Tracking
- Complete vs. Pass: Determine if a course will be show as Complete/Incomplete, Pass/Fail, or some other reporting metric.
- Completion Criteria: Is user required to pass a quiz, simply view X number of slides, or some other custom requirement?
- Publishing Format:
- Desktop Computers (Flash)
- Mobile Device (HTML)
- Android or IOS (TinCan)
- LMS Testing: Confirm the following…
- Course uploads to the LMS without errors
- Course can be assigned to a test user(s)
- Course shows up in the test user account as “not started” or equivalent
- Start and close the course. Confirm that the LMS now displays the course as “in progress” or equivalent.
- Restart the course and confirm that the course returns you to the page last visited (bookmark).
- Fail the course (if applicable) and verify that the LMS recorded this appropriately
- Pass the course and verify that the LMS shows the course as complete (or equivalent)
Note: The terms e-Learning MediaQC™, e-Learning NavQC™, and e-Learning TechQC™ are trademarks of eLearning, Inc. All rights reserved.