Pinned Reply
Hi Lisa and Theresa!
Good news! We are no longer seeing this bug where content published to Review 360 isn’t accessible via screen reader. Please let us know if you're still noticing the issue, we'd love to continue troubleshooting with you in a support case.
8 Replies
I just upgraded to 1.48 and now I am having the same problem. Also using NVDA. I need preview and review 360 to work the same way as the published content so that I can test it before I publish it. I feel like I have just lost functionality instead of gaining it with this update. Staff, is this something that can be fixed in the next update?
Hello Lisa!
Thank you so much for sharing your .story file! I started by testing the course in Review 360 and also publishing the course for Web. Here's a quick Peek of my test: Link
Please let me know if you have additional questions! You can also reach out to us in a support case. Whichever is best for you!
Hi Theresa!
I'm happy to help! Storyline 360 as an authoring tool is not an accessible tool. To test your course to experience what your learners will experience using assistive technology, we recommend publishing for Web.
This is still a conversation we are having in regards to our accessibility journey. Our priority was to make the published output accessible. We'll update this discussion if our team decides to make improvements to the authoring side.
I really appreciate you taking the time to share this feedback with us!
Hi Lauren, Please do. Prior to this "upgrade" the Preview mode and 360 Review functionality mirrored the Production functionality, which is what designers need. Both of my current projects have a couple hundred slides / layers. I test / tweak functionality as I go. I takes much longer to publish than to preview... This is reducing my efficiency. That is never a win... My QA team uses 360 review to do a first test for accessibility and provide feedback. We have now lost that ability, making 360 review less useful and the feedback process more laborious. My current projects will go to 60,000 learners, not sure how many have accessibility needs, but NVDA is the go to tool as it is free - vs JAWS that has a price point in the thousand plus range. I urge you to ensure it works with NVDA, and to ensure the preview / 360 Review mirror the published environment.
Thanks for considering this. :-)
Hi Lauren. I agree with Theresa. Preview mode and Review 360 both need to mirror what the course will be like in production. This is independent of whether you make the authoring tool itself accessible. The courses we test in those modes/tools need to reflect the actual accessibility they will have in production. Otherwise, Preview and Review 360 become unreliable for testing, and the workaround of publishing to Web becomes just like all of the other workarounds we have to do to make things work in Storyline: laborious and time-intensive. Just weighing in with my two cents, for what it's worth. Thanks for considering it. ~Lisa
Hi Theresa and Lisa,
Thank you for your feedback. I can understand the need to have the content accessible in Review 360.
I've shared your feedback with our team and attached this conversation to our internal report so that we can share any additional information with you here.
Thank you, Leslie! Please keep us posted, if you can.
Hi Lisa and Theresa!
Good news! We are no longer seeing this bug where content published to Review 360 isn’t accessible via screen reader. Please let us know if you're still noticing the issue, we'd love to continue troubleshooting with you in a support case.