Forum Discussion
Issue with visited state of buttons not reading in NVDA
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!
Hi, is there an update on this issue? I am experiencing the same with buttons and NVDA. I expect that all screen readers have the same issue with buttons and Articulate Storyline as the accessibility does not seem to be built in here. Thank you. Martin
Hi Martin!
Sorry to hear you are also experiencing functionality issues with buttons in your course and the NVDA screen reader!
I don't have any updates to share at the moment, but our team is actively monitoring the bug that causes visited states of buttons to be read intermittently by NVDA.
If you'd be willing to share your project file here in the discussion or privately through a support case, I'd be happy to test it out to determine if you are being affected by the same bug.
Looking forward to hearing from you!
Hi Steven, Thank you for your reply. I have created a post regarding the issue where I shared the file as it is associated with another accessibility issue to do with focus/layer.
