Prevent interim results slides from being read by screen readers
Feb 24, 2023
Hi - we have an assessment that calculates results on 10 sections and then reports the total as well as 'scores by module' to the user when the quiz is submitted.
Based on what i've seen in the forums, the way we have it now is the suggested way to do it - there must be a result slide for every module score in order to get the subtotals, but we set them to submit results as soon as the timeline starts on the slide and move to the next calculation (jump to next slide when the timeline starts) - then the overall results slide is shown. From the user's perspective they see only 'submit' and then 'overall results'.
This works fine unless you are using a screen reader - the screen reader (using nvda for testing) still stops to say "results screen 1, results screen 2, results screen 3" before reading the content on the overall results page.
So i'm looking for an option to calculate those interim results without the screen reader feeling it has to interpret that content.
3 Replies
Hi Patricia,
I'm sorry to hear you're hitting this snag! I want to create a sample Storyline project and test it in NVDA to look at this issue, but I'm not sure I have all the details I need to reproduce the problem. It would be helpful to see your Storyline file to have the same setup that you have. Do you mind attaching your project to this discussion or privately in a support case?
Thanks for your patience!
Hi thanks for replying! a team member actually solved this (yesterday) - i didn't realize that as long as the results slides were present in the project, even if you didn't go to them and 'submit' the individual results, when you 'submit' on the overall results slides, the variables we need for each module have been calculated. So we moved all the interim results slides off to a scene that doesn't get touched and it works! We have an open case for a related issue: #03492840
In that one we don't have a resolution.
Hi, Patricia!
I'm glad to hear you and your team were able to resolve this issue. I looked into your support case and saw that after testing your file, my teammate, Ronaziel, discovered the issue is related to a possible software bug we are tracking. I'll link this discussion so we can update this thread when we have news to share!