Hi Joseph, I’ll go through the menus over the next few days and try to make some useful suggestions. I think the input thing is the most difficult to understand though, and so easy to miss

On Sun, Feb 17, 2019 at 02:12 PM, Steve Nutt wrote: 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

By context a lot of the time. if not, they will know a word is missing because what is being said won't make sense. At that point, you can go back and read the word by letter. Gene ----- Original

Hi, the reason for this test is, I received an email just now telling me that one my emails was marked as spam and I should try to subscribe again after 7 days. As it clearly was a mistake,

-- Cheers, Marcio Follow me on Twitter

Hi, 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

Hi, At some point, in addition to bringing up terminology issues with other developers, I’ll go over the user guide (for the umpteenth time) and bring up parts that could lead to misunderstandings

Hi, At least it is separated in terms of how it is presented (multiple entries for the same command description, each of which have different commands assigned; this is on JAWS 2019). But the fact

Hi I am guessing the touch commands are the etc in the input gestures section. it does not mention touch at all only keyboard and braille but should be updated to say also touch. Gene nz On

But how would they know the word was missing, if the synth didn’t utter anything? All the best Steve

Hi Brian, 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

Hi, Yes, JAWS does separate them. I’m surprised this wasn’t done at the offset. All the best Steve

Yes, it would be skipped. Most people wouldn't come across the word often in documents and they have to remember that they won't hear it. They can read letter by letter at the missing word location

Hi Jean, What happens then if you come across the word graphic in a document? Does it just get missed out? That would make it awkward for proofing. I don’t like using dictionaries as a cludge

But that means you have to go somewhere to look up what NVDA terms a gesture? No, I think it needs rethinking a bit. All the best Steve

That's even worse. <Smile>. What is a scheme? I think we need to separate off the input methods. Keyboard, Touch Gestures, etc. All the best Steve

Hi Brian, Doesn't audio ducking solve the loud stuff playing problem for you? I know NVDA does this. All the best Steve

On Sun, Feb 17, 2019 at 12:52 PM, Joseph Lee wrote: To me, saying that programmers should not write manuals robs them of a valuable educational opportunity to communicate (I am a programmer and do

HI, UIA: UI Automation, an accessibility API (libraries, standards, documentation) used to let assistive technologies communicate with other programs. Cheers, Joseph

Hi, UIA support is already in use with Windows 10 unless it is somehow disabled from NVDA’s side. Cheers, Joseph