Is there a way to disable the Return Key so that it doesn't advance the presentation to the next slide? The problem we have is it allows learners to skip over learning activities that they should complete.
Are learners tabbing to the Next button, then pressing the Return key to select it and move to the next slide?
You may want to add some conditions to the Next button trigger. For example, Jump to slide Next slide when the user clicks the Next button if the state of all of the objects are Selected.
This trigger will prevent the Next button from working unless the learner has clicked on all of the objects on the slide. Of course, your trigger may look a bit different depending on how your slide is set up.
I'd be happy to help you set up your trigger if you don't mind sharing your file with me! You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.
Thanks Alyssa. No, the issue is that they're able to advance to the Next slide by using the Return key which is allowing them to skip over assessment activities which don't have a Next enabled on those screens. They must complete all activities and then are presented with a Continue button on one of the layers. They can be on the base layer with only a Submit and Previous button visible and by hitting the return key advance on to the next slide.
Have you set the next button to hidden when timeline starts, or have you fully disabled it from the slide properties? It sounds similar to an issue our team is investigating where the button is disabled at the timeline start, and a workaround mentioned was:
Delete the trigger that hides the Next button when timeline starts.
Restrict the navigation so that the Next button will be in its disabled state.
You can add a trigger that would make the button Normal when the timeline reaches x seconds.
Let me know if that's not a match for your setup, as then we'll want to take a look at the project file. You can share it here with our ELH community or send along to our Support Team here privately.
You mentioned you're using Quizzing slides, so that's why you don't have a Next button. In that case, you wouldn't need restricted navigation.
I was able to reproduce the problem in a sample file on my side. Here's a quick screen recording of my testing with a demonstration of how you can work around it.
5 Replies
Hi Robert!
Are learners tabbing to the Next button, then pressing the Return key to select it and move to the next slide?
You may want to add some conditions to the Next button trigger. For example, Jump to slide Next slide when the user clicks the Next button if the state of all of the objects are Selected.
This trigger will prevent the Next button from working unless the learner has clicked on all of the objects on the slide. Of course, your trigger may look a bit different depending on how your slide is set up.
I'd be happy to help you set up your trigger if you don't mind sharing your file with me! You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.
Thanks Alyssa. No, the issue is that they're able to advance to the Next slide by using the Return key which is allowing them to skip over assessment activities which don't have a Next enabled on those screens. They must complete all activities and then are presented with a Continue button on one of the layers. They can be on the base layer with only a Submit and Previous button visible and by hitting the return key advance on to the next slide.
Hi Robert,
Have you set the next button to hidden when timeline starts, or have you fully disabled it from the slide properties? It sounds similar to an issue our team is investigating where the button is disabled at the timeline start, and a workaround mentioned was:
Let me know if that's not a match for your setup, as then we'll want to take a look at the project file. You can share it here with our ELH community or send along to our Support Team here privately.
I can give that a test. How do you restrict navigation so that the Next button will be in its disabled state.
Hi Robert,
You mentioned you're using Quizzing slides, so that's why you don't have a Next button. In that case, you wouldn't need restricted navigation.
I was able to reproduce the problem in a sample file on my side. Here's a quick screen recording of my testing with a demonstration of how you can work around it.
Does that seem to match what you're seeing?
This discussion is closed. You can start a new discussion or contact Articulate Support.