Screen reader (JAWS) not reading Prev and Next buttons
I'm creating an HTML5 course in Storyline 360, using the inbuilt player to provide Prev and Next buttons on each screen. When published, the tab key is cycling focus through all slide objects, then onto the player buttons/features as designed.
The problem is that the screen reader (JAWS) is not reading any kind of Alt Text for the Prev/Next buttons on the player, so even though they have focus, they are essentially invisible to a non-sighted user.
Has anyone else experienced this? I would love any suggestions for solutions please, as my poor client is getting seriously discouraged at the accessibility hurdles we are encountering as a result of Storyline "features".
(I would love to not have to manually rebuild the Prev/Next buttons on each screen if possible, as they have triggers attached - and besides, if the Storyline 360 output is touted as being accessible then I assume there is some way for these buttons to be read by screen readers.)