Open XLTechie opened 4 years ago
Hi, this indeed requires an external fix (specifically from Microsoft’s Windows Shell team; I know one engineer from that team, but don’t know her GitHub handle at the moment; I can try messaging her on Twitter). Thanks.
Hi, the following feedback was filed four months ago (by someone else, not me): https://aka.ms/AA9bjoz
@XLTechie, @josephsl is the Microsoft bug fixed in the last Windows 10 updates? Or is this issue still reproducible with NVDA 2024.3 Beta?
I unfortunately do not currently have access to updated Windows 10 to test this.
Hi,
July 2024 update: not resolved and unlikely to be resolved unless Microsoft looks into this before October 2025 (tested on a virtual machine running Windows 10 Insider release preview channel build).
Thanks.
Is your feature request related to a problem? Please describe.
When opening Windows 10 Action Center, the following is spoken:
The first item, the one I expect to be interacting with, at least at the moment on my system, is:
However, NVDA is not interacting with the brightness slider. In fact it appears to be interacting with nothing. But if I press tab, followed by shift+tab, I am then interacting with the brightness slider. From a UX prospective, and intuitively, if I open a window, the item I'm focused on should be the same one reached by the compound action of Tab followed by Shift+Tab. But instead, opening Action Center leaves one in limbo.
Describe the solution you'd like
Upon opening Action Center, I would expect to hear:
And I would expect arrow keys at this point to be immediately changing the brightness slider's value.
Describe alternatives you've considered
Leaving it the way it is. What NVDA speaks is correct to what actually happens: when opening Action Center, no control is given keyboard focus, and so no control is spoken. So the current behavior is correct in as far as it goes, it just doesn't seem to be what a user would expect. Not this user anyway.
A point for the other side: Narrator behaves the same way. So perhaps this is intentional behavior on Microsoft's part.
Additional context
Here is the devInfo for the focused object when Action Center opens: