Is there a clear guide on using NVDA screen reader with Storyline output?

Hi Rupert, I have the same issue when testing, which I think relates to the ability to get "into" the right landmark for the screen reader in the first place (out of the browser "shell" if that makes sense, and into the Storyline page content). Once I can get it reading it seems to work fairly consistently as long as I don't switch to using the mouse, or switch up between using the NVDA commands to navigate and using the Tab key to navigate. I understand that Articulate made the difference between tab and arrow key on purpose a few years ago, supposedly to help the experience for sighted keyboard users, but I'm hoping unsighted screen reader users (who I guess we can assume are super users of their screen reader) are finding it easier to get going than I am with my limited NVDA familiarity.