Announcing Storyline 2 Update 5

May 07, 2015

Hi everyone,

I'm pleased to announce that Storyline 2 Update 5 is now available. This update makes it easier to create accessible e-learning content, improves HTML5 performance, and of course squashes lots of bugs. Read all about it now (or just jump over to the update page).



208 Replies
Fiona Macelli

Thank you for the update - the Tab Order window was so necessary for creating accessible content - this was the reason we upgraded to 2 and I'm very happy with it so far.

Question: There is a note in the release notes that says "Added feature to skip player navigation when tabbing through elements with a screen reader (Flash output only)".

How does the course author enable that, or does it happen in the back-end via the user's screen reader?


Fiona Macelli

Also, there's this note: "Added feature to adjust player font size up to 200% (Flash output only)".  I didn't notice a button when I published. Do I need to enable that feature somewhere?

Now that you've got a solid feature set to support accessibility requirements, I'd love to see a tutorial, article or webinar specifically on designing accessible content.


Sarah Blatnik

Back in May after I installed Update 5 I opened a support incident regard the fact that after saving my multiple choice question slides would change any text box with more than one line, into a single line text box that would not fit on the slide. I also reported that it was altering my font sizes. I was asked to "Repair" my Articulate installation. In case you are unfamiliar with this process, according to Articulate "Repair" means uninstall and reinstall. After wasting an hour of my time "Repairing", the problem was not fixed. I was told they could not reproduce the problem and to do a more extensive "Repair" - uninstall and run some sort of Registry cleaning tool. I did not have time for that. I did my own troubleshooting and found a workaround. I reported it to Articulate support and they agreed that it was reproducible and was a bug. Now, I need to reuse the content affected by this bug. I contacted Articulate Support and was told that this "known issue" had not been addressed. So now I am redoing all of my projects that are affected by this "known issue". When can we as Articulate users expect these "known issues" to be addressed? It is unconscionable for Articulate expect us to waste valuable time fixing problems introduced by bugs in the software.

Ashley Terwilliger-Pollard

Hi Fiona,

Here is the information on how to skip the navigation, and then to adjust the player font size.

In regards a tutorial, a lot of it will still be audience dependent, so it's hard to say as a whole how to make accessible content, but there is a great free e-book here that may help you get started. 

Ashley Terwilliger-Pollard

Hi Sarah,

Thanks for reaching out here and I see that you were working with my colleague John. He's reported the issue to our QA team, but we're unable to offer a time frame in regards to when we'll hear back regarding a fix or an update. We'll keep you posted in the case that you submitted once there is additional information to share. 

Justin Grenier

Hey Robin!

I don't see that we heard back from Vicki on this, but our testing shows that Error Number 80070652 seems to happen when running 2 different application installers at the same time.  If this doesn't ring a bell, I'd recommend rebooting your machine, re-downloading our installer, and starting installation again.

If the problem persists, please submit a Support Case so that we can work more closely with you on the problem.  Thanks!

This discussion is closed. You can start a new discussion or contact Articulate Support.