I have duplicated this issue in the story file attached. Basically, NVDA seems to be randomly choosing an object to announce before actually reading the slide. It will also do this randomly on text-only slides. It will just announce the middle of the sentence and when I arrow down, it will start reading the slide.
My focus order is set just like you would imagine. I've been doing this a long time and haven't missed anything like that. This is a glitch.
I have tried to adjust the slide settings, the location of the last item in the FO of the previous slide, adding alt text to the buttons.......It seems like an impossible problem to solve. I can't find any logical structure to this problem what-so-ever. It just happens at random.
I tried to replicate the behavior on my end but I was unable to do so using NVDA as my screen reader. In the transcript below, you'll see that my installation of NVDA wasn't able to detect anything unusual on the same slide that you used for testing.
I'd like to ask the following to help clarify the experience:
Which version of NVDA are you using? For your reference, here is the version of NVDA that I have installed:
I have the latest updates for SL but I am using the newer version of NVDA
2023.1.
I'm glad you weren't able to duplicate this because that gives me hope that
it will work properly for others. For now, I've updated my accessibility
instructions so users won't be alarmed if this error occurs (and they will
know to ignore it and continue on through the slide).
3 Replies
Hello Mind Garden,
Sorry to hear that you ran into this issue.
I tried to replicate the behavior on my end but I was unable to do so using NVDA as my screen reader. In the transcript below, you'll see that my installation of NVDA wasn't able to detect anything unusual on the same slide that you used for testing.
I'd like to ask the following to help clarify the experience:
Looking forward to your response!
I have the latest updates for SL but I am using the newer version of NVDA
2023.1.
I'm glad you weren't able to duplicate this because that gives me hope that
it will work properly for others. For now, I've updated my accessibility
instructions so users won't be alarmed if this error occurs (and they will
know to ignore it and continue on through the slide).
Hello Tania,
Thanks for the update. Feel free to open a support case if the issue persists and we'll be glad to take a closer look at what's happening.