I have a Storyline file with groups in the focus order that the NVDA screen reader is not reading. I have triple-checked, and the groups have appropriate Alt text and are in the correct order, but the screen reader skips right over them.
Thanks for reaching out! I understand that the groups in your file aren't being read by the NVDA screen reader. I’m happy to get this sorted out with you! I have a follow-up question regarding the groups so I can understand what you are experiencing a little better.
Are the groups visible to the accessibility tools? You can follow these steps to find the "Object is visible to accessibility tools setting.
Right-click on the group
Click Accessibility
Check the box next to "Object is visible to accessibility tools".
Here is a screenshot highlighting the setting.
Also, would you be willing to share your file here or with our support engineers privately in a support case so we can help troubleshoot?
Thanks for reaching out and I look forward to your response!
I had a similar question to Ariauna and figured it might be easier to piggyback on this discussion rather than start a new one. I am currently working on a storyline 360 project and have added each text item in the focus order as I have been taught to and selected the "Object is visible to accessibility tools" box. When I activate the NVDA, it doesn't read what I have identified in the focus order. Any help would be appreciated.
Great question! I understand that NVDA isn't reading your objects even though they are marked as visible in the accessibility tools box. I'd be happy to work with you to figure out what is going on! I have a couple of follow-up questions regarding the situation so I can better understand your experience.
What type of objects aren't being read by the screen reader?
How are you navigating the course? Are you using the arrow keys for text and the TAB key for buttons?
Also, would you be willing to share your file here or with our support engineers privately in a support case so we can troubleshoot the issue?
Since I have an issue with two projects - here is the easiest one first.
For this particular project, I changed the order of the words on the tab interaction but the NVDA is still reading the original order. The first diet on the updated one is Atkins but the NVDA is still reading Paleo from the original. I know I must be doing something wrong!
Looking at the tab order because they are buttons I would have had the text on each layer and show that in the focus order when they press enter rather than add all the additional text to the alt text.
It is definitely reading them in the wrong order, never seen that
I would delete the alt text and have the label, and then add back in to the focus order the text boxes from the layers in order. This makes maintenance much easier as well.
The order is very odd and didn’t expect this to fix it just a better way to do it. Have you looked inside the states and checked alt text? You may need a support case to fix the wrong labels being read.
My goal was to create an accessible drag and drop which works but once more the NVDA isn't reading what I have on the focus order. I have attached the focus order for slide 1.2 - all the others are identical.
I see that you’ve reached out to our Support Engineers and connected with my teammate, Mcgem. You’re in great hands! We’ll continue the conversation in your support case.
Was there an update to these issues? I'm trying to test a course using NVDA and have set focus order for a slide but it isn't picking up anything on the slide. All the objects I want visible are ticked as visible to accessibility tools.
Are you using "tab" or "up/down" to navigate the items? "Tab" will jump to the next interactive element; so it will skip over text boxes and images. You'll want to use the keyboard's up and down arrows to move up and down the focus order.
Thanks Pierre. Yes I had been using the arrow keys. Weirdly enough, today they are working. Can't figure it out but delighted that I can carry on with my testing!!
I have often wondered if the issues we have NVDA skipping things when testing has to do with how SL does not carry over the alt text for all items in the timeline to the Focus Tab. I have sporadic results too, but one time, the screen reader said for my text boxes, "blank" "blank" then read the alt text for the next item, which was generally a button. If the focus order tab is what screen readers use, why is SL not automatically carrying over the alt text from the time line for us to the Focus Order tab when it is a text box?
The all text in the focus order table only shows if you have edited it or added it as in an image, otherwise it will read the text in the textbook. If the order is not what you would expect report it to Articulate who will investigate and hopefully find.
I'm glad that Phil was able to pop in and help you here.
As he mentioned, screen readers read text boxes without customizing the alt text. Be sure that you're navigating in Browse mode via arrow keys. Tabbing through content in Focus mode will not read the text boxes since these are not interactive.
We'd be happy to look at your project file if you're still experiencing issues with this or run into sporadic results in the future.
21 Replies
Hi Ariauna,
Thanks for reaching out! I understand that the groups in your file aren't being read by the NVDA screen reader. I’m happy to get this sorted out with you! I have a follow-up question regarding the groups so I can understand what you are experiencing a little better.
Are the groups visible to the accessibility tools? You can follow these steps to find the "Object is visible to accessibility tools setting.
Here is a screenshot highlighting the setting.
Also, would you be willing to share your file here or with our support engineers privately in a support case so we can help troubleshoot?
Thanks for reaching out and I look forward to your response!
Hi John,
I had a similar question to Ariauna and figured it might be easier to piggyback on this discussion rather than start a new one. I am currently working on a storyline 360 project and have added each text item in the focus order as I have been taught to and selected the "Object is visible to accessibility tools" box. When I activate the NVDA, it doesn't read what I have identified in the focus order. Any help would be appreciated.
Thanks,
Melanie
Hi Melanie,
Great question! I understand that NVDA isn't reading your objects even though they are marked as visible in the accessibility tools box. I'd be happy to work with you to figure out what is going on! I have a couple of follow-up questions regarding the situation so I can better understand your experience.
Also, would you be willing to share your file here or with our support engineers privately in a support case so we can troubleshoot the issue?
Thanks for reaching out!
Hi! Here is the AWS link - https://melanieamricheportfolio.s3.us-east-2.amazonaws.com/Amrich+Tab+Interaction/story.html
Since I have an issue with two projects - here is the easiest one first.
For this particular project, I changed the order of the words on the tab interaction but the NVDA is still reading the original order. The first diet on the updated one is Atkins but the NVDA is still reading Paleo from the original. I know I must be doing something wrong!
Looking at the tab order because they are buttons I would have had the text on each layer and show that in the focus order when they press enter rather than add all the additional text to the alt text.
It is definitely reading them in the wrong order, never seen that
The other odd thing is the title and content textbooks are describing themselves as buttons which they shouldn't be doing and they are tabable.
Here is what the layer looks like - the text is on each layer - should I delete the alt text?
I would delete the alt text and have the label, and then add back in to the focus order the text boxes from the layers in order. This makes maintenance much easier as well.
Hi so here is what I did ... but it's still reading it incorrectly.
The order is very odd and didn’t expect this to fix it just a better way to do it. Have you looked inside the states and checked alt text? You may need a support case to fix the wrong labels being read.
I have ... thank you, I'll submit a case for this project.
I have another project with a similar issue, could I ask you for help on that one?
Yes of course
Sent from my iPhone
Thank you so much!
Here is the AWS link: https://melanieamrichprojects.s3.amazonaws.com/Amrich+Drag+and+Drop+Now+Accessible/story.html
My goal was to create an accessible drag and drop which works but once more the NVDA isn't reading what I have on the focus order. I have attached the focus order for slide 1.2 - all the others are identical.
Hi, Melanie!
I see that you’ve reached out to our Support Engineers and connected with my teammate, Mcgem. You’re in great hands! We’ll continue the conversation in your support case.
Hi all
Was there an update to these issues? I'm trying to test a course using NVDA and have set focus order for a slide but it isn't picking up anything on the slide. All the objects I want visible are ticked as visible to accessibility tools.
Thanks
Eveline
Are you using "tab" or "up/down" to navigate the items? "Tab" will jump to the next interactive element; so it will skip over text boxes and images. You'll want to use the keyboard's up and down arrows to move up and down the focus order.
Thanks Pierre. Yes I had been using the arrow keys. Weirdly enough, today they are working. Can't figure it out but delighted that I can carry on with my testing!!
Hi, Eveline!
I'm so glad to hear you solved your issue. If you run into any trouble moving forward, please let us know and we'll be happy to help out! 🎉
I have often wondered if the issues we have NVDA skipping things when testing has to do with how SL does not carry over the alt text for all items in the timeline to the Focus Tab. I have sporadic results too, but one time, the screen reader said for my text boxes, "blank" "blank" then read the alt text for the next item, which was generally a button. If the focus order tab is what screen readers use, why is SL not automatically carrying over the alt text from the time line for us to the Focus Order tab when it is a text box?
The all text in the focus order table only shows if you have edited it or added it as in an image, otherwise it will read the text in the textbook. If the order is not what you would expect report it to Articulate who will investigate and hopefully find.
Hi Amy!
I'm glad that Phil was able to pop in and help you here.
As he mentioned, screen readers read text boxes without customizing the alt text. Be sure that you're navigating in Browse mode via arrow keys. Tabbing through content in Focus mode will not read the text boxes since these are not interactive.
We'd be happy to look at your project file if you're still experiencing issues with this or run into sporadic results in the future.