Thank you for sharing a sample .story file so I could look at it. However, I am unable to replicate the behavior you are reporting.
When navigating via the arrow keys, the screen reader reads the text. I'm attaching a screenshot of the speech viewer for reference:
When using a screen reader, the Tab key is used for navigation from one interactive object to another, which is why it typically works for buttons. To navigate text and interactive objects, you would use the arrow keys. You can read more in this article, Storyline 360: Slide Content Is More Accessible.
What version of NVDA are you currently using, and what browser/version did you test it with? I'm using:
2 Replies
Hello Bhupendra!
Thank you for sharing a sample .story file so I could look at it. However, I am unable to replicate the behavior you are reporting.
When navigating via the arrow keys, the screen reader reads the text. I'm attaching a screenshot of the speech viewer for reference:
When using a screen reader, the Tab key is used for navigation from one interactive object to another, which is why it typically works for buttons. To navigate text and interactive objects, you would use the arrow keys. You can read more in this article, Storyline 360: Slide Content Is More Accessible.
What version of NVDA are you currently using, and what browser/version did you test it with? I'm using: