Forum Discussion
Screen Reader Accessibility for Button States
Hi there,
I'm having some trouble implementing accessibility for my Pick Many activities. Screen readers do not seem to recognize the difference between a Normal state and a Selected state of a button
I have a multiple choice question where the user can select more than one answer. I've made Normal state alt texts (Option 1, Option 2, Option 3, Option 4) and I've made Selected state alt texts (Option 1 Selected, Option 2 Selected, Option 3 Selected, Option 4 Selected). This way, a visually impaired user can know which answers he/she has already chosen before selecting the Next/Submit button.
It doesn't work though and the screen reader just reads the normal alt texts. Is there a solution around this? Thanks!
Thanks Ameba, our support team will be in touch as soon as they can - typically in 1-2 business days. Keep an eye out for an email from Support@articulate.com and I'll follow along as well.
Hi Ameba,
Just following up on your case and it appears the latest update for Storyline 360 resolved the initial issue you were experiencing.
Feel free to let Emily or I know if you need anything else!
- AmebaAaaCommunity Member
Sorry, maybe there was a misunderstanding, because the problem fixed is concerning JAWS and notes (https://community.articulate.com/discussions/articulate-storyline/screenreader-not-reading-notes-in-player#reply-458625). Actually, I published right now (update installed) an example course with two slides: the first one with multiple choice quiz and the second one with radio buttons; there is still the problem in html5 (not in flash reading correctly). Also on radio buttons, JAWS says "to change the selection press up or down arrow", but you can use only the space bar to select a radio button.
Thanks Ameba - that link seems to be this same discussion, but I reached out to Emily as well to follow up on your continued issues.
- KaraCampbellCommunity Member
Hi Ashley, I am having the same issue as Ameba:
"Also on radio buttons, JAWS says "to change the selection press up or down arrow", but you can use only the space bar to select a radio button."
Do you know if this will be fixed or if there is a current work around for this issue? Thanks.
Hi Kara,
Thanks for chiming in. Our team is currently investigating this bug. While I don't have an ETA on a fix just yet, you're in the right place to stay up-to-date on this bug's progress. As soon as a fix is released, we'll post the good news here in this discussion thread!
- RafDolanowsk896Community Member
Is there any further update on this?
I just updated my Storyline to the latest but am still seeing the issue with "not selected" being read by JAWS, even when it is selected.
Also there is nothing being read out to indicate states for shape buttons, native buttons, checkboxes or radio buttons. Both in the cases of them being independent or grouped into a button set.
Looking forward to hearing an update.
Testing in latest IE, HTML5 export using latest JAWS and Thunder. Hi Raf,
Thanks so much for chiming in. First, have a look at a screen recording of my testing in Internet Explorer 11.
In that recording, you see that JAWS announced "radio button checked" when you tab back to a selected radio button.
Our output doesn't support a "real time" change in the state of a radio button. In other words, JAWS doesn't read "Radio button selected" as soon as a user selects it in any version of Storyline. So, it's expected that you would have to tab back to a selected radio button to hear that's it's checked.
Now, let's talk about object states. We are seeing a problem in Storyline 360 where JAWS does not announce Alt Text on an object's states, and we're working to fix this problem. Does that sound similar to the issue you're seeing in your file?
- RafDolanowsk896Community Member
Hi Alyssa,
What version of Storyline did you use to create that export in your video?
As the behaviour you are showing and what I am seeing are not the same. My radio buttons always say "not selected" regardless of setup, screenreader or browser.
Glad to hear the bug with the object states is also being addressed.
Looking forward to that update, as I primary create custom buttons rather than using the native assets.
Cheers,
Hi Raf,
That video was recorded with the most recent version of Storyline.
Mind sharing one of your slides with me? I'd be happy to test it and create a similar recording for you.
- WenqingMa-268c3Community Member
Hi, Alyssa
Your video says for first distracter: "Think about the learner. Don't set up your questions as "gotcha" questions. radio button not checked. To change the selection, press up/down arrow."
The issue is when follow the instruction to press up/down arrow, the user can't change the selection status of the distracter. Instead, user could press space bar to change the selection.
So, the fix would be let JAWS read "....To change the selection, press space bar"
or
fix the up/down arrow and let up/down arrow execute the radio button selection.
Wondering if this issue has been fixed?
Thank you.
Wenqing
Hi Wenqing,
You're right, and this is a bug we are working on in both Storyline 360 and Storyline 3. We'll share updates here as soon as this bug is fixed. Thanks for chiming in!
- BirgitMuehlenhaCommunity Member
Hi Alyssa,
I'm wondering if my issue is related to what has been discussed in this thread. I have two radio buttons, both with Alt text in my Storyline 360 file.
The first radio button in the tab order (CC on) is UNCHECKED and the screen reader (both JAWS and NVDA) announce the following: Radio button 2 radio button not checked.
The second radio button in the tab order (CC off) is CHECKED and the screen readers announce: CC off button radio button checked.
If I select the CC On button and deselect the CC Off button, then the announcements are reversed:
CC On CHECKED: CC on button radion button checked
CC Off UNCHECKED: Radio button 2 radio button not checked
I tested this with 3 web browsers: Google Chrome, IE and Edge and with screen readers NVDA version 2018.1.1 and JAWS 2018.
Is this similar to the issue mentioned above or is this another issue altogether? Thanks for any help!!!
I have attached my Storyline file here if that helps.