Forum Discussion
Quiz not allowing student to select answer choice in quiz
Hello folks,
I'm hoping someone has had a similar situation and been able to find a solution. I have quizzes that contain multiple choice questions. There have been reports from students that are sometimes unable to select an answer choice. The blue highlight bar that normally appears while hovering over an answer choice does not appear and when clicking on an answer choice it is not selected (i.e. the radio button does not show that it has been selected). Interestingly everything else that can be clicked in the quiz works, including the volume slider, previous and next buttons, and the question list dropdown menu.
The quizzes are delivered via an LMS and are published in QM'13 using SCORM 2004, 4th ed. I don't believe the problem to be a browser issue as I've switched browsers and the same problem occurs.
What's makes this even more difficult to solve is that it only happens intermittently. Most students are able to get through the same quizzes with no problems.
Any ideas? Would you lean towards this problem being caused by the LMS or a glitch in QM'13?
Thanks for any feedback any of you might be able to provide.
Best,
Steven
Awesome, Tyler. Thanks for chiming back in to share an update.
Has this issue been resolved? These posts are 6-7 years old. For me the problem is occurring in a course originally built in Articulate 9.0. I updated the course using my 360 account but learners are not able select any options from multiple choice/multiple answer questions. T/F and single answer questions work fine. Any suggestions? I guess I could rewrite all these multiple answer questions but I'd rather not.
Hi, Rich.
I'm sorry you're experiencing those issues with multiple-choice questions!
The posts above are not only older but also from different versions and with different solutions. If you go back a page in this discussion, you will also notice we fixed the bug we had logged for Articulate 360 related to this issue four years ago.
I'd be happy to look at your specific .story file to troubleshoot what's happening in your project. Would you feel comfortable sharing your file here or privately through a support case?
Hello everyone,
We have a similar problem, we have built an assessment with single or multiple choice questions, and we have uploaded the e-learning in SCORM 2004 on a LMS platform (Edx).
We don't have this problem directly, but for the moment 2 users have this problem via their account, and we have seen this.
No selection of possible answers, all other buttons work, but impossible to select answer choices.
Have you provided any technical solutions to counter this bug for the last 4 years?
Thank you for helping me.
I actually encountered a similar problem here in 2021! It was in the LMS itself, you would get to the question and it would just freeze almost. You couldn't select any answers whatsoever. You could click the custom submit button, but it wouldn't advance you because you hadn't made any selections.
We discovered that it was because two slides back, there was a random unassigned "submit" trigger on a Correct layer. Apparently, that Submit trigger was still sending a TinCan "Pass" verb to the LMS. So, once you clicked continue, the verb would send, and you'd make it a couple slides to the next question (a multiple response) and it would freeze.
Deleting the unassigned "Submit" trigger seemed to work. I'm not saying that's what it was necessarily, but we were able to get through this time in the LMS. Phew! I just wanted to get on here and add in case anyone else ended up having the same problem and stumbled across this older thread. :)
Alternatively, I just encountered another case where we weren't able to select the radio buttons, and it has happened often in the past. It appears that the radio button selections were located at the bottom of the slide and partially obscured by the invisible surface area of the textbox directly above them.
So, maybe try selecting the multiple-choice object and moving it to the top of the slide. It's such an easy issue, but one that could go unnoticed, I think. :)
