Applying Accessibility with new update on Storyline 360

Heyo. A few users that work with 508 compliance have rolled back to the previous build just to avoid the pitfalls of what you have described.

There is a staff post on the first page of the Articulate forums that announces the version release that you are having issues with. I believe it is the second thread with the pin icon. In that thread, several users are posting feedback. It might be interesting to read through some of them. I posted a few links there as well, pointing to other threads that further detail some specific issues. You might find a workaround in some of that. Or, at least, confirm that you are not alone.

:)

Hi Shilpa!

I'm here to answer your questions regarding our newest update!

Previously, learners tabbed to each object on a slide for screen readers to read it. That method was accessible, but it wasn’t the best experience. So we optimized slide navigation to require fewer keystrokes for screen reader users and keyboard-only users.

Now, the tab order that you define for each slide in Storyline 360 controls the reading order of text and images for screen readers as well as the navigation order of interactive elements, such as buttons, hotspots, and data-entry fields. 

Also, every object that you add to a slide is now rendered as a complete, semantic HTML element that follows best practices for web accessibility. This means learners can use assistive technologies, such as screen readers, to navigate your courses much the same way they browse web pages. It’s a familiar experience based on recognized standards.

Lastly, we've added a "Skip Navigation" button which allows users to navigate through the slide content and ignore the Player tabs.