Issue with visited state of buttons not reading in NVDA

Jan 27, 2023

We have a page which is a simple click and reveal in a popup. Functionality wise the page is working fine. Only in the accessibility testing on NVDA, we are observing that the NVDA is not reading the state change after button click  as visited. For example - for the 1,2 and 6th button clicks, NVDA is properly reading the state change of button as 'visited', but for the rest of the buttons (3, 4 and 5th)it is not reading the state change as visited. We have populated the accessibility text wherever required. We even tried the buttons with shapes, images and default buttons. but to no avail.  Any suggestion will be helpful.

7 Replies
Kelly Auner

Hi Kirsten,

Thanks for reaching out!

I don't have an update on the bug John referenced above, but if you're comfortable sharing your file with us, I'd be happy to test it on my end to confirm this is the cause. You can upload it here or privately in a support case, and we'll delete it from our systems once troubleshooting is complete.

Steven Benassi

Hi Martin!

Sorry to hear you are also experiencing functionality issues with buttons in your course and the NVDA screen reader!

I don't have any updates to share at the moment, but our team is actively monitoring the bug that causes visited states of buttons to be read intermittently by NVDA.

If you'd be willing to share your project file here in the discussion or privately through a support case, I'd be happy to test it out to determine if you are being affected by the same bug.

Looking forward to hearing from you!