Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Le thread ibilondoloziwe. Nceda ubuze umbuzo omtsha ukuba ufuna uncedo.

On Firefox, NVDA will not read the whole words(sentence) which is wrapped. (URGENT)

gagan.deep
gagan.deep
more options

Hi Team,

We are facing the issue in firefox browser when we are using NVDA (Screen reader). The Screen reader is not reading whole paragraph it read only one line till last word of the line (before wrapping the content). but ie,edge,chrome it's working fine. kindly let us know what is the solution of this

Hi Team, We are facing the issue in firefox browser when we are using NVDA (Screen reader). The Screen reader is not reading whole paragraph it read only one line till last word of the line (before wrapping the content). but ie,edge,chrome it's working fine. kindly let us know what is the solution of this
Iqhotyoshelwe imifanekiso ekwisikrini

All Replies (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

Hmm, it's strange. If you load a page and let it go, it reads from top to bottom with no issues. But if you move the mouse pointer over a line, it just reads that line (instead of the entire paragraph).

If you want to file a bug, it would be very useful to know the last version of Firefox where it would read the entire paragraph, and run a regression using this tool to figure out when the bug was introduced:

https://mozilla.github.io/mozregression/