Disabling the question if Correct
May 29, 2020 12:00 AM
Is there a way to set a question to be disabled?
In a question type with a set number of attempts Lectora (v18.2.3 at least) always allows up to "that many" attempts. Therefore, if you have set the Attempts to 2 (or 3 or 4), then proceed to answer the question Correct on the 1st Attempt, you're still able to change the answer (and also the selected Radio Button selection).
This is most noticeable when developing to WCAG as the learner's tab-focus can be pushed back into the question. In addition, a learner can alter the Radio Selection, take a screen-cap and falsely claim the a selection to our support group. Other work-arounds have been unsuccessful as accessibility keystrokes can still function, and heavy customization with a large number of questions is not ideal.
Ideally:
- Incorrect Response shows 'incorrect' feedback - keeping question active
- Final Attempt shows 'Feedback for Maximum Attempts' - deactivate question
- Correct Responds shows 'correct' feedback - deactivate question regardless of attempts
undefined
Discussion (4)
Hi Tim, thanks for the quick reply,
On a 2 attempt Question, I put in a few extra ProcessQuestion actions, an extra one below the original under the "Submit" button (with a condition that the answer "Is Correct"), even tried a third one OnShow of the Correct Feedback. Didn't seem to have any effect.
The radio buttons are still active for a 2nd attempt and I can select the wrong answer (after the Correct feedback on the 1st attempt) and prompt the incorrect feedback. (also can still tab-focus back into the question)
D.
An attempt is counted when the question is processed. To use up all attempts if correct, just process the question as often as necessary.
It was working in my test with a simple multiple choice question.
Thanks Tim!
As soon as I move the second process question into a run action group it seemed to work fine, perhaps there was a conflict where I had it before. Viewing your example to reference was quite helpful. Thank you again!
Discussions have been disabled for this post