Forum Discussion
Looking for tips on how screen readers read Storyline output
Hi everyone,
I'm looking for tips on Storyline output and screen readers. Is there a way to edit the objects so that the screen reader does not read "radio button" "group" after each object?
See me going through this example:
I've also been having issues with when a user selects a radio button and they check it, it still reads as unchecked. Not on the YouTube example above.
24 Replies
Hey Mel!
Thanks for posting your question! Like you, I'm also new to accessibility and am learning as much as I can about it, mostly through trial and error. Accessibility in E-Learning (from what I've read and the research I've done) seems to be an area that is still evolving in terms of standards and best practices, but obviously a lot is borrowed/copied from the web world.
In terms of screen reader support, for now Articulate Storyline 360 supports JAWS (you can read more about screen reader support here: https://articulate.com/support/article/Combined-Tech-Specs-for-All-Articulate-360-Apps#screen-readers) Important to note, we are having the discussion about supporting a broader range of screen readers. Accessibility in general is very important to us and an area we're making ongoing improvements in.
In terms of the screen reader saying aloud "Group" I think if you go into the Tab Order window for the slide and make some changes there, I do believe you can get rid of that. In terms of the radio checkbox, I believe that is a bug we already have logged, but I do still recommend logging it here.
Also, there's a bunch more helpful resources about accessibility I just wanted to point out:
- Designing Accessible E-Learning with Storyline 360
- Storyline 360: How to Design an Accessible Course
- Articulate Storyline and Section 508 Accessibility
- Storyline and Web Content Accessibility Guidelines
- Supported Screen Readers for Viewing Content
- 6 Best Practices for Designing Accessible E-Learning
I always do custom tab order and edit my alt text. I mean nothing ever said group but somehow it is still reading group. It is in a group but no where does it say to read it.
and then this one doesn't say to say button after Continue but it still reads button. Someone commented saying just to make buttons out of shapes so it does not do that.
PS Im sure that for you, like it was for me, using a screen reader to preview content has been eye-opening. As you briefly mentioned in your video (or at least I think you did) you almost have to tweak and edit your writing specifically FOR that purpose. For example, I Realized I couldn't say "Now that you've read/seen all the content"... because those using screen readers DIDN'T read or see the content. Anyways, been really good learning experience for me.
So surprisingly enough our accessibility advocate had said that saying read/seen is extremely appropriate. I don't know enough to say that but I trust them.
We are having the same issues with Studio and Storyline content we are creating. We have to make the content with compatible with screen readers. When we publish for HTML5 the screen reader says "group" for almost every object on the screen. We have hidden objects from the screen reader and they are being ignored properly, but the parts that can be seen become groups and the screen reader says "group" along with the alt-text we provide. How can we fix this?
Hi Daniel,
I just did a quick test and I'm not seeing this issue on the latest update of Storyline 360. What version are you using?
If you're on the latest update of Storyline 360 and still seeing it, the quickest way to resolve this issue is to have our Support Team take a look. You can submit a case here.
In the meantime, if there's anything else I can do to help, please let me know!
Is this adjustment also done for Storyline 3? (removal of the voicing of the word "group" etc.)
Hi,
Did you try testing it with another browser? I have that issue when I test with IE, but then it works in Chrome.
Robi
Same issue. Can't find "group" anywhere- in tab order or in the name of the objects but the screenreader reads "group" after all objects.
Hi Amy. Sorry to hear you're experiencing some unexpected behavior. Do you know if you're using a supported screen reader/browser? If you are, I think the next step is for us to get you into a support case so we can have a closer look at your project file.
Hi there,
Yes I'm using a supported browser- Chrome.
Amy Birkhead
Module Developer
New York University IT
Teaching and Learning with Technology (TLT)
Visit Project Engage to learn about our work
with games & simulations.NEW YORK UNIVERSITY SENSITIVE DOCUMENT STATEMENT OF CONFIDENTIALITY:
This e-mail and any attachments thereto are intended for use solely by the
addressee(s) named herein, and the contents may contain legally privileged
and/or confidential information. This e-mail message should not be shown
to or forwarded to anyone without the explicit, prior consent of the
sender. If you are not the intended recipient of this e-mail, you are
hereby notified that any dissemination, distribution, copying, or other use
of this e-mail and/or any of the attachments hereto, in whole or in part,
is strictly prohibited. If you have received this e-mail in error, please
notify the undersigned immediately by telephone and permanently delete the
original and all copies of this e-mail, the attachments thereto, and any
printouts, in whole or in part, thereof.
Hi Robi,
The issue is occurring in Chrome.
Glad to hear this is a true issue that is being worked on. Thank you.
Sure thing! :)
Hi Everyone,
I'm excited to let you know that we just released Update 36 for Storyline 360! Here are all the details.A new enhancement that has been added is learners can now use a broader range of screen readers on more web browsers and devices, including VoiceOver.Just launch the Articulate 360 desktop app on your computer and click the Update button for each application. Details here.Hello! I'm curious if this issue was ever resolved. I'm running the latest version of everything. When I try to view my project in Chrome using VoiceOver, every text object is read twice and it says group every time as well, even though I have removed the groups from the focus. It's treating each text item as two different things.
I'm relatively new to testing things with screen readers so if there's something I'm missing let me know! Thanks!
I just tried it in Safari and VoiceOver works much better there. It does not do the repeating thing.
Perfect, Jeffrey. VoiceOver is an Apple design and works best in the native Safari.
