I just checked.  F1 brings up the user manual.  Shift f1 opens the manual to the part that describes the command you are on when you issue the command. 

I don't know how often shift f1 is used for context `sensitive help these days.  It used to be a long time ago but I haven't seen it discussed for a long time. 

Gene

On 5/14/2022 1:01 AM, Luke Davis wrote:

Gene wrote:

I don't know the significance of the lines per page setting. 

Again, easily determined by pressing F1 while in that field. It configures how many lines a page up/down keypress moves while in browse mode.

I have mine set to 48, since that is the line count on my Linux text consoles, and I am used to its progress characteristics. That said, I rarely use pgup/pgdn on web pages.

Gene wrote:

I don't know the significance of the lines per page setting. 

Again, easily determined by pressing F1 while in that field. It configures how many lines a page up/down keypress moves while in browse mode.

I have mine set to 48, since that is the line count on my Linux text consoles, and I am used to its progress characteristics. That said, I rarely use pgup/pgdn on web pages.

Hi Gene,

 Tab to a check box that says Enable browse mode on page load.
If it isn't checked, check it with the space bar.
Then press enter.  

This works. 

Never the les, this behavior was different with 2021.x  🤷

Thx 

Yeti 

One of the browse settings asks for the maximum number of characters on one
line. 

Another question is how many lines on one page.

What should be the number entered for each?

The driver for the old Vocalizer is already updated on the web page...


The direct link is:

https://www.tiflotecnia.net/Instal/vocalizer-driver_2.1.3.nvda-addon


Best regards,

Rui Fontes
Tiflotecnia, Lda.



Às 23:41 de 12/05/2022, David Mehler escreveu:

Hello,

Also with regards Vocalizer will the 2.1 nvda.addon be updated for
2022.1 compatibility?

Thanks.
DAve.


On 5/12/22, Rui Fontes <rui.fontes@...> wrote:

Hello!


I'm a bit of a suspect, since I'm from Tiflotecnia...


But, let's see:

* Which, if any, support automatic language switching? Using the

CodeFactory bundle 1.1 with NVDA 2021.3.5, neither Eloquence nor
Vocalizer seemed to be able to auto-switch despite that option being
enabled in Voice Settings.

Our Vocalizer works very good in that feature...

And, for people using no latin characters, like chinese, japonese,
cyrilic, hebrew or arabic, even on apps not informing the screen reader
to change language, our Vocalizer changes automatically based on the
type of characters...

* Which tends to be updated for compatibility with new NVDA releases
most promptly?

Ours. We have already the new driver to publish it today or tomorrow...

* What are other differences that should be accounted for in one's
decision?

Our technical support is better andfaster...


Rui Fontes

Tiflotecnia, Lda.

Thanks for this. I use Word all the time and had no idea. Sounds like it would be faster than using Word’s spellcheck.

 

Janet

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: May 12, 2022 6:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and reporting of spelling error

 

I don't know if anyone is reading this thread who doesn't know what is being discussed.  I'll briefly explain it.

In Word, NVDA space places you in browse mode.  W moves you to the next misspelled word.  You can hear the word in context by reading the current line. 

When you are finished in browse mode, NVDA space turns browse mode off and you can work directly with the document, such as edit it, just as before.

Gene.

On 5/12/2022 7:10 PM, William wrote:

> Did you know you can navigate between misspelled words by pressing NVDA plus Space, then W? When you find a misspelled word, press your applications key or Shift plus F10 to open the context menu, in order to correct the word. If you want to correct the word manually, you'll need to press NVDA plus Space again. I hope this is helpful.

 

Correct, but in reality, I cannot do any correction without first reading the whole sentence, cause sometimes the spelling errors suggested by word is not correct.

 

 

 

Abbie Taylor 於 13/5/2022 06:47 寫道:

I'm noticing the same thing. So, I'm assuming it's normal.

Did you know you can navigate between misspelled words by pressing NVDA plus Space, then W? When you find a misspelled word, press your applications key or Shift plus F10 to open the context menu, in order to correct the word. If you want to correct the word manually, you'll need to press NVDA plus Space again. I hope this is helpful.

 

Thanks for this. I use Word all the time and had no idea. Sounds like it would be faster than using Word’s spellcheck.

Janet

I don't know if anyone is reading this thread who doesn't know what is being discussed.  I'll briefly explain it.

In Word, NVDA space places you in browse mode.  W moves you to the next misspelled word.  You can hear the word in context by reading the current line. 

When you are finished in browse mode, NVDA space turns browse mode off and you can work directly with the document, such as edit it, just as before.

Gene.

> Did you know you can navigate between misspelled words by pressing NVDA plus Space, then W? When you find a misspelled word, press your applications key or Shift plus F10 to open the context menu, in order to correct the word. If you want to correct the word manually, you'll need to press NVDA plus Space again. I hope this is helpful.

 

Correct, but in reality, I cannot do any correction without first reading the whole sentence, cause sometimes the spelling errors suggested by word is not correct.

 

 

 

Abbie Taylor 於 13/5/2022 06:47 寫道:

I'm noticing the same thing. So, I'm assuming it's normal.

Did you know you can navigate between misspelled words by pressing NVDA plus Space, then W? When you find a misspelled word, press your applications key or Shift plus F10 to open the context menu, in order to correct the word. If you want to correct the word manually, you'll need to press NVDA plus Space again. I hope this is helpful.

I don't know if anyone is reading this thread who doesn't know what is being discussed.  I'll briefly explain it.

In Word, NVDA space places you in browse mode.  W moves you to the next misspelled word.  You can hear the word in context by reading the current line. 

When you are finished in browse mode, NVDA space turns browse mode off and you can work directly with the document, such as edit it, just as before.

Gene.

> Did you know you can navigate between misspelled words by pressing NVDA plus Space, then W? When you find a misspelled word, press your applications key or Shift plus F10 to open the context menu, in order to correct the word. If you want to correct the word manually, you'll need to press NVDA plus Space again. I hope this is helpful.

 

Correct, but in reality, I cannot do any correction without first reading the whole sentence, cause sometimes the spelling errors suggested by word is not correct.

 

 

 

Abbie Taylor 於 13/5/2022 06:47 寫道:

I'm noticing the same thing. So, I'm assuming it's normal.

Did you know you can navigate between misspelled words by pressing NVDA plus Space, then W? When you find a misspelled word, press your applications key or Shift plus F10 to open the context menu, in order to correct the word. If you want to correct the word manually, you'll need to press NVDA plus Space again. I hope this is helpful.

Hi,

I also disagree with Jean on this one, Quickbooks makes some use of Mouse Overs, and JAWS works well with it.

All the best

Steve

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Luke Davis
Sent: 08 May 2022 07:27
To: nvda@nvda.groups.io
Subject: Re: [nvda] mouse hover

Gene wrote:

My guess is that if mouse over links did anything other than be 
marginally useful, that is, show necessary information more than very 
rarely, NVDA would have incorporated a mouse over function.  JAWS has one, Window-eyes didn't.  I think if it were considered at all important, more than just one screen[-reader would have it.

Gene, I must disagree with you.

I have been in several situations where a website's functions were completely unusable without mouseover capability, or some way to simulate it. I present, again, GetResponse as one example.

Now, that bad design is not NVDA's fault, but I think that the real reason here is that it is simply very difficult to do given the way NVDA presents information.

Apparently, in Jaws, it is not unusual to hear that new options have appeared on line such-and-such of the virtual buffer. But users jumping to specific lines, is not an NVDA paradigm.

So the question becomes: if new options do appear, how should NVDA get you to them, or tell you about them?

I suspect if there was a reasonable answer to that, more progress might be made on mouseover support.

Luke

My guess is that if mouse over links did anything other than be
marginally useful, that is, show necessary information more than very
rarely, NVDA would have incorporated a mouse over function. JAWS has one, Window-eyes didn't. I think if it were considered at all important, more than just one screen[-reader would have it.