Quick navigation command for next/previous spelling error in Word

[LeonarddeR]

For MS Word, one of the Dutch NVDA users requested the possibility to jump to the next/previous spelling error using quick navigation. I agree that this might be an interesting feature. The p key would be an option for this.

[josephsl]

Hi, agreed. One thing though: why the letter “P”? Thanks. From: Leonard de Ruijter [mailto:notifications@github.com] Sent: Tuesday, March 7, 2017 5:54 AM To: nvaccess/nvda <nvda@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [nvaccess/nvda] Quick navigation command for next/previous spelling error in Word (#6942) For MS Word, one of the Dutch NVDA users requested the possibility to jump to the next/previous spelling error using quick navigation. I agree that this might be an interesting feature. The p key would be an option for this. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6942> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkFYiw3VGtbcBBaTq7DO2qtppm7-Cks5rjWFggaJpZM4MVgb0> .

[LeonarddeR]

Because the p is in the word spelling. Other free letters ale as I recall correctly j, w, y and z. One of those will fit too of course. furthermore, we might want to use p for paragraphs, pages or the like? N.B. Sent on behalf of @BabbageCom

…

Op 7 mrt. 2017 om 16:52 heeft Joseph Lee ***@***.***> het volgende geschreven: Hi, agreed. One thing though: why the letter “P”? Thanks. From: Leonard de Ruijter ***@***.*** Sent: Tuesday, March 7, 2017 5:54 AM To: nvaccess/nvda ***@***.***> Cc: Subscribed ***@***.***> Subject: [nvaccess/nvda] Quick navigation command for next/previous spelling error in Word (#6942) For MS Word, one of the Dutch NVDA users requested the possibility to jump to the next/previous spelling error using quick navigation. I agree that this might be an interesting feature. The p key would be an option for this. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6942> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkFYiw3VGtbcBBaTq7DO2qtppm7-Cks5rjWFggaJpZM4MVgb0> . — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[LeonarddeR]

One other option is to just use s. In other words, allow different browse mode implementations to use different key mappings. We also have comma, period, slash, backslash, etc. N.B. Sent on behalf of @BabbageCom

…

Op 7 mrt. 2017 om 16:52 heeft Joseph Lee ***@***.***> het volgende geschreven: Hi, agreed. One thing though: why the letter “P”? Thanks. From: Leonard de Ruijter ***@***.*** Sent: Tuesday, March 7, 2017 5:54 AM To: nvaccess/nvda ***@***.***> Cc: Subscribed ***@***.***> Subject: [nvaccess/nvda] Quick navigation command for next/previous spelling error in Word (#6942) For MS Word, one of the Dutch NVDA users requested the possibility to jump to the next/previous spelling error using quick navigation. I agree that this might be an interesting feature. The p key would be an option for this. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6942> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkFYiw3VGtbcBBaTq7DO2qtppm7-Cks5rjWFggaJpZM4MVgb0> . — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[derekriemer]

Or control+; to fit with docs.

…

On Tue, Mar 7, 2017 at 1:34 PM, Leonard de Ruijter ***@***.*** > wrote: One other option is to just use s. In other words, allow different browse mode implementations to use different key mappings. We also have comma, period, slash, backslash, etc. N.B. Sent on behalf of @BabbageCom > Op 7 mrt. 2017 om 16:52 heeft Joseph Lee ***@***.***> het volgende geschreven: > > Hi, agreed. One thing though: why the letter “P”? Thanks. > > > > From: Leonard de Ruijter ***@***.*** > Sent: Tuesday, March 7, 2017 5:54 AM > To: nvaccess/nvda ***@***.***> > Cc: Subscribed ***@***.***> > Subject: [nvaccess/nvda] Quick navigation command for next/previous spelling error in Word (#6942) > > > > For MS Word, one of the Dutch NVDA users requested the possibility to jump to the next/previous spelling error using quick navigation. I agree that this might be an interesting feature. The p key would be an option for this. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub < #6942> , or mute the thread < https://github.com/notifications/unsubscribe-auth/ AHgLkFYiw3VGtbcBBaTq7DO2qtppm7-Cks5rjWFggaJpZM4MVgb0> . > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread. > — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6942 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFGivbC_8mPGjLCvl1WKyO4CgCyTekXNks5rjb9DgaJpZM4MVgb0> .

-- Derek Riemer: Improving the world one byte at a time! - University of Colorado Boulder Department of computer science, 4th year undergraduate student. - Accessibility enthusiast. - Proud user of the NVDA screen reader. - Open source enthusiast. - Skier. Personal website <http://derekriemer.com>

[ruifontes]

Please, avoid that! Semi colon in portuguese layout is Shift+comma... So we will need to use three keys... Rui

…

-----Mensagem Original----- De: Derek Riemer Data: 7 de março de 2017 21:18 Para: nvaccess/nvda Cc: Subscribed Assunto: Re: [nvaccess/nvda] Quick navigation command for next/previous spelling error in Word (#6942) Or control+; to fit with docs.

On Tue, Mar 7, 2017 at 1:34 PM, Leonard de Ruijter ***@***.*** > wrote: One other option is to just use s. In other words, allow different browse mode implementations to use different key mappings. We also have comma, period, slash, backslash, etc. N.B. Sent on behalf of @BabbageCom > Op 7 mrt. 2017 om 16:52 heeft Joseph Lee ***@***.***> het volgende geschreven: > > Hi, agreed. One thing though: why the letter “P”? Thanks. > > > > From: Leonard de Ruijter ***@***.*** > Sent: Tuesday, March 7, 2017 5:54 AM > To: nvaccess/nvda ***@***.***> > Cc: Subscribed ***@***.***> > Subject: [nvaccess/nvda] Quick navigation command for next/previous spelling error in Word (#6942) > > > > For MS Word, one of the Dutch NVDA users requested the possibility to jump to the next/previous spelling error using quick navigation. I agree that this might be an interesting feature. The p key would be an option for this. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub < #6942> , or mute the thread < https://github.com/notifications/unsubscribe-auth/ AHgLkFYiw3VGtbcBBaTq7DO2qtppm7-Cks5rjWFggaJpZM4MVgb0> . > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread. > — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6942 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFGivbC_8mPGjLCvl1WKyO4CgCyTekXNks5rjb9DgaJpZM4MVgb0> .

-- Derek Riemer: Improving the world one byte at a time! - University of Colorado Boulder Department of computer science, 4th year undergraduate student. - Accessibility enthusiast. - Proud user of the NVDA screen reader. - Open source enthusiast. - Skier. Personal website <http://derekriemer.com> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[LeonarddeR]

We can even choose to leave the scripts unbound by default. Whatever key we choose, when we reach consensus about it, I can send in a pr, as the code is ready for review.

[LeonarddeR]

So, two options have been mentioned:

• P: second letter of word spelling
• control+; , although @ruifontes argued against it

Also, we do have some punctuation keys left unbound, including semicolon, left and right bracket, dash, equals, `period, slash and accent grave

[jcsteh]

Another possibility is including spelling errors as part of annotations. It's not an exact fit, since other annotations are written by the author and spelling errors are automated, but it does make some sense, especially since proofreading/correcting errors would also involve addressing review comments. If we do want a separate command, I think it should be for "errors", not specifically "spelling errors". That allows for grammar errors as well without consuming extra keystrokes.

[LeonarddeR]

Another possibility is including spelling errors as part of annotations. It's not an exact fit, since other annotations are written by the author and spelling errors are automated, but it does make some sense, especially since proofreading/correcting errors would also involve addressing review comments.

When we treat spelling and grammatical errors as annotations, it means that false positives will also get into annotations checking. I think that false positives are quite common, so this will slow down the process of annotation checking.

If we do want a separate command, I think it should be for "errors", not specifically "spelling errors". That allows for grammar errors as well without consuming extra keystrokes.

That's what I actually did in the code I have ready for a pr as soon as we agree about the key stroke to use. Unfortunately, all the letters from the word error are bound to other quick navigation commands.

[ruifontes]

Well, why not W for wrong? LOL! Rui

-----Mensagem Original----- De: Leonard de Ruijter Data: 29 de maio de 2017 12:29 Para: nvaccess/nvda Cc: ruifontes ; Mention Assunto: Re: [nvaccess/nvda] Quick navigation command for next/previous spelling error in Word (#6942)

Another possibility is including spelling errors as part of annotations. It's not an exact fit, since other annotations are written by the author and spelling errors are automated, but it does make some sense, especially since proofreading/correcting errors would also involve addressing review comments.

When we treat spelling and grammatical errors as annotations, it means that false positives will also get into annotations checking. I think that false positives are quite common, so this will slow down the process of annotation checking.

If we do want a separate command, I think it should be for "errors", not specifically "spelling errors". That allows for grammar errors as well without consuming extra keystrokes.

That's what I actually did in the code I have ready for a pr as soon as we agree about the key stroke to use. Unfortunately, all the letters from the word error are bound to other quick navigation commands. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[LeonarddeR]

Well, why not W for wrong?

Actually, the more I think about this one, the more I like it. W for warning could also be applied to alerts on web pages.

[jcsteh]

It's about as close as we're going to get to something memorable, so I can live with that. :)

[bhavyashah]

I agree with 'w' for wrong to jump spelling and grammar errors. Sounds memorable once you corelate it to wrong and 'w' will unlikely be required by another element.

…

On 6/5/17, James Teh ***@***.***> wrote: It's about as close as we're going to get to something memorable, so I can live with that. :) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #6942 (comment)

-- Best Regards Bhavya Shah Blogger at Hiking Across Horizons: https://bhavyashah125.wordpress.com/ Contacting Me E-mail Address: bhavya.shah125@gmail.com Follow me on Twitter @BhavyaShah125 or www.twitter.com/BhavyaShah125 Mobile Number: +91 7506221750

[LeonarddeR]

So, we go for w here. But what message will someone get when there's no error left?

1. No next spelling error. This fits the case, as a grammatical error is also related to how you spell things
2. No next proofing error. @dkager brought this one up, and I like it
3. No next warning. At least spelling errors get a red line underneath to warn the user. Furthermore, this one can be generalised to alerts and other types of warnings as well, as I proposed above.

[jcsteh]

What about "No next error"? Alerts are often errors anyway and I think people can forgive it in the case when they're a warning instead. Also, we could then extend this to cover form fields with aria-invalid, which might be useful when trying to find out which field you messed up when filling out a compliant form.