Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Windows Magnifier to follow NVDA virtual cursor #12539

Open
CyrilleB79 opened this issue Jun 11, 2021 · 1 comment
Open

Allow Windows Magnifier to follow NVDA virtual cursor #12539

CyrilleB79 opened this issue Jun 11, 2021 · 1 comment

Comments

@CyrilleB79
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

As a visually impaired person, I am using NVDA in conjunction with Windows Magnifier.
That works quite smoothly in applications such as Windows Explorer or text editors, since the magnified view follows the caret or the focus.
However on the web, the magnified view does not follow the virtual cursor (browse mode cursor) and what is read by NVDA often cannot be seen on the screen, unless an element making the focus move is encountered (e.g. a link).
I did not test recently, but I think the same issue occurs with Zoomtext and probably with other magnification tools.

Describe the solution you'd like

NVDA should inform the Magnifier of its virtual cursor's location so that the magnified view can follow it.
Note that Windows Magnifier follows the narrator's cursor on the web.

Describe alternatives you've considered

None

Additional context

N/A

Notes

@LeonarddeR
Copy link
Collaborator

The vision framework should offer you everything you need as long as there is an option to tell the windows magnifier the virtual cursor position (like with Narrator. However, I'm afraid this is a private API only Narrator is allowed to access, or it is the magnifier that accesses Narrator, I don't know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants