NVDA's instability is getting worse for me, and I just encountered a pretty nasty bug in Microsoft Word, but I don't know if it's triggered by how many elements are in each group in this document (almost 200) or what, but whenever I shift+tab or tab to change the element type to something else other than links such as headings, NVDA gets very sluggish. That's probably something to do with how that Elements feature is coded because it also takes longer than it should to come up with NVDA+F7, which you also can't do with Browse Mode on. Also read the Word portion of the NVDA User Guide and I'd say if NVDA can only do what it details in that section, then the Word support is indeed basic! What's up with that? Not that many requests I'd imagine, since apparently the Roadmap that NVAccess released didn't say anything about improving Word support, sad. They also need a much easier way for users to report bugs because telling everyone to just submit through GitHub is not the right answer. That probably hasn't been done because that would require writing something that would file the bug propperly on GitHub since they already have so many there. Oh, you need a GitHub account? Definitely not, then! I already have so many accounts!
=> More informations about this toot | More toots from GamingWithEars@tweesecake.social
text/geminiThis content has been proxied by September (3851b).