NVDA should indicate misspelled words on The Braille display by The blinking first character of The mispelled word

[nvaccessAuto]

Reported by janusz on 2013-08-25 11:54
Dear NVDA developers.
I have one new NVDA feature suggestion.
Do You think, that would be possible to make special modiffication, which would enable Braille display users to have misspelled words assigned on The braille display by A blinkink first character of The misspelled word?
Or even whole word would blink, all characters in The misspelled word?
I would like to know, if Braille displays are supporting blinking more than one cell at The same time.
And if it is possible, if Braille Python bindings, Brltty for Windows would manage this?
If it is not possible to blink more than one cell at The same time because of The hardware design of todays Braille displays, i think, that would be possible to assign every first character of The misspelled word by adding 7 Braille or 8 braille dot to The first character of The misspelled word.
For beginning, it would work for Microsoft Office.
What do You think about my idea?

Blocked by #3022

[nvaccessAuto]

Comment 1 by jteh on 2013-08-26 01:11
It's certainly possible, though it's definitely not easy. However, the question is whether blinking characters is an intuitive way to communicate spelling errors; i.e. will the average user be able to figure this out? Also, would this be tied to the cursor blink rate setting? I'd rather not introduce another blink rate setting due to potential confusion, but that said, linking it to cursor blink rate is also potentially confusing.

[nvaccessAuto]

Comment 2 by ragb on 2013-08-26 09:11
Hi,

I was more inclined to use dots 7 and 8 to "underline" miss-spelled words. This may cause confusion with some computer braille tables (you loose the information that a letter may be capitalized or something) however it seems a good metaphor regarding what sighted folks are seeing. Just dot 8 is also an option.

I don't really like blinking, due to the fact that it may be confused with the cursor, and if the word is miss-spelled one would need the cursor to edit it :).

Regards,

Rui Batista

[nvaccessAuto]

Comment 3 by jteh on 2013-08-26 23:01
Dots 7 and 8 are used to indicate selection, so it shouldn't be this.

[nvaccessAuto]

Comment 4 by ragb (in reply to comment 3) on 2013-08-27 11:21
Replying to jteh:

Dots 7 and 8 are used to indicate selection, so it shouldn't be this.

So just dot 8? This may be also confused with numbers in some computer braille tables.

An alternative approach would be to provide underline type forms to liblouis at the position of the miss-spelled word. However, I don't know how well braille tables are handling this (if they are at all. I couldn't get it to report underline in Word 2007, although with speech reporting works.
On the other hand, I'm not sure if this is viable to implement or not (probably in !braille.TextInfoRegion) since I'm not that familiar with internals of braille formatting and how objects (mainly text objects) are reporting it.

I suggest underline as it is what appears on screen for miss-spelled words, as far as I recall. This as the drawback to be confused with normal underlining. I can't think of something that won't be confused with something else though :).

[nvaccessAuto]

Comment 5 by jteh on 2013-09-03 23:40
I just discovered this is a duplicate of #3022. :)
Changes:
Added labels: duplicate
State: closed