Replying to @menelion@caneandable.social
@menelion There is, but not to notify the Accessibility Settings framework, which is separate from the general "is an accessibility tool running" stuff. @FreakyFwoof
Jamie Teh
Accessibility engineer/tech lead at Mozilla. Previously co-lead developer of the NVDA screen reader. Father, husband, pianist/keyboardist, tech enthusiast, totally blind.
- Website
- https://www.jantrid.net/ verified
- Pronouns
- he/him
Replying to @FreakyFwoof@universeodon.com
@FreakyFwoof That's slightly less strange than you might think, but it still means something broke somewhere. To cut a very long, ridiculous story short, NVDA needs to integrate with the Windows Accessibility Settings in order to run on secure screens, start after logon, etc. And the way a screen reader tells that framework that the screen reader is now running is to set a temporary registry key and... inject the Windows+u keystroke. I'm not joking. No, it's not okay. Don't shoot me, I'm just the messenger. Anyway, I guess something must be going with the temporary registry key part of that horrible recipe.