Forum Discussion
Roll back to a previous version of Storyline 360
Hi Omar, before you roll back, it's probably first worth looking at the individual issues.
The accessibility issue you mention, may not actually be an issue, but a change in how accessibility works. Since January this year, the Storyline slides are functioning more like a web page when it comes to accessibility (screen readers and keyboard navigation) and so it may be a change rather than something being broken? For example, text areas are no longer tabbed to (only interactive elements are accessed using tab) however, the tab index is still relevant to the reading order when it comes to screen readers. Screen readers are now controlled using Arrow keys (and other shortcut keys available to the screen reader e.g JAWS and NVDA).
The videos issue I'm not sure about, what problem do you experience?
Completion, there haven't been any issues reported with the latest version 3.43 that I am aware of. Which version of SCORM are you using and what is your completion trigger?
I'm only suggesting to check these first as the improvements in accessibility are significant and it would be great if you can continue to keep your module up to date with those improvements and pass them on to the users who need them.
Hi Sam,
Thank you for your reply. We are using both scorm 1.2 and scorm 2004 (3rd and 4th ed).
I understand that there have been changes to the way things are managed, but there are some cases where we have some clickable items on screen that used to work fine when navigating using the keyboard (tab to move between items and enter/space to click the buttons), while now they are not. And we also have cases where we decided objects should not be reached via keyboard to simplify the user experience, but now are automatically focused when moving between slides.
For the mute/unmute options, we used to apply some javascript that it's now not working anymore. We found a different code to make this work with the updated version of the software, so this would not be a problem.
Finally, for the completion issue, we found out that when opening the course with the new Storyline the 'submit result' triggers were automatically disabled and this was causing the problem. We just had to enable them again to get completion working.
So, to recap, the only open issue would be with the accessibility. I think we could use the newest version of the software when starting new courses, but to be honest having to check and readapt all the courses we previously created to the big changes that have been done to storyline will mean wasting a lot of time (and money), so I still believe it's a better option to revert back to December version.
Is this something that can be quickly achieved?
Understand completely Omar. I hope you got sorted.