You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Reported by ddeangelis on 2012-03-13 16:34
In Mozilla Firefox and Internet explorer.
When using the mouse to hover over a given line NVDA stops reading the line if it contains a link withing the text. The NVDA home page contains several examples of text links within a given line of text on a web page. If I move the mouse cursor over the link it will be read, but the text following the link will not be read even if I move the mouse cursor over it. If I hover over the block of text following linked text NVDA reads the text proceeding the linked text.
It would be extremely helpful to have a setting to read the entire line calling out links with a selectable beep, verbal or no description and continuing to read the entire line.
I consider this to be a bug in the software as it disallows partially sighted individuals from reading websites using the mouse to hover over the text that is desired to be verbalized. This is a standard option in many screen readers. It is much more efficient for partially sighted individuals to navigate in this manner as opposed to using browse mode and keyboard navigation.
This issue exists in all versions after 2011.3. This issue was ovserved in both Windows XP and Vista.
The text was updated successfully, but these errors were encountered:
Comment 1 by 4RJames on 2013-11-13 14:54
In addition to links this happens any time there is something like a link such as dates. There are many times when I cannot read all the text due to this problem. It is also not always obvious when text is skipped. It was good to see this was already reported. It has been many months and would be greatly appreciated if it was fixed.
I very much doubt there's been any change here. This should work as expected now in editable text boxes in Firefox (not sure about Chrome), as we use the rich text editing code to support this. Other than that, this doesn't work because browse mode doesn't contain enough information to support this kind of tracking, and supporting it without using browse mode would cause severe performance problems.
The issue here is I think related to #3590 - I did a bit of testing on that one and wrote up a fairly long post describing all the symptoms some time ago, but it is good to have it linked here as well.