Forum Discussion

KennyDyer-44519's avatar
KennyDyer-44519
Community Member
2 years ago

Screen Reader Not Reading Button States

Hey everyone, I noticed that after the last couple of Storyline 360 updates, my screen reader (JAWS and NVDA) no longer reads the alt text for button states. For example, I added "visited" for the alt text under the button's Visited state. This used to work fine but now the screen reader does not read the "visited" alt text and just reads the alt text for the normal state. My screen readers are up-to-date. Has anyone else experienced this?

16 Replies

  • MarissaB's avatar
    MarissaB
    Community Member

    Hello,

    It looks like I've also run into this same issue. Do we know if this has been fixed? Or any proven workarounds? I did try adding a custom visited state with a trigger to change button states when clicked, but it didn't work. 

    • JoseTansengco's avatar
      JoseTansengco
      Staff

      Hi MarissaB,

      Sorry to hear that you ran into this issue. 

      We don't have anything new to share about the status of this bug, but I've added your voice to the report so we can notify you as soon as a fix is released. As a workaround, you can try using images as replacements for your buttons, and the interaction should work as expected. The only downside is you'll lose the press animation that's only available to buttons. 

    • StevenBenassi's avatar
      StevenBenassi
      Staff

      Hi RebeccaSiahaan-!

      Sorry to hear you've also run into this setback!

      This Storyline bug affects the visited States of buttons, as well as shapes. Causing intermittent dictation by the JAWS and NVDA screen readers. I don't have any updates to share at the moment, but I've included your voice in the bug report. We'll be sure to notify you as soon as a fix is in place.

      Thank you for your patience. I'm sorry if this has been slowing you down!

      • RebeccaSiahaan-'s avatar
        RebeccaSiahaan-
        Community Member

        Ok. Thank you! I'm trying to pinpoint guidance for my team as to when we can leverage states to signify something to screen reader users and when we won't be able to. For instance, does this impact inserted images (.png, .jpg, etc.)? I could swear I recently heard NVDA read states - maybe it was just an intermittent thing.

  • Vic's avatar
    Vic
    Community Member

    Hello was this ever resolved? I'm having this problem for the first time today. 

    • Hi Vic,

      Thanks for reaching out!

      I'm sorry to hear you're experiencing this issue. Currently, I don't have an update on this bug. MzwandileMas281 shared a workaround which was to create a custom visited state and add a trigger to change buttons to the state when clicked.

      Please let me know if that helps! I've added you to the bug report so we'll update you as soon as we have news of a fix.

      • Steph_kauf's avatar
        Steph_kauf
        Community Member

        Hello! I am experiencing the same issue, has this bug been fixed?

  • HannahRamsey's avatar
    HannahRamsey
    Community Member

    Hello,

    Just checking in to see if this bug has been resolved? I seem to be experiencing the same issue with a few slides in one of my files. Or does anyone know of any work arounds?

    Thanks!

  • Creating a custom visited state and adding a trigger to change buttons to this state when clicked seemed to work for me.

  • Hey Jose,

    Thanks for confirming this issue. I did import an image file and the JAWS screen reader did state "visited" on the Visited state whereas the button does not.

    • EricSantos's avatar
      EricSantos
      Staff

      Hi Kenny,

      Thanks for sharing what you see on your end! Unfortunately, this confirms that you're also experiencing the reported bug. We'll let you know when this is fixed and the button's Visited state is read as expected.

      In the meantime, I'm sharing this information on how we tackle bugs.

      Thank you, Kenny!

  • Hello Kenny,

    Sorry to hear that you ran into this snag. 

    We are currently tracking a known issue where the visited state of buttons or shapes is announced/read intermittently by JAWS or NVDA. I've added this ELH post to the bug report so we can notify you as soon as any new updates are shared. Just to confirm if you are being affected by this bug, would you mind replacing the button in your course with an image file that has similar states and 'alt text' and let me know if your screen readers will now read the states correctly?