2 ms·
Yes, NVDA has some problems to do with network connectivity. It's a fairly well-known problem. It has been solved several times, and re-appeared several times,
by shakna 7y ago
Yes, NVDA has some problems to do with network connectivity. It's a fairly well-known problem. It has been solved several times, and re-appeared several times, but getting the right trifecta of Windows version, network card and NVDA version means it can take somewhere in the range of a full minute just to say "Firefox".
---
Windows isn't my daily driver, mostly because Windows 10 has at several points reset _all_ the system settings with some updates, not just accessibility. Again, this isn't an unknown problem. It may happen less often now the team seems more aware of it, but it only has to happen once to render my computer nearly useless. It's less of a problem with Narrator, and more the tightly couple nature of Windows components and the decided drop in update quality in recent years.
The part about Narrator randomly speaking is something has appeared since the XP days. Now and then a single word will squeak through when the whole thing is supposed to be on mute. It's completely unpredictable though, so I wouldn't expect it (as a programmer) to be solved at any point soon.