In this article, I will attempt to review and rank three of the most popular current screen readers that are available at this time. The three screen readers were tested on the most recent version of Windows 10 anniversary update. This is important because one of the screen readers is Microsoft’s most recently updated Narrator. Although ranking the screen readers might prove to be quite controversial, I think it can also open up a real discussion on which screen readers are most accessible, and even the question of accessibility can sometimes be up for debate. I do realize that accessibility is determined by personal needs and preferences, so I will attempt to define the criteria I used for accessibility in this review.
What Is Accessibility?
Quite simply, I determined that accessibility is the ability to access that which needs to be accessed. Also, I take points off accessibility for the screen readers that make it difficult to access material by being dysfunctional or by making it very difficult to figure out which keystrokes need to be used with the material. Some screen readers make you use ridiculous key combinations to activate website elements or functions within applications. So without further ado, here are the rankings!
Number One: Microsoft Narrator!
It took me about a day to get used to the screen reader, but once I did, I realized what a powerful tool Microsoft had created and that the company was finally serious about supporting a built-in screen reader for the blind. In fact, the only thing I could find wrong with the screen reader was that it did not work with my braille display. I am currently working with Microsoft and HIMS to see if this problem can be resolved. Besides that one issue, the screen reader was fully accessible on all websites and applications. I tested the screen readers on Microsoft Edge, Internet Explorer, Groove Music, Skype, Dropbox, Microsoft Word, Audacity, Feedback, and the Settings app. Narrator now uses something called scan mode. You can toggle this on and off by pressing caps lock and space bar. When scan mode is off, you can tab through active elements, use Windows keyboard commands, and navigate by means of your preferred preference; such as, items, headings, and paragraphs. When scan mode is on, you can navigate through everything on the screen—that includes text, website elements, and application controls—by using the tab key, arrowing around the screen, or employing letter navigation. How often has your screen reader announced; “OK button”. And you are wondering; “What am I saying OK to?” When scan mode is turned on, you can just arrow up and read the text associated with that button. You do need to toggle scan mode off when you want to use keyboard commands such as control P to pause a music track or alt F4 to close an application. This was the only screen reader that was fully functional using Microsoft Edge. It was also the only screen reader that was able to read every active element and all text on each website and application. Clearly, hands down, Narrator is the winner!
Second-Place Goes to NVDA.
NVDA performed mostly well. The problem is it uses a function called browse mode that doesn’t actually work at this time. You’re supposed to be able to toggle between focus and browse modes by pressing insert plus spacebar. It’s supposed to function like Narrator’s scan mode. Because it didn’t work, Microsoft Edge was only able to read active elements, not text, on the screen. It was also difficult to read text on other applications. Like I said before, you want to know what you’re saying “OK” to. Also, there were other applications where you had to switch the pain view to see what else was on the screen. That’s OK if you know that there are other pains on the screen. But if you don’t, you’re missing out on loads of information. NVDA is still a fantastic screen reader and the developers of the project are working on fixing browse mode. I suspect they will work out the kinks very soon. But can they keep up with all the changes and updates coming from Microsoft on an almost daily basis?
JAWS Finishes in a Distant Third.
This wasn’t even close! I don’t even know where to begin! For starters, the JAWS display driver interfered with the Microsoft Upgrade Assistant which is a program that allows customers to download Windows10 Anniversary Update without having to wait for the automatic update. I had to uninstall the Freedom Scientific display driver just to download my free copy of Windows 10 Anniversary Update. Next, JAWS does not work with Microsoft Edge unless you’re using the touch cursor. This makes Microsoft’s primary browser virtually unusable. This is inexcusable and unacceptable. JAWS has also come up with some very convoluted keystroke combinations to interact with elements on webpages. I also ran into several situations where JAWS was incapable of activating navigation bars on webpages. I just want to know, are the people at VFOserious about accessibility, or just interested in convincing people in enterprise and government that they are?
Final Thoughts.
I really enjoyed the Mark mobile voice that Narrator uses. I was also pleasantly surprised at how quickly the screen reader reacts. I’m now using it as my primary screen reader. I of course will always continue to use NVDA as well. It is an amazing product and will only continue to improve. They have one of the most talented group of developers I’ve ever seen. As for JAWS, I can’t think of one good thing to say. And that’s a difficult position for me to take. When I first became a teacher 25 years ago, JAWS was the only program that made the digital world accessible for me. It was an amazing product, and I’ve always shown a great deal of gratitude toward them, but even I have to admit that they’re not maintaining their commitment to customers. You don’t know how difficult that is for me to say this because I have a great deal of loyalty toward the people who helped me when I was younger. I hope the people at VFO and Freedom Scientific can turn things around, but most importantly I applaud the accessibility team at Microsoft. For years Microsoft has preached accessibility but seemed more interested in promoting their own advancement within the field of accessibility. The new Microsoft accessibility team is finally focusing on their actual customers. What a refreshing change! I have also recorded a podcast demonstrating the use and accessibility of Windows 10 anniversary update. I hope you give it a listen.
The views expressed here are purely my own, and should be taken as such.
I have to disagree with you about Jaws. I had no problems with the display driver when I updated to the Windows 10 Anniversary edition, and I find Jaws quite easy to use for the most part. My main two screen readers are Jaws and System Access, and NvDA comes in third. I knock NVDA quite a bit because the last version I tried was extremely choppy and sluggish. I still use a 2013 version of NVDA, and if I did not have a radio programming software for my HAM Radio that only works with NVDDA, I probably would not still have it around.
Hello
It surprised me that Window-Eyes was not mentioned at all, especially since Microsoft has bundled it with free Office program. Most users, especially in the lower grades, rely heavily on MS Word; it would be nice to know how Narrator access compares to that of the other SR’s.
Hi James,
Thank you for the great write up.
For me the bottom line here is that Microsoft is taking Accessibility seriously again and this is great!! Only good things can come from that and I am sure all screen readers will catch up with whatever it is they have to do to make our experience great.
Al
Hi James and everyone,
First, thanks for giving folks some updates on latest happenings with Anniversary Update. Overall, it was a fun read. However, I do have some concerns and some explanations to do, especially because I am the one who wrote UAC fix and have worked with NV Access on enhancing toast announcements in the Anniversary Update and have watched Edge issues closely:
Edge: Edge is an interesting subject to talk about, as it provides an example of what Microsoft should and ought not to do in the future. Back in the days of versions 1507 (build 10240) and 1511 (build 10586), Microsoft used a specific value for a UIA attribute in Edge. Sometime earlier this year, Microsoft changed an important UIA attribute value (specifically, UIA framework ID) that caused browse mode and related Edge-based controls to not function correctly, hence you may have noticed browse mode in Edge not working as expected in NVDA 2016.2.1. Fortunately, I’m happy to announce that browse mode in Edge will return in 2016.3 (late August).
Narrator’s scan mode: basically, scan mode is a combination of item navigation, text review and other goodies from VoiceOver and others. With scan mode on, up and down arrows will try to emulate caps lock+right/left arrows unless one is moving through a multi-line control.
Also, in order for Narrator to become a great screen reader, three things must be in place: solid braille support, scripting/extension development capability, and awareness of accessibility needs by third-party developers. As I mentioned in an open letter a few months ago, it is important that universal app developers should take an active role in making sure their apps are accessible, and one way to do that is to forge cooperation between screen reader users, app developers and Microsoft.
As for screen reader component compatibility: all fixed as of latest upgrade tool. However, I and others would like to urge users to wait until Anniversary Update (Version 1607) shows up on Windows Update.
As for appearing to blame a company: I’m of the opinion that credit should be given appropriate, and this includes recognizing the fact that Freedom Scientific (now part of Vision Freedom Optelec (VFO)) has opened a way for many folks to live improved lives. Same can be said about AI Squared (also part of VFO), NV Access, Dolphin Computer Access, Baum, Humanware, Microsoft accessibility team and many others.
Thus, my overall impression of the article is that it was fine, but it could have been better: some good stuff here and there, but doing some additional research and talking to folks effected by the problem described in the article could have made it a great one. Thanks.
references:
* UIA framework ID change in Edge (NVDA GitHub): https://github.com/nvaccess/nvda/issues/5955
* Open letter to Microsoft and universal app developers (Joseph Lee): https://joslee22590.blogspot.com/2015/10/an-open-letter-to-microsoft-and-windows.html
Hello, I disagree that JAWS wasn’t able to read notification. When you hear the notification sound, pressing windows key plus A you can access the notification panel. Whereas with NVDA, it automatically speaks the notification, but offer no control to turn off speaking notification. I would agree that JAWS make some changes so that people will be able to toggle speaking notification automatically or vice versa, but to say that JAWS cannot read notification is totally not true.
My workplace uses Open Office, and getting the spell check to work with NVDA and JAWS is a total pain. I think NVDA being a free screen reader should also support OO, which is also open source and widely use by those who cannot invest in Microsoft Office.
Hello,
I don’t completely agree with the ranking here since NVDA should deservedly take the first spot. The reason is because NVDA is a fully functional screen reader which can be integrated to work with brail displays, covers office applications and serves a pleasing experience on the web. Though I have been a loyal JAWS user for 6 years now, I have come to realise that NVDA is paying more attention to accessibility and integration with the latest updates of Windows. If they fix some issues such as the sluggishness on windows explorer and Microsoft word, then it would be the greatest screen reader we have.
About Jaws, I have to say that it is a little outdated compared to NVDA or Microsoft Narrator. The most annoying issue of Jaws is the inability to read notifications and the inability to read combo boxes on the settings app. Maybe we should wait for JAWS 18.
Finally, some words for Narrator, I can say that I’m pretty amazed at what Microsoft has done in the anniversary update! It’s wonderful! What Microsoft couldn’t do in twenty years did it now.
The integration with Microsoft edge is cool except for some areas where you will frequently need to switch from Scan mode to normal mode. Also reading text with Narrator on Microsoft word isn’t as pleasing as it should be. I logged in to facebook two days ago using Edge and Narrator and got pleasantly surprised when Narrator read imoji. That was uprising!
Clearly, you missed some very important facts here. First, the problems you say you have with JAWS are, in fact, well-known issues on Microsoft’s end. Microsoft has not made the onscreen model for Edge available, so neither JAWS nor Window-Eyes, (which you didn’t even say anything about), are currently not able to be made to work with Edge. This is not something that VFO has any control over. Second, the video driver being flagged was also an error on Microsoft’s part, and has since been fixed. To me, your post clearly indicates a bias against certain companies, and I feel that more research and fact-checking should have been done before writing this.
Hello,
Ranking screen readers is a difficult and somewhat subjective process. For the most part, I think you did a good job. However I’m not sure if you understand the purpose of NVDA’s review cursor. While it shares the Capslock+Space hotkey to toggle it with narrator’s scan mode, NVDA’s browse mode is only used to read websites or any other HTML based document like a PDF or an E-mail. NVDA does however have a review cursor which acts just like Narrator which is controlled either using the numpad or with caps+shift+ arrow keys in the laptop layout. Because Narrator has only one cursor used to read everything, its Scan mode can be compared to the Quicknav function of iOS/Mac VoiceOver which is why it works everywhere.
Back in June I tried to exclusively use Narrator as my main screen reader for a week with insider builds and it’s honestly amazing how much Microsoft did to improve it, Especially when it comes to crash recovery if an app freezes and working with universal apps it beats NVDA hands down. There are some controls that could work a lot better than they do now, especially tables outside of webpages. If you move with the arrow keys IE in task manager, the registry editor or any twitter client, Narrator only reads the first column which most of the time isn’t very useful. The table navigation keys in scan mode or on the function row don’t help either as if you first move across to a different column, then move down a row Narrator loses its place. I have also seen the cursor get stuck on quite simple webpages like the audio games forum, but this could have now been fixed. FInally, the cursor isn’t being tracked in the command prompt and some hotkeys still could be a lot more intuitive (I don’t see the logic behind the function row keys for table review outside of Scan Mode, which also is missing simple keys to go to the top and bottom of a window.)
So, for the time being, NVDA is still going to be my main SR on Windows, even though it has issues of its own (random freezing in Firefox or the focus jumping up multiple lines to edit fields I don’t want to be typing into). But if Microsoft keeps on going at the rate they shown so far this very well may change soon.