I have a storylinen static slide which has: Heading+ content + 2 pointers and a button. NVDA screen reader automatically reads all the content including the alternative text for the button which does not give the user enough time to read to press tab to access the button.
How can I fix this issue? I want the nvda reader to read heading + content + 2 pointers and then prompt the user to click on the button. Once the button is clicked, then I want the nvda reader to read the alternative text for the button contents. I have attached the relevant screenshot and am happy to provide the relevant storyline file as well.
Bottom line: I want to make this slide accessible and fully functional with screen readers.
NVDA will automatically read the slide content unless a user navigates to an object. This is the same experience when using a screen reader with a webpage. Are you able to navigate from Heading to the content to the two pointers and then the button?
Additionally, NVDA will read the alternative text for buttons if the buttons have alternative text. Have you added alt text to each of the buttons?
Can you provide more details as to how you're navigating the course?
1 Reply
Hello Srivani!
NVDA will automatically read the slide content unless a user navigates to an object. This is the same experience when using a screen reader with a webpage. Are you able to navigate from Heading to the content to the two pointers and then the button?
Additionally, NVDA will read the alternative text for buttons if the buttons have alternative text. Have you added alt text to each of the buttons?
Can you provide more details as to how you're navigating the course?