Screen Reader Can't read "Invalid Answer" message
Sep 16, 2019
Hi there, I have a course with multiple choice questions in it. I thought I had made everything accessible until I tried navigating the course using only NVDA (screen reader). My "correct" and "incorrect" layers work perfectly; but if the user clicks the 'Submit' button, the system-generated pop up displays and it is impossible to tab to the message. The only thing that is accessible is the "OK" button. So if I get this message, I have to tab around to reach the "OK" button, and if I am not sighted, I don't even know why I got the message.
I found a work-around video on how to create your own custom invalid answer slide. I was so excited! But when I test it, the audio on the slide (which is necessary for the unsighted learner to hear) plays when the user returns to the question and selects either a correct or incorrect answer.
Does anyone have any idea how to fix this? Here is what I've tried:
- Adding a "start media when timeline begins" trigger on both the 'correct' and 'incorrect' slides
- Adding a "stop media when timeline ends" trigger on the 'invalid answer slide
- Changing the feedback master - I realized that I had duplicated the 'Correct' quiz layout when I created my 'Invalid Answer' Layer and I thought that might be the problem. I completely re-did the feedback master, applied the new layout...and had the same problem
I've attached a short Story project of just a couple of the slides so you can see. If you test it, be sure to click it a couple of different ways. For me, the slide didn't work when I selected the correct answer (2nd bullet). The invalid answer message plays over the correct one.
Thanks, I look forward to hearing from folks!
4 Replies
Thank you, I will keep that in mind. I'm curious if the "Invalid Answer" popup can be read with JAWS.
UPDATE: A designer from another agency found a work-around! Attached is the Story file, with slide 1 showing my solution, which DIDN'T work. Slide 2 is the example that WORKS. Screen reader picks it up just fine.
Posting in case someone else has this issue.
Thanks everyone!
Thanks, Kelly for sharing that workaround and keeping us posted! Our team is looking into Accessibility improvements and some fixes for Storyline so I'll be sure to share this example with them.
Hi everyone,
Thank you all for continuing to share the crucial need for creating accessible content for all learners. While more work remains, we're at a point where we're confident the job done so far delivers meaningful real-world improvements for learners with accessibility needs.
I've included links below where you can find all the details on what this means for Storyline 360 Update 36:
You'll also see our general FAQ on accessibility in Articulate 360 tools here.
This release makes it significantly easier for those users to perceive, operate, and understand content published with Storyline, while opening up more choices of the browser, assistive technology, and devices for the first time. Learners will benefit from the vast majority of these improvements, even when the course author is not designing their course for accessibility.
If you have any questions or concerns, let us know here or reach out to our Support team. We know there is more to do, so we'll continue to keep you posted about future releases.
This discussion is closed. You can start a new discussion or contact Articulate Support.