Forum Discussion
Button states not reporting to screen reader users
An important WCAG 2.0 A guideline is 4.1.2 "For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be progr...
Hi David,
I have good news!
I am happy to share that we just released the newest version of Storyline 360 Build 3.37.21453.0, which fixed the issue where only the normal state of a button was read by a screen reader tool.
The next step is to update Storyline 360 by heading to your Articulate 360 desktop app and clicking "Update" next to Storyline 360.
As always, we are happy to answer any questions you have by posting in this discussion, or you can contact our Support Engineers directly.
