Forum Discussion
New Storyline Accessibility bug
Hello
There seems to be a brand new bug since the October 22 update.
When a button that was previously disabled is changed to normal, the screen reader and keyboard still pick it up as disabled - it reads as 'button unavailable' and is ignored by the tab and cannot be selected by the keyboard.
However, the state shows as normal with the hover state working properly and it can be clicked with a mouse.
This seems to happen in specific circumstances - The trigger to change the button from disabled to normal is "When the timeline starts on this slide" and the button has an entrance animation.
Normally I would just ditch the entrance animations but it worked fine before the October 22 update when we accessibility tested it, the course including animations has been signed off by our client and entrance animations are blinging anyway.
Here is an example module. The current version was published using todays November update and the slightly older version was published using the October 8 update to Storyline. I would also rather not roll back Storyline to republish as there are a whole bunch of recent bug fixes that I need.
https://360.articulate.com/review/content/c5e0d117-32d3-4a2b-b91b-f5e4504765a3/review
Hi Vic!
Sorry to hear you've run into this setback!
Thank you for sharing your file. I can confirm we have this issue logged as a bug in Storyline 360. This bug disables the Focus Order when Triggers are used to change states from Disabled to any active state.
I've linked this discussion to the bug report so you can be notified as soon as a fix is in place. In the meantime, as a workaround, we suggest downgrading to Storyline 360 version 3.92.33293.0 or earlier, where this behavior cannot be observed.
Thank you for your patience. I'm sorry if this has been slowing you down!
Thanks StevenBenassi
Unfortunately some of the recent bug fixes are essential to this course so downgrading isn't really an option.Will Articulate be doing a minor release to correct this soon StevenBenassi
If we roll back to 3.92.33293.0 won't that mean we get all of the other bugs back? For example Fixed: Screen readers didn't always announce layer content and Fixed: Audio might not play as expected when using jump-to-slide triggers or adding audio to a slide layout.
