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