Forum Discussion
Dialogue accessibility
Hi! Just wondering if this is expected behaviour.
When a dialogue is displayed and then closed again, the screen reader:
- Reads the label of the dialog after the dialog is closed (or it says 'dialogue' if there is no label)
- Once it gets to the end of the focus order, reads the most recently visited dialogue label (or 'dialogue' if no label) again. It seems to focus on the whole slide when it does this. It happens before it gets to the player controls.
Bonus weird thing/bug:
If you activate NVDA then click with your mouse on elements (including ones that are hidden from accessibility), when you go back to keyboard control, the elements you clicked on also get added to the end of the focus order before the player controls.
https://360.articulate.com/review/content/985a380f-0762-4823-b2f1-62f0f3ba2bac/review
Hello Vic! Thank you for sharing your .story file and Review 360 link! I was testing it out on my end and saw the exact same behavior. "Dialogue" is announced even when the layer isn't open. I also connected with our Engineering team, and we found this is, unfortunately, a bug that occurs when using NVDA. We don't see that same behavior when using another screen reader like JAWS.
I've logged this as a software bug, which will help our team begin investigating. I don't have a timeline for a fix, but if you're looking for a workaround, you should use JAWS instead of NVDA.
Thank you for bringing this to our attention!
Thanks LaurenDuvall I'll let our client know. Were you also able to test the bonus bug? I think people should be able to swap between methods of navigating the page without this happening.
Yes, Vic! I've also shared this with our team. We'll update you when we have a fix.
