Hi everyone, I’m writing to get some feedback on an issue related to focus movement within a web app.
I’m conducting tests with NVDA to evaluate the accessibility of a digital reading app. The app includes a button that allows users to switch between the fixed-layout version and the reflowable-layout version of the text, without changing the web page’s URL.
Keyboard focus is moved to the reflowable text container using JavaScript. NVDA’s system caret does not change position and remains in the same area of the page where the button was located, even though the page content has changed. From my perspective, this can be quite disorienting for blind users who use a screen reader.
I would expect the cursor to automatically follow the movement of the keyboard focus—as happens when a modal dialog box opens.
Any thoughts on this?
First step might be to double-check settings in the review cursor category, and see if they make any changes/difference.
--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/f21b4e10-ae59-4f56-aadd-90de6cd28dc9n%40nvaccess.org.