I love the versatility of Articulate Storyline 2 and the ability to forego the default options for navigation in favor of truly custom courseware. However, there’s one drawback I learned of by getting rid of all the buttons that line the bottom of the Storyline course player (Previous, Next, Submit, volume, and the seekbar): navigation for the Review Quiz function is missing!
After some testing, I learned if you keep at least one course control available on the bottom, Previous and Next do in fact appear to make backward and forward movement possible while reviewing quiz results. However, if you exclude all the aforementioned buttons, your learners will get stuck as they look back at the first question. I racked my brain about what to do here, as I had a colleague frustrated with this very situation for a module he was building, and I wanted to help solve the problem. Knowing the way Articulate implements its quiz review functionality, I decided to implement my own version to get around the limitation.
In this tutorial, a practice file is provided, and a live demo is also available. I will demonstrate a different means to afford learners the opportunity to review quiz results should your modules exclude all bottom controls.
Practice File Scenario
In the practice file, you will see 10 questions, and all course player elements are turned off.
Below, you will see the Results slide, which I also customized to my preferences. Notice the Review Quiz button and its trigger are not calling upon the Review Results function. Instead, there is a trigger to jump to the next slide, which is where I have a new slide inserted to host my spiffy Review Results solution.
Looking at the custom Review Results slide, you can observe what I’ve done to make this solution happen. As you see, there are red x’s at the far left, followed by a reiteration of the question text (copied from the previous slides). At the far right, a column of graphical markers sit which I used to host feedback upon mouseover or touch.
Naturally, you may assume the red x’s will tell learners they answered the question incorrectly, which is a correct assumption. The red x’s are a shape that actually live within the Normal state of the question text objects (Q1text, Q2text, etc. on the timeline). Having the practice file open, select the Q1text object, go to States, and observe the second state called Correct. You will see in the Correct state that a green checkmark is in place. You will want the Correct state to show upon the timeline’s start if the associated variable for Q1text has a True value, which is set to False by default. That brings us to some variable work that needs to be done.
Create 10 Variables
Seeing this practice file has 10 quiz questions, you will need 10 variables (one for each question slide). As you see in the Variables list, the 10 are named q01, q02, and so on.
Each variable is set to True/False with its default value as False.
In your own module, if you have a quiz with more than 10 questions, proceed to create additional variables following the same sequence (q11, q12, etc.). Looking back to the Review Results slide within the practice file, you will see multiple triggers at the far right telling Q1text and the others to turn to their respective Correct states if their associated variable values (q01, q02, etc.) are equal to True.
How do those variable values go from False to True, anyway? Let’s look at quiz question 1 in the practice file.
The Q1 slide has three selections, with the correct selection labelled as Right Selection. Selecting that option would bring learners to the Correct layer post-submission, which will contain the necessary trigger to change the q01 variable from False to True upon the layer’s timeline start.
Slides Q2 – Q10 have the same setup, thus working with the triggers from the Review Results slide to turn Q1text and the others to their respective Correct layers and thereby displaying to learners their well-earned green checkmarks.
Feedback Mechanism: Do It Your Way
I love the graphical markers Storyline provides us! They are a great way to tuck away information (to reduce screen load) which can be accessed with minimal interaction. I recommend this setup for those very reasons, but seeing the design of the Review Results slide is custom, you can ultimately decide what works for you and what doesn’t. For instance, if you prefer verbiage to communicate correct/incorrect responses versus the checkmarks and x’s, or if you prefer another way to communicate feedback outside of graphical markers, then go for it! The canvas is yours.
Don’t Forget to Reset Your Variables
Be sure to check out the Try Again button on the Review Results slide. Notice the associated triggers that tell all 10 q# variables to go back to False, which is essential to clearing the green checkmarks upon a new quiz attempt. Also present for the Try Again button are triggers to Reset Results and Jump to Slide (to return to Q1). The same exists on the Results slide for its Try Again button.
You will notice this custom solution does not show learners what their actual selections were for each quiz question. I believe this one drawback is fair as the red x’s and green checkmarks sufficiently communicate to learners if they answered correctly or incorrectly, plus the markers at the far right provide ample room (via mouseover/touch) to explain what the correct answer was and why.
As always, if you found success with this tutorial, share with us in the comments and let us know!