Embed Notice

@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