Embedded Storyline accessibility issues

Hello, LucianaPiazza​  following up on this b/c we are experiencing this issue as well. I had someone test our training and they responded with this (using NVDA): 

The sentence before the 4 boxes (this is the storyline block) reads with read aloud but the text in each of the 4 boxes does comply with read aloud and skips to bottom of the page which means I would have to search around to see what still needs to be completed instead of actually hearing the directions.  

I opened on all the interaction tabs and was not able to click in the interaction to start the read aloud function.  

(this was more b/c he's unfamiliar with the tools we use and was trying to help solve the issue):
Are these interactions pictures? If they are pictures, then accompanying alt text need to be added.  If a person is using windows narrator, the tool does not function in pdfs. Read aloud is the only option. It would be more conducive to accessibility tools if the pages were not continuous, in other words possibly page breaks.  What happens is that the Read aloud functions jumps back to the start of the training when it reaches the of a current page.  The only way to get the current page to read is to scroll back down, then highlight the first word on that page and start the reading. When you are able to make a choice, for example, during the last lesson you can select summary or either of the other 2 buttons and the page reads from where its supposed instead of jumping back to the beginning of the training.