I've completed some compliance tests and have inconsistent results, depending on the device used when taking the test. The quizzes score correctly when launched through Chrome on a PC. However, the results are incorrect when launching through Chrome on an Android tablet, Safari on an iPad, and Chrome on an iPad.
After checking several tests, it appears all questions that are notmultiple choice are scored as incorrect. The various tests have multiple response, matching, and ordering questions.
I published from Presenter using the following settings: Include HTML5 output. I did not select Use Articulate Mobile Player for iOS or Android because the test needs to be launched and tracked through our LMS. The tests will be taken on PCs and Samsung Galaxy Note tablets.
I've attached one of the tests along with the test key. Another anomaly I've seen on the tablet and IPad is on the first page of the test where a proctor code is required. I used Wingdings as the font because I don't want the tester to see the code; however, it displays using a regular font (like Arial).
Thanks for sharing Lynnette! I was able to see the issue that you are reporting.
This is actually an issue that has been filed with our QA Team regarding multiple response questions being evaluated incorrectly when set to 'Submit All at Once'.
I have added this thread for the team and will update this thread when applicable.
The device that you are utilizing will default to standard font when the font is not available, which is why you would see Arial.
Is there an estimate as to when the issue will be resolved? And can you recommend a work-around other than changing the setting to "Submit one answer at a time" until it is resolved?
I do not have any kind of estimate that I can provide, and my workaround would be to change how it is submitted - Submit one question at a time. So, I do not have another suggestion for you at this time. I did pop in to check on the other users that encountered this issue, and the suggestion was the same.
8 Replies
Hi Lynnette!
Would you be able to share your Articulate Package for us to take a look at?
Hi Leslie!
I've attached one of the tests along with the test key. Another anomaly I've seen on the tablet and IPad is on the first page of the test where a proctor code is required. I used Wingdings as the font because I don't want the tester to see the code; however, it displays using a regular font (like Arial).
I'm eager to hear what you find...thank you!
Thanks for sharing Lynnette! I was able to see the issue that you are reporting.
This is actually an issue that has been filed with our QA Team regarding multiple response questions being evaluated incorrectly when set to 'Submit All at Once'.
I have added this thread for the team and will update this thread when applicable.
The device that you are utilizing will default to standard font when the font is not available, which is why you would see Arial.
Is there an estimate as to when the issue will be resolved? And can you recommend a work-around other than changing the setting to "Submit one answer at a time" until it is resolved?
Thank you for your quick response!
I do not have any kind of estimate that I can provide, and my workaround would be to change how it is submitted - Submit one question at a time. So, I do not have another suggestion for you at this time. I did pop in to check on the other users that encountered this issue, and the suggestion was the same.
Follow-up question about the issue: are other users only encountering this issue on mobile devices like me, or are they encountering it on PCs also?
I do believe they are having issue with HTML5. Looks like mobile devices and PC.
Hello everyone! I wanted to pop in and let you know that Studio '13, Update 9 was released today which addressed the following issue:
Fixed issue where correct responses would be scored incorrectly in HTML5 output when set to submit answers all at once
You can read all of the details in this documentation and download the latest update here.
This discussion is closed. You can start a new discussion or contact Articulate Support.