JAWS screen reader and radio buttons SL2

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
Ashley Terwilliger-Pollard

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! 

Ashley Terwilliger-Pollard

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.

Rio Sloan

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.

Chiranjib Bhowmick

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? 

Chiranjib Bhowmick

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. 

Leslie McKerchie

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.

Alyssa Gomez

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!