Preflight Checklist
Electron Version
30.0.0-beta.8
What operating system(s) are you using?
Windows
Operating System Version
Windows 11 22631.3880
What arch are you using?
x64
Last Known Working Electron version
30.0.0-beta.7
Expected Behavior
NVDA screen reader can properly read elements in Electron app.
Actual Behavior
NVDA screen reader fails to read elements in Electron app.
Testcase Gist URL
No response
Additional Information
Reproduce steps:
- Download NVDA (https://www.nvaccess.org/download/) and run
- Make sure the mouse tracking is enabled (by default it was for me), even without running through the setup the software would begin working
- Move the mouse over the standard Electron app
- Observe on
30.0.0-beta.8 and later that this doesn't really follow the mouse and just detects the 4 item list group heading
- In prior versions (
30.0.0-beta.7) and earlier this will properly read each text element the mouse moves over
It appears this change #41256 broke the behavior. Looking at the accessibility tree in MSAA (Microsoft Active Accessibility) mode within the Inspect.exe tool (available in the Windows SDK) it looks like the extra pane and sibling are shown from the above change - when I mouse over elements the empty pane is incorrectly discovered, which I suspect is leading to this behavior.
Note: This could be a NVDA bug as well, but reporting here for visibility and in case there's a known fix that could be done.
Preflight Checklist
Electron Version
30.0.0-beta.8
What operating system(s) are you using?
Windows
Operating System Version
Windows 11 22631.3880
What arch are you using?
x64
Last Known Working Electron version
30.0.0-beta.7
Expected Behavior
NVDA screen reader can properly read elements in Electron app.
Actual Behavior
NVDA screen reader fails to read elements in Electron app.
Testcase Gist URL
No response
Additional Information
Reproduce steps:
30.0.0-beta.8and later that this doesn't really follow the mouse and just detects the 4 item list group heading30.0.0-beta.7) and earlier this will properly read each text element the mouse moves overIt appears this change #41256 broke the behavior. Looking at the accessibility tree in MSAA (Microsoft Active Accessibility) mode within the Inspect.exe tool (available in the Windows SDK) it looks like the extra pane and sibling are shown from the above change - when I mouse over elements the empty pane is incorrectly discovered, which I suspect is leading to this behavior.
Note: This could be a NVDA bug as well, but reporting here for visibility and in case there's a known fix that could be done.