JAWS screen reader and radio buttons SL2
Dec 10, 2015
By
Belen Ferrer
I've been doing a lot of accessibility testing lately and it looks like JAWS cannot read the text in native-to-Storyline radio buttons. When I tab to a radio button, JAWS just says "radio button" and tells me whether it's selected or not.
I have to copy the text of the radio button into the Alt Text field in order for JAWS to be able to read it. On the other hand, JAWS can read the text in regular 'shape' buttons just fine, without me having to put anything in the Alt Text field.
Have other people noticed this or is my experience unique?
39 Replies
Thanks Mark for sharing a copy of your project file - I took a look using Jaws 18 and the Microsoft Edge browser. I also didn't notice any Alt text on the Month titles so when I navigated to them I was only hearing "Tab" and "Spacebar" when I clicked to select them.
I do know the issue is with our QA team is specific to freeform interactions in Storyline 2 where the objects are being appended with the words "radio button" even though they are shapes/objects. (The other issue discussed here is for Storyline 360 and HTML5 output).
Since your file seems to behave differently for you and me, I'm going to start a support case for you so that our team can dig in a bit deeper to your file. You'll see an email from Support@articulate.com soon!
Hi Max,
I wanted to let you know that the issue where JAWS screen readers would announce selected answer choices as "not checked" in HTML5 output is fixed in the latest update of Storyline 360.
You can see all the fixes and new features in the release notes here.
Just launch the Articulate 360 desktop app on your computer and click the Update button for each application. Details here.
Hello any update on this? Is this still a known issue? We are running into issue with the latest SL3 update and going back a version to help correct accessibility issues. Thx
Hi Jeff,
We're still looking into this bug for Storyline 3, and we've got this thread tagged to be updated as soon as the fix is released. You'll be notified immediately since you're now subscribed here!
Is there is any update on the "radio button not checked" issue. For accessible users this is very misleading. With Articulate storyline we commit the content to be accessibility compliant, but issues like these are really taking us back. Hope the issue will be addressed very soon.
Hoping for an update, too. The current workaround I have is to have a button that the screenreader user can tab to to notify them which option they chose, and they can either submit it or change their answer. But we would really prefer for just selected radio buttons to be read as checked or selected.
Hi Rio and Chiranjib,
I'm sorry that this is causing you such trouble. We don't have a release date set for the next update to Storyline 3, but as soon as we do we'll let you know here. That release will include the fix already available in Storyline 360 for this issue.
Hi Ashley, Thanks for reverting back. I am using Storyline 360 V3.4.10364.0. JAWS announcing "Radio button not checked" for the ones which is already checked is an issue in the HTML5 published version of Storyline 360 version I am using. Is there an update in the Storyline 360 with the resolution?
Hello Chrianjib! Yes, looks like you're a few updates behind.
Be sure to check out the documentation here as well as instructions to update. The issue is marked as corrected in the latest Storyline 360 version.
Hi Leslie, I have upgraded my Storyline 360 to the latest version (3.10.13923.0). Unfortunately I am still encountering the same issue of JAWS announcing Check radio button to be "not checked" and additionally asking the user to use up and down arrow for change selection. I can share a a page with radio button for your reference. Though I can see this issue stands resolved according to the link you have shared, but I continue to face the issue.
We would certainly want to take a look at that Chiranjib.
Could you please share a demo page and description of the issue directly with our support team here to take a look?
Hi Leslie, I have uploaded the demo page with description two weeks back. I am yet to receive any response from the support team. Can you please follow up. Thanks in advance.
Oh, sorry to hear that Chiranjib.
Looks like Abel reached out on 12/9 with a response and this issue has been filed as a bug.
I will re-send the e-mail (be on the lookout for an e-mail from support@articulate.com in case it goes to junk/spam)l, attach this thread to the report, and we will update you when we are able.
Good news, folks! I'm excited to let you know that we just released update 3 for Storyline 3! It includes new features and fixes - check them all out here.
One of the fixes addresses an issue where JAWS screen readers would announce selected answer choices as "not checked" in HTML5 output.
Here’s where you can download and install the latest version of Storyline 3. Let me know how you make out!
This discussion is closed. You can start a new discussion or contact Articulate Support.