Forum Discussion

RiaFernandez's avatar
RiaFernandez
Community Member
9 years ago
Solved

Screen Reader Accessibility for Button States

Hi there, I'm having some trouble implementing accessibility for my Pick Many activities. Screen readers do not seem to recognize the difference between a Normal state and a Selected state of a bu...
storyline 360
  • KellyAuner's avatar
    KellyAuner
    3 months ago

    Hi, all!

    I have some great news to share! We just released a new version of Storyline 360 (Update 103), which included a fix for the issue where screen readers didn't always announce the visited state of buttons or shapes.

    To take advantage of this update, simply launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find step-by-step instructions here.

    Please let us know if you have any questions by posting here or reaching out to our Support Engineers directly. We'll be happy to help!

ArinOBoyle-919d's avatar
ArinOBoyle-919d
Community Member
8 years ago

Hello, We had 30+ training modules in Rise, and I am in the process of learning Storyline to transfer them to Storyline for Accessibility purposes-

I am trying to make sure I am up to speed on everything in Storyline that is Accessible/508 Compliant, and where there are bugs/issues that I should be aware of on the front end until we are able to get a screen reader to check our modules as we go-

Has this issue in this thread regarding Ria's question been resolved? Just wondering as I am making a list and I didn't see a final comment, but I wasn't sure if that was typical or not and I just wanted to check, thank you!