Somebody save us from vibe coded #NVDA add-ons. The latest has a global shortcut layer that can only be activated once, and then needs NVDA to be restarted for it to work again. 🤦♂️
@Bri I wish I didn't have to agree with your last sentence, but I do. The thing with Spotify is that you can actually use it, but it's such a pain that nobody would want to. I had cancelled for a few years before this add-on came around, and only subscribed a few years ago because of Blindspot. If this add-on were to disappear, I would cancel again and wouldn't bother. Maybe people who like music more than I do would put up with the annoyances, they're not for me.
@Bri We could do that. I'm not convinced running two copies of NVDA would be better than running one, though. Particularly as that separate app wouldn't need such deep keyboard hooking, and wouldn't be able to as easily output braille, for example.
I agree with you that there are certain tools that simply don't belong in a screen reader. In this case, it's close enough to making a shitty program (Spotify) more accessible that it doesn't cross the line for me personally.
Having just installed the latest version of the add-on (1.6.0), the new global keyboard layer only works once for me and then can no longer be invoked until NVDA is restarted or plug-ins are reload...
@Bri I don't fully agree with you on this one. The add-on is legitimately useful when it works, and the alternative would be a separate (probably huge) app with global keyboard input, gesture remapping, speech output, etc. needing to be rebuilt.
That said, it does a lot of add-on stuff wrong, like implementing its own autoupdate mechanism for some reason. And the whole not currently working thing.
Cleverson
Unknown parent • • •Tech Singer
Unknown parent • • •James Scholes
Unknown parent • • •@Bri We could do that. I'm not convinced running two copies of NVDA would be better than running one, though. Particularly as that separate app wouldn't need such deep keyboard hooking, and wouldn't be able to as easily output braille, for example.
I agree with you that there are certain tools that simply don't belong in a screen reader. In this case, it's close enough to making a shitty program (Spotify) more accessible that it doesn't cross the line for me personally.
James Scholes
in reply to James Scholes • • •The issue for this delightful behaviour:
github.com/InfiArtt/accessify-…
Global keyboard layer only works once per NVDA session
jscholes (GitHub)James Scholes
Unknown parent • • •@Bri I don't fully agree with you on this one. The add-on is legitimately useful when it works, and the alternative would be a separate (probably huge) app with global keyboard input, gesture remapping, speech output, etc. needing to be rebuilt.
That said, it does a lot of add-on stuff wrong, like implementing its own autoupdate mechanism for some reason. And the whole not currently working thing.