Forum Discussion
Screen Reader don't detect elements
In my project I added Alt description to elements like buttons or images, but when I am previewing Screen Reader dont detect the elements such as text boxes or images even they appear in the focus order section. Also when it gets a button it is reading as "UNKOWN" and each one has its own description.
I am using NVDA screen reader .
Hi Cindy,
Thanks so much for reaching out! Sorry to hear you've run into this snag with Alternative Text and the Focus Order in your course. Happy to help!
Would it be possible for you to share your .story file in this thread or privately in a support case. I'd like to take a closer look at your setup.
Looking forward to hearing from you! ✨
Just confirming: are you 'tabbing' through your course, or are you using the up-and-down keyboard arrow buttons? You'll get a different read experience based on that navigation technique.
I am using tabbing for interactive elements and up-and- down keyboar arrow buttons for text, but in some slides is not working
Hi Cindy!
Thanks for the clarification!
I noticed you opened a support case for this issue some time back and had been working with my teammate Philam. I've added the feedback you shared to your case, notifying Philam so he can continue troubleshooting with you.
We can continue the conversation in your support case to help keep all information in one spot.
Can you update this thread when it's resolved? I'm having the same issue. It doesn't matter what I put in the alt text box in focus order, it won't read text unless it's an object that the user can interact with. I have to turn the text box into a button that does nothing for the screen reader to process it. I'm just using the default Windows screen reader. I'm using tab, and the arrow keys, nothing works.
Hi Randy!
Sorry to hear you've also hit a snag with Alt Text not being read by the Windows screen reader.
It would be easier for myself and other community members to assist if we could take a look at your project file. Would you be willing to share a copy of your .story file here in the discussion or privately through a support case?
We'll delete it when we're done troubleshooting!
