Forum Discussion

LisaSpirko-3976's avatar
LisaSpirko-3976
Community Member
4 years ago

Non-button objects in focus order are skipped in preview and Review 360

Hi! I'm testing the focus order on a slide, and none of the non-button objects listed in tab order are getting the focus (yellow) box in Preview or Review 360. There's only one button on the slide, ...
storyline 360
  • JohnMorgan-c50c's avatar
    JohnMorgan-c50c
    2 years ago

    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.

TheresaAinswort's avatar
TheresaAinswort
Community Member
4 years ago

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?

  • LaurenDuvall's avatar
    LaurenDuvall
    Staff
    4 years ago

    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!

    • LisaSpirko-3976's avatar
      LisaSpirko-3976
      Community Member
      4 years ago

      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

Related Content