Focus order not working as expected
Mar 21, 2022
Hi everyone, I'm having an issue with accessibility whereby screen readers (we tested with NVDA) will skip some of the content in the project, or won't read it in the correct order. If you get to the end of an interaction, it will usually catch the text if you then navigate the slide in reverse, but obviously that's no good for visually impaired learners as they won't know that they have missed something! Everything is correct in the focus order. I've submitted a case about this and it seems that this is a software bug with no known fix date. In looking at previous release notes it seems that this issue has cropped up and was apparently fixed twice in the past couple of years. So my question is, has anyone else encountered this and come up with a workaround that could help while I wait for the bug to be fixed?
Thank you! Mary T.
4 Replies
I am having the same issue, but the program is not picking up any of my objects in the focus order unless it is a 'button' or there is a trigger attached to the object. This is a stop work issue for me as I cannot publish non-accessible projects. This would mean I have to go back and change every object to a 'button' in my project.
Sample:
https://360.articulate.com/review/content/fac5246a-89d3-4440-afa4-e6d4895726e7/review
Each of these things need to be accessible with the tab key. Currently, only the buttons and the objects attached to a trigger are accessible with NVDA so users are unable to access the text boxes, shapes, etc. to hear the alt text.
Hi Jessica,
I responded to a similar question here. I wanted to share the link for anyone following along.
Thanks Leslie but unfortunately the issue occurs when testing with the arrow keys.
Hi Mary,
I apologize for any confusion in my reply to Jessica. I see that you are currently working privately with Luiza, and we are investigating the issue you are experiencing.