@jcsteh I never did that, or perhaps, for whatever reason, you misinterpreted my message. I clearly said that I don’t expect every single bug I report or encounter to be fixed. Rather, I suggested that frequently used areas or apps, like the Start menu or the modern Notepad, should be given some level of priority. That’s what Freedom Scientific is doing, as demonstrated by JAWS’s performance in those areas. When you have limited resources, and when a couple of functional add-ons are already handling remote access effectively, I wouldn’t give remote integration such a high priority, especially at the cost of crippled Start menu access or buggy interaction with the modern Notepad. Meanwhile, after around eight betas, your focus still seems to be on integrating and refining remote functionality.
@NVAccess

@jcsteh And how can you be sure that Freedom Scientific has fixed the Start menu issue by a hack? Are you sure it's not a full-fledged fix? The way you insist on calling it a "hack" means perhaps you have some insider knowledge.
@NVAccess

No insider knowledge. However, at least one other user reports that this same bug occurs with Narrator, even though your own experience seems to disagree with that. If that's the case, it's almost certainly a bug in Windows. Working around a bug in the wrong layer is always going to be hacky and brittle to some extent. For want of a better analogy, it's like arguing about reality: Windows says one thing, the screen reader overrides that with its own definition. It's sometimes necessary, of course - far too often honestly - but best avoided.

@jcsteh Very much appreciated. I’d gently say my original comments did address the main issues discussed. That said, I completely understand the challenge of balancing user groups and funder obligations. Still, this current prioritization means NVDA 2025.1 is landing more like a delayed 2025.2, and the heavy focus on Remote has come at the cost of more frequent glitches and lingering unresolved issues. It’s becoming increasingly clear that NVAccess needs a couple more full-time devs. If contributors from around the world can financially support NVDA, there must be a way to work around the employment limitations under Australian law. NVDA is global now, so its development model should reflect that if it’s to thrive.
@NVAccess

I did look at your original message multiple times and I still see nothing about priority, just about history repeating itself and effectively beingtold to live with it. Maybe there's a separate post that I can't see for some reason. At any rate, even putting aside legal concerns, hiring more devs would require significant additional funding, which takes us back to the challenges of managing additional funding obligations.

@jcsteh Ah, no, it wasn't about priorities, but the topic shifted to that. I meant the original topic, and the issue being discussed, was clear enough. I meant like many P2 to P5 issues, this one is also being sort of dumped by NVAccess. And whatever the legal or financial hurdle is, it's negatively affecting NVDA in today's environment where attention to a whole host of apps and environments cannot, and should not, be handled by just a couple of full-time employed devs.
@NVAccess

We'd all probably agree more full time devs would be a good thing. We have worked very hard to make our current level of funding more sustainable, as well as securing additional funds. Hiring full time devs means being able to guarantee employment, which is a very serious commitment, and also training those devs. What you're saying isn't untrue, but the way you're saying it suggests that you perhaps underestimate our awareness of the need for more resources or the constant work that goes into exactly that problem behind the scenes.

@davetaylor2112 @bermudianbrit @andrew Indeed! I hope I didn't come across as dismissing that. It's often not obvious to US whether a bug is a Windows or NVDA bug, so we don't expect everyone else to know either. BUT, once we ascertain that something is a Windows bug, then it does also give the opportunity to complain to Microsoft to fix it. I don't think we have a specific workaround, except maybe it works in some builds of Windows.... for some users? More data is needed.