On Wed, Apr 7, 2021 at 07:27 AM, Chris Smart wrote:
Windows is universal to all NVDA users.-
And even though this is absolutely true, NVDA documentation should not focus on Windows commands, either. Of course some will come up incidentally as you can't divorce a piece of software, in this case NVDA, from the ecosystem it runs under, which means that "natural interactions" between the two will occur in any user manual or similar at certain moments.
But it should be presumed that someone coming to NVDA is and has already been a Windows user and already knows the keyboard shortcuts used to do things like cut, copy, paste, save, save as, and the list goes on and on.
In addition, there is really excellent documentation for NVDA and for virtually any Microsoft offering you can name, including Excel. You're going to need both, but the commands for NVDA have nothing to do with Excel (and, no, I'm not counting dedicated add-ons, which are another discussion) nor do the Excel commands have anything to do with NVDA. You can insert any of the following in place of Excel and the principle applies: Word, Firefox, PowerPoint, Chrome, Edge, etc., etc., etc.
It is important, critically important, to be able to separate out "who controls what," and by that I mean knowing what commands are Windows commands and work pretty much everywhere under Windows, what are screen reader commands, and what are commands specific to the application being accessed. These things interact with each other, but are definitely separate from each other in terms of "whos doing what." And knowing who does what is the very first step in solving an issue (or knowing that you don't know, and asking to get clarity).
Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042
Always remember others may hate you but those who hate you don't win unless you hate them. And then you destroy yourself.
~ Richard M. Nixon