NVDA and Firefox 58 – The team is regaining strength

A week before the Firefox 57 “Quantum” release in November, I published an Article detailing some bits to be aware of when using Firefox and the NVDA screen reader together. In Firefox 58, due on January 23, 2018, the reliable team is regaining strength in playing well together and offering you good and fast web accessibility.

After the Firefox 57 release, due to many changes under the hood, NVDA and Firefox temporarily lapsed in performance. Statistics quickly showed that about two thirds of the NVDA user base stayed with us despite of this. So to all of you who stuck with us on this difficult release: Thank you! Many of the others moved to the extended support release of Firefox 52. Thank you to those of you as well, you decided to stick with Firefox! Also, statistics show that barely any of those of you who stuck with 57 decided to turn off multi-process Firefox, but instead used the new technology, and some of you even reported problems to us.

Since then, the accessibility team at Mozilla have worked hard to improve the situation. And I am glad to report that in Firefox 58, most of the bottlenecks and slowdowns could be fixed. We’re now delivering most pages fast enough again so that NVDA doesn’t feel the need to notify you that it is loading a document. In addition, you will start feeling the actual effects of the Quantum technologies, like faster page load times and other more smooth experiences now that the accessibility bottlenecks are out of the way. Feedback from users who have been using the Firefox 58 beta releases has been good, so we feel confident that those of you who upgrade from 57 to 58 upon release, will immediately feel more comfortable with your screen reader and browser combination again. And I am hoping that this encourages many of those who switched to the 52 ESR, to come back to Firefox 58 and give it a try. If you still don’t like it, you can go back to 52 ESR as before, but I sincerely hope you’ll stick with 58 once you notice the improvements.

Moreover, Firefox 58 introduces a new feature that NVDA will take advantage of starting in the 2018.1 release, due in February. Those of you NVDA users on the Next or Master development snapshots, already have that particular improvement. That improvement will speed up the cooperation between NVDA and Firefox even more, causing web content to render in the virtual buffer faster.

What’s coming beyond 58?

Of course, more bug fixes! 🙂 We’re continuing to make improvements which bring us closer to parity with Firefox 56, or even beyond that. On many small and medium size pages, that is already the case now, so Firefox 59 deals with stuff that mostly hits on big pages with lots of hyperlinks or many chunks of differently formatted text.

We’ll also continue to work hard to iron out any problems that may cause JAWS and Firefox to slow down so badly together. While some of the above mentioned improvements also improve the interaction between Firefox and JAWS somewhat, JAWS’s interactions with Firefox are different enough that there is still something causing bad slowness that we don’t see with NVDA at all. And while we’ll do everything to improve the situation on our end, there will also need to come some updates to JAWS from Freedom Scientific, the makers of JAWS. So for JAWS users, the recommendation still stands to remain on 52 ESR, which will receive regular security updates until way into the third quarter of 2018, or keep multi-process tabs turned off, as many JAWS users who remained with current Firefox releases have done. Note, however, that turning off multi-process tabs is something you do at your own risk. This is officially an unsupported configuration, so if anything breaks there, it’s tough luck.

I will have more updates in a separate article once we have them and there is significant progress to report.

In conclusion

As we continue to find bottlenecks, debug hangs, and look into sites reported by users, the situation will return to normal, if it hasn’t for you already. All of the above mentioned improvements we have made in Firefox 58 should impact more assistive technologies than just NVDA, except where noted.

I would like to repeat my thanks to all of you who decided to stick with the release, or even try out the beta and give us feedback on the sites you use day to day. This helped a lot over the past few weeks to make more improvements, and moreover, get agreement from release management to push these out to 58 even when they were initially already in the 59 timeframe. Through that, we’ve been able to give you even more improvements in Firefox 58 than I initially anticipated.


17 thoughts on “NVDA and Firefox 58 – The team is regaining strength

  1. Thanks for all your hard work on this marco and the rest of the teem. I am now running firefox 59 and a snapshot build of NVDA and it is so much better even large pages load in a snap.

    1. Well, our active user base is pretty much divided between NVDA and JAWS, so both are equally important to us. As I state in my above post in the last paragraph before the conclusion, we‘re continuing to investigate and improve on our end what we can to make JAWS and Firefox work better together again. But it also requires updates from the Freedom Scientific side to truly improve. And if and when they‘ll come out with those updates, I do not know.

      1. Hi Marco. The JAWS 2018 February Update, coming in early February, has the necessary changes on the JAWS side made. over the past 4 to 6 weeks by our engineering team. We understand that Mozilla is still working to resolve things related to cross process calls in FireFox that are still slowing things down with respect to using JAWS but that this work is in process and that Mozilla hopes to get those changes made in the coming weeks.

  2. Hello Marco!

    Can you elaborate a little more technically on what is this feature deploied on NVDA 2018.1?

    I ask that because this is suposed to come latter than the ff 58 release and I would like to know what emproves more that relation-ship ** changes on NVDA or on firefox. Deppending on what is more relevant I can recomend waiting for 2018.1 to upgrade to 58 or upgrading now.
    Also I am curious to understand what was envolved in a high level overview to overcome that dificulties even with the multi tasking taking place.

    Other than that, thanks a lot for the team hard work on that issue and for reporting us back.

    1. You will definitely want to upgrade to Firefox 58 now and not wait for NVDA 2018.1. The change in NVDA 2018.1 concerns one specific use case: In a particular chunk of text, ask for all contained hyperlinks in one call, instead of querying each hyperlink separately. This feature was implemented in Firefox 58 along with a lot of other pre-fetching data from the content process to deliver it to screen readers like NVDA faster, but this particular change requires a change in NVDA as well to take full advantage of it. But it will be much faster even when you‘re not on NVDA 2018.1 or the Master or Next development snapshots yet. So, yes, upgrade to Firefox 58 next week by all means.

      1. Nothing against with the new features which is fairly fast, indeed. However there is distinct and noticible in terms of the sounds is not heard specially in progress bar to download certain file. I am taking time to installed and tested this to the latest master snapshot of nvda. Not sure of causing of this but looking forward to fix this soon in the stable build version of Firefox. Thanks alot.

  3. Hello,

    thanks Marco and other for your great work so far. I have another question regarding Firefox accessibility in next versions. Until Firefox 57 we have used addon called Navigational sounds. this addons allowed us to configure also “sound” feedback to us. For example, Firefox played a sound, when We have landed to site, where was detected a RSS feed, Firefox played sound, when the download was completed etc. Do you know, if this feature is going to be implemented into next versions of Firefox, because as I know, addons, which are based on web extention technology cannot see system sounds and other windows components so, this addon is out of date.
    I have suggestion for this task. Is it possible, that Firefox implements its sound scheem as it is done in Microsoft Office 2016 (last feature update), where you can enable sound feedback and choose modern or classic sound scheem.

    Thanks for your good work.

    Regards, Jožef

  4. Hi Marco et al! Thank you as always for pushing the state of accessibility forward!

    One question: any plans to get back to making devtools accessible, especially the debugger? The inspector seems to have remained accessible through the quantum upgrade, but the console is a bit odd to use now, especially the output pane. Seems a few buttons have migrated into the tab order for the output pane, which definately makes it more difficult to find the start of log / error messages that might be posted there.

    AGain, thanx for all you do!!

    — Rich

  5. Hello Marco,
    Is there any chance, that we will have once more fast and responsive firefox as before multiprocess? I today updated to 68 and it is really hard to read bigger pages. Try for example this:
    I have to read Android documentation every day because of my job. I know, we have new and great technology, which is probably good for majority, but blind community (definitely?) lost really good browser. 🙁
    Sorry for the tone of this message… I am frustrated.

  6. I was one of many AT users that were disabling multiprocess to make loading of bigger pages much less painful. Now that this option is gone, I’m seriously thinking of switching browsers, as this change takes me back to 2001 and it’s unacceptable for the day-to-day experience.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.