Re: CLARITY OF TERMINOLOGY AND DOCUMENTATION
toggle quoted messageShow quoted text
I’m interested in seeing which parts of the NVDA’s user interface appears to be difficult for everyday users. That way, we can figure out what can be done to improve it rather than pass on our own experiences alone.
From: firstname.lastname@example.org <email@example.com> On Behalf Of Steve Nutt
Sent: Sunday, February 17, 2019 11:12 AM
Subject: Re: [nvda] CLARITY OF TERMINOLOGY AND DOCUMENTATION
I agree with you completely about programmers not really able to document.
Even the menu structure of NVDA that we’re talking about, was given little consideration in terms of non-geek terminology. Writing menus, is the same in a way, as writing documentation, the menus need to be intuitive at the outset, or people won’t find or use your feature set.
All the best
On Sun, Feb 17, 2019 at 12:52 PM, Joseph Lee wrote:
And, to me, having been a programmer and having written documentation (that most people seem to like), I'd say that if you have no real ability to write to begin with you should not be writing documentation. Or if you (any you, not you, Joseph) are writing it you had better be ready to subject it to editorial review by someone known to be skilled in the area.
Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763
A great deal of intelligence can be invested in ignorance when the need for illusion is deep.
~ Saul Bellow, To Jerusalem and Back