Help needed: Making a StoryLine SCORM file readable by a Screen Reader

Hi, Josh -- Thanks for reaching out and sorry for your difficulties! Perhaps it would be best if you were to work with our Support Engineers directly so they are able to provide additional technical insights. Please use this form to submit your case, and rather than share the published output folder as above, it would be most helpful if you could share the .story or source file. :)

I submitted a case and attached the story file to it. Thanks.

Thanks for the update, Josh, and I see that your case, 00788207, has been received in our system! I will be sure to follow along with the progress being made on your case, and I plan to share relevant updates here for others who may benefit. :)

Sadly you've taken this out of the community realm and many of us want to know how this was solved.  

Please share the outcome and summary of the fix here.  

That woukdbe greatly appreciated. 

Hi there D M, 

The support engineer on this case was able to reproduce the issue that Josh described and unfortunately was not able to determine a workaround. The issue is now in the hands of our Quality Assurance team. I cannot offer a time frame for when or if this issue will be resolved, but I will certainly post updates here as they become available!

Ok thank you for getting back to me on this.

All the best,
Diane

Absolutely! Happy to help!

Hello all any solution found for the issue?

Hello Carmelo - I took a look and it seems that this issue is still open and in the hands of our QA Team.

Are you utilizing Storyline 2 with Windows 10, IE, and JAWS? You can see our tech specs here.

I will update to reflect users impacted and this thread is attached for update when applicable as well.

Are there any more recent updates to this issue?

Hi Sally,

Thanks for reaching out. The issue tied to this conversation is specific to Storyline 2 and viewing the output in Microsoft Edge. 

Does this sound like what you are running into as well?

I have been asked this by a former colleague who still works in the region. And the team I'm on is mid rebranding LOTS of objects for our organisation.

So this question is pertinent to us (Storyline v3, no idea what JAWS version we have here, but Windows 10)

Hi Dave,

Are you running into the same trouble using Storyline 3's latest update? This discussion originated with Storyline 2, and I know that's still an open issue. 

If you've run into it with Storyline 3, we'd love to take a look! Can you share a copy of your file with our Support Team? 

Hi there

I would like to know if Articulate products (latest releases) conform with the accessbility guidelines as outline by the W3C.  

We have a potential issue and I want to ensure I have the right information at hand

Thanks in advance 

Hi Mardi,

Great question! You can find some answers in our Articulate 360: FAQs for Accessibility. 

Let us know if you have any specific questions and we'll do our best to answer them!