I must admit that the #LLMs are very good at explaining why code is causing #screenreaders to behave a certain way. Documentation on #NVDA is limited, and usually requires a lot of digging through people's complaints about things on reddit and stackoverflow.

@mikemccaffrey Which documentation is limited for NVDA? (Keen to find out if it isn't there, or if it's hidden & we need to publicise it better).

Any issues (foxed or open) with NVDA will be on our GitHub: https://github.com/nvaccess/nvda/issues

User discussions will largely be on our user group: https://nvaccess.org/nvda-users (or here on Mastodon is one of our our most active communities)

Our blog also regularly has information, and actually yesterday's has a handful of developer links too: https://www.nvaccess.org/post/in-process-10th-march-2026/

nvaccess/nvda

NVDA, the free and open source Screen Reader for Microsoft Windows - nvaccess/nvda

GitHub
@NVAccess It not so much that the mobile keyboard shortcuts are missing, as much as sometimes they are an afterthought. I haven't needed to review the official documentation recently, so it might not still be an issue.