Thanks so much itenpl who started us off with QA (and kudos to brisho, too, who was only a minute behind!).
Please post your answers here to the question: What Quality Assurance tasks do eLearning developers do?
othols has made a grand start, and I’ve copied their ideas from the previous post here to inspire everyone else.
eLearning Developers:
- Identify errors in alignment, line spacing, and kerning.
- Identify when the wrong font or colour is used.
- Identify inconsistencies in the functions of buttons or other selectable objects.
- Identify problems in timing, for example when narration does not match up with what is happening on screen.
- Identify errors in branching/logic that could prevent someone from progressing smoothly through the course.
- Document standards for personal use and use by other developers.
With this great start, everyone should be able to think of two more things that developers do. Please add them to this post.
Nothing to add – this covers my issues
Create a detailed list of any and all issues found within a course.
Ensure all media (audio and video) is properly displayed in its entirety.
Ensure the course reports correctly to the LMS.
Watch for interactions that could be confusing or “clunky”.
Check course for WCAG compliance where applicable.
Confirm that knowledge check/test answers are correct.
Discuss treatment with the instructional designer on any particularly delicate interactions, prior to completing development – to reduce guesswork.
Ensure that narration reports match the final script version, and contain necessary pronunciation guides, prior to submitting to voice actors.
Ensure accuracy when filing artifacts in the correct folder for the development stage.
Speak with the PM if a client request does not translate well in reality (i.e. yellow font on a light blue background), and options should be discussed. This will save time later on.
Ensuring compatibility with all commonly used browsers (Safari, IE, FireFox, etc.)
Confirming functionality on different devices (phone, iPad, etc.)
Confirming the accuracy of external web links
Ensuring progress isn’t lost when the user leaves the course
Catch typographical or grammatical errors that were missed
Catch inconsistencies of style, such as appearance of bulleted lists