I was thinking today about a new feature that might speed up work a good deal when writing documents.  I generally don't use f7 spell check these days.  I read my messages before sending them and change flagged spelling errors, thus doing two things at once that I would do separately otherwise. 

My proposal for a new feature, which I'd like comments about in terms of demand and feasibility is this:

There could be an NVDA command that moves to the next flagged misspelled word in a document.  Even if I read a document and hear a word flagged, the cursor is almost never on the word.  Its often at the beginning of the line and the misspelled word may take a lot of movement by word to get to.  If I could hear the flag, then issue the move to command, moving to the word could be sped up a lot most of the time.   As I think about it, this adds the equivalent to what a sighted person can do now.  A word is flagged, the sighted person can immediately move to or click on it, thus placing focus on it, and either manually correct it or use the context menu to do so.  Or a sighted person can do so later by seeing the flag, clicking on it, and correcting the word.

I'm surprised this hasn't been discussed before.  I did a Google search and I didn't find a Github issue, though I didn't search Github directly.

Gene

Hello!

Where you compose your e-mails?

In Word and Outlook, in browse mode, w will move to next error...

Rui Fontes

Rui Fontes

Às 01:00 de 31/01/2022, Gene escreveu:

I was thinking today about a new feature that might speed up work a good deal when writing documents.  I generally don't use f7 spell check these days.  I read my messages before sending them and change flagged spelling errors, thus doing two things at once that I would do separately otherwise. 

My proposal for a new feature, which I'd like comments about in terms of demand and feasibility is this:

There could be an NVDA command that moves to the next flagged misspelled word in a document.  Even if I read a document and hear a word flagged, the cursor is almost never on the word.  Its often at the beginning of the line and the misspelled word may take a lot of movement by word to get to.  If I could hear the flag, then issue the move to command, moving to the word could be sped up a lot most of the time.   As I think about it, this adds the equivalent to what a sighted person can do now.  A word is flagged, the sighted person can immediately move to or click on it, thus placing focus on it, and either manually correct it or use the context menu to do so.  Or a sighted person can do so later by seeing the flag, clicking on it, and correcting the word.

I'm surprised this hasn't been discussed before.  I did a Google search and I didn't find a Github issue, though I didn't search Github directly.

Gene

I was thinking today about a new feature that might speed up work a good deal when writing documents.  I generally don't use f7 spell check these days.  I read my messages before sending them and change flagged spelling errors, thus doing two things at once that I would do separately otherwise. 

My proposal for a new feature, which I'd like comments about in terms of demand and feasibility is this:

There could be an NVDA command that moves to the next flagged misspelled word in a document.  Even if I read a document and hear a word flagged, the cursor is almost never on the word.  Its often at the beginning of the line and the misspelled word may take a lot of movement by word to get to.  If I could hear the flag, then issue the move to command, moving to the word could be sped up a lot most of the time.   As I think about it, this adds the equivalent to what a sighted person can do now.  A word is flagged, the sighted person can immediately move to or click on it, thus placing focus on it, and either manually correct it or use the context menu to do so.  Or a sighted person can do so later by seeing the flag, clicking on it, and correcting the word.

I'm surprised this hasn't been discussed before.  I did a Google search and I didn't find a Github issue, though I didn't search Github directly.

Gene

I was thinking today about a new feature that might speed up work a good deal when writing documents.  I generally don't use f7 spell check these days.  I read my messages before sending them and change flagged spelling errors, thus doing two things at once that I would do separately otherwise. 

My proposal for a new feature, which I'd like comments about in terms of demand and feasibility is this:

There could be an NVDA command that moves to the next flagged misspelled word in a document.  Even if I read a document and hear a word flagged, the cursor is almost never on the word.  Its often at the beginning of the line and the misspelled word may take a lot of movement by word to get to.  If I could hear the flag, then issue the move to command, moving to the word could be sped up a lot most of the time.   As I think about it, this adds the equivalent to what a sighted person can do now.  A word is flagged, the sighted person can immediately move to or click on it, thus placing focus on it, and either manually correct it or use the context menu to do so.  Or a sighted person can do so later by seeing the flag, clicking on it, and correcting the word.

I'm surprised this hasn't been discussed before.  I did a Google search and I didn't find a Github issue, though I didn't search Github directly.

Gene

>From what Rui has said, the function is already supported.

Why it does not work specifically in the Thunderbird message composition Window which, based on Gene's comments has no browse mode, is likely where the resolution lies.  And that likely depends on exactly why the current situation is as it is.  There are certain things that NVDA can't fix unless fixes are applied to the software it's using to access.  I have no idea whether that's the case here or not, just a general observation.

Sarah is also right that unless there is an issue in GitHub that addresses this then, from a development standpoint, the issue does not exist. Having taken a look with the filters
is:issue is:open Thunderbird compose 
doesn't turn up anything that looks at all related.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 

On Mon, Jan 31, 2022 at 01:30 PM, Gene wrote:

The flagging is done by the program being used and NVDA is aware of those flags. 

-
Then, Gene, make the request, formally.  It ain't gonna happen otherwise, and it may take a while even once on record.

What appears superficially to be "the same thing" (and, from a human perspective, actually is the same thing) is often anything but at the coding level.

Who knows, you could get your desired result in one of the upcoming 2022 releases?
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The instinctive need to be the member of a closely-knit group fighting for common ideals may grow so strong that it becomes inessential what these ideals are.

       ~ Konrad Lorenz (1903-1989)

 

Great idea. Window-Eyes used to have this feature and it was really quick and useful.

Janet

I was thinking today about a new feature that might speed up work a good deal when writing documents.  I generally don't use f7 spell check these days.  I read my messages before sending them and change flagged spelling errors, thus doing two things at once that I would do separately otherwise. 

My proposal for a new feature, which I'd like comments about in terms of demand and feasibility is this:

There could be an NVDA command that moves to the next flagged misspelled word in a document.  Even if I read a document and hear a word flagged, the cursor is almost never on the word.  Its often at the beginning of the line and the misspelled word may take a lot of movement by word to get to.  If I could hear the flag, then issue the move to command, moving to the word could be sped up a lot most of the time.   As I think about it, this adds the equivalent to what a sighted person can do now.  A word is flagged, the sighted person can immediately move to or click on it, thus placing focus on it, and either manually correct it or use the context menu to do so.  Or a sighted person can do so later by seeing the flag, clicking on it, and correcting the word.

I'm surprised this hasn't been discussed before.  I did a Google search and I didn't find a Github issue, though I didn't search Github directly.

Gene

I was thinking today about a new feature that might speed up work a good deal when writing documents.  I generally don't use f7 spell check these days.  I read my messages before sending them and change flagged spelling errors, thus doing two things at once that I would do separately otherwise. 

My proposal for a new feature, which I'd like comments about in terms of demand and feasibility is this:

There could be an NVDA command that moves to the next flagged misspelled word in a document.  Even if I read a document and hear a word flagged, the cursor is almost never on the word.  Its often at the beginning of the line and the misspelled word may take a lot of movement by word to get to.  If I could hear the flag, then issue the move to command, moving to the word could be sped up a lot most of the time.   As I think about it, this adds the equivalent to what a sighted person can do now.  A word is flagged, the sighted person can immediately move to or click on it, thus placing focus on it, and either manually correct it or use the context menu to do so.  Or a sighted person can do so later by seeing the flag, clicking on it, and correcting the word.

I'm surprised this hasn't been discussed before.  I did a Google search and I didn't find a Github issue, though I didn't search Github directly.

Gene

Hi Gene,

This is another feature that JAWS already has, prior and next misspelling.

It’s a great feature.

All the best

Steve

I was thinking today about a new feature that might speed up work a good deal when writing documents.  I generally don't use f7 spell check these days.  I read my messages before sending them and change flagged spelling errors, thus doing two things at once that I would do separately otherwise. 

My proposal for a new feature, which I'd like comments about in terms of demand and feasibility is this:

There could be an NVDA command that moves to the next flagged misspelled word in a document.  Even if I read a document and hear a word flagged, the cursor is almost never on the word.  Its often at the beginning of the line and the misspelled word may take a lot of movement by word to get to.  If I could hear the flag, then issue the move to command, moving to the word could be sped up a lot most of the time.   As I think about it, this adds the equivalent to what a sighted person can do now.  A word is flagged, the sighted person can immediately move to or click on it, thus placing focus on it, and either manually correct it or use the context menu to do so.  Or a sighted person can do so later by seeing the flag, clicking on it, and correcting the word.

I'm surprised this hasn't been discussed before.  I did a Google search and I didn't find a Github issue, though I didn't search Github directly.

Gene

Put it on the github if it is not already there, otherwise that feature suggestion won’t exist, and it will get lost here. then those of us who are on ther can react with a thumbs up or down if we feel it is a priority for devs or not.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Wednesday, February 9, 2022 6:44 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Opinions about adding an NVDA feature to jump directly to misspelled words

 

Hi Gene,

 

This is another feature that JAWS already has, prior and next misspelling.

 

It’s a great feature.

 

All the best

Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: 31 January 2022 01:00
To: nvda@nvda.groups.io
Subject: [nvda] Opinions about a new feature

 

I was thinking today about a new feature that might speed up work a good deal when writing documents.  I generally don't use f7 spell check these days.  I read my messages before sending them and change flagged spelling errors, thus doing two things at once that I would do separately otherwise. 

 

My proposal for a new feature, which I'd like comments about in terms of demand and feasibility is this:

There could be an NVDA command that moves to the next flagged misspelled word in a document.  Even if I read a document and hear a word flagged, the cursor is almost never on the word.  Its often at the beginning of the line and the misspelled word may take a lot of movement by word to get to.  If I could hear the flag, then issue the move to command, moving to the word could be sped up a lot most of the time.   As I think about it, this adds the equivalent to what a sighted person can do now.  A word is flagged, the sighted person can immediately move to or click on it, thus placing focus on it, and either manually correct it or use the context menu to do so.  Or a sighted person can do so later by seeing the flag, clicking on it, and correcting the word.

 

I'm surprised this hasn't been discussed before.  I did a Google search and I didn't find a Github issue, though I didn't search Github directly.

 

Gene

I have submitted this request as a Github issue.  Those interested in seeing how I ;present the issue and commenting may do so on this page:

https://github.com/nvaccess/nvda/issues/13323

Gene

Put it on the github if it is not already there, otherwise that feature suggestion won’t exist, and it will get lost here. then those of us who are on ther can react with a thumbs up or down if we feel it is a priority for devs or not.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Steve Nutt
Sent: Wednesday, February 9, 2022 6:44 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Opinions about adding an NVDA feature to jump directly to misspelled words

 

Hi Gene,

 

This is another feature that JAWS already has, prior and next misspelling.

 

It’s a great feature.

 

All the best

Steve

 

--

To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

 

Computer Room Services

77 Exeter Close

Stevenage

Hertfordshire

SG1 4PW

T: +44(0)1438-742286

M: +44(0)7956-334938

F: +44(0)1438-759589

E: steve@...

W: https://www.comproom.co.uk

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: 31 January 2022 01:00
To: nvda@nvda.groups.io
Subject: [nvda] Opinions about a new feature

 

I was thinking today about a new feature that might speed up work a good deal when writing documents.  I generally don't use f7 spell check these days.  I read my messages before sending them and change flagged spelling errors, thus doing two things at once that I would do separately otherwise. 

 

My proposal for a new feature, which I'd like comments about in terms of demand and feasibility is this:

There could be an NVDA command that moves to the next flagged misspelled word in a document.  Even if I read a document and hear a word flagged, the cursor is almost never on the word.  Its often at the beginning of the line and the misspelled word may take a lot of movement by word to get to.  If I could hear the flag, then issue the move to command, moving to the word could be sped up a lot most of the time.   As I think about it, this adds the equivalent to what a sighted person can do now.  A word is flagged, the sighted person can immediately move to or click on it, thus placing focus on it, and either manually correct it or use the context menu to do so.  Or a sighted person can do so later by seeing the flag, clicking on it, and correcting the word.

 

I'm surprised this hasn't been discussed before.  I did a Google search and I didn't find a Github issue, though I didn't search Github directly.

 

Gene

Hi,

Closed as a duplicate of an earlier issue raised by the same person. I beg you, please search for existing issues before filing a new one.

Cheers,

Joseph