Why I Ditched JAWS for NVDA: A Practical Screen Reader Switch

Who This Is For (And Why I'm Writing It)

If you're a blind or low-vision computer user who has been loyal to JAWS for years, or if you're a developer or IT pro responsible for making software accessible, this is for you. I've been using screen readers for over a decade, and I've watched the landscape shift. In WebAIM's 2024 Screen Reader User Survey, JAWS held a narrow lead as the primary desktop screen reader—40.5% vs. NVDA's 37.7%—but when respondents were asked which screen reader they use at all, NVDA came out on top at 65.6%, beating JAWS's 60.5%. That gap tells me something: more people are keeping NVDA around as a backup, and many are using it as their main tool. I made the switch to NVDA permanently last year, and I'm here to tell you why you might want to too.

Why I Switched: The Cost and the Community

Let's be blunt: JAWS costs money. NVDA is free. That's not a small thing. The WHO estimates that over 2.5 billion people currently need assistive technology, but about 90% of them don't have access to it. Cost is a huge barrier. NVDA, developed by the non-profit NV Access, is free and open source, and it's translated into more than 55 languages, used in over 175 countries. That's a game-changer for accessibility. But I didn't switch just because of price. I switched because NVDA's community is vibrant and its development is fast. When a new Windows update breaks something, NVDA often gets a fix before JAWS does. And with 86.1% of screen reader users on Windows, that matters.

Step 1: Start With NVDA on a USB Stick

Before you commit, try NVDA without installing it. Download the portable version from the NV Access website and run it from a USB stick. This way, you can test it on your own computer without disrupting your current setup. I did this for a week, using NVDA for email, web browsing, and document editing, while keeping JAWS available. The transition was smoother than I expected. One thing to note: NVDA's default speech rate felt slower than what I was used to, but I quickly adjusted the settings to match my preference.

Step 2: Learn the NVDA Key Commands (They're Different)

NVDA uses the Insert key (or Caps Lock) as its modifier, similar to JAWS, but many specific commands differ. For instance, navigating by headings—essential for efficient web browsing—is done with the H key in both, but the way you access the elements list is different. In NVDA, it's Insert+F7. I spent an afternoon going through the built-in command reference, and within a day I was almost as fast as I was with JAWS. Don't let the learning curve scare you. The 71.6% of screen reader users who first navigate by headings will find NVDA just as capable.

Step 3: Configure Braille Output If You Use It

If you're one of the 38% of screen reader users who use braille output, NVDA supports it well. I use a refreshable braille display, and NVDA recognized it automatically. But there's a catch: NVDA's default braille settings may not match your display's specifications. You'll need to go into NVDA's settings and select your display type and input method. It took me about ten minutes to get it right. Once configured, braille output works seamlessly. This is a critical feature for many, and NVDA doesn't skimp on it.

Step 4: Use It on Your Phone, Too

Screen readers aren't just for desktops. The same survey found that 91.3% of screen reader users use one on a mobile device. On my iPhone, I use VoiceOver, which is built in and excellent. But when I'm testing a web app for accessibility, I often switch to TalkBack on an Android device to see how it behaves there. Having both NVDA on Windows and TalkBack on Android gives me a broader perspective. If you're a developer, this cross-platform testing is invaluable.

What Can Go Wrong: The CAPTCHA Problem

Here's a warning: CAPTCHAs are the most problematic item for screen reader users, according to the WebAIM survey. And respondents with disabilities were twice as likely to rank CAPTCHA as problematic. I've encountered CAPTCHAs that were impossible to solve with NVDA, even with audio challenges. This isn't a failure of NVDA—it's a failure of web design. But it's something you'll face. My advice: when you encounter a CAPTCHA, try the audio version, and if that fails, contact the site's support. Many sites don't realize their CAPTCHA is inaccessible. This is a reminder that even the best assistive technology can't overcome inaccessible content. As the survey showed, 85.9% of screen reader users say that better websites, not better assistive technology, would have the bigger impact on web accessibility.

My Recommendation: Switch, But Keep JAWS Around

I'm not saying you should delete JAWS. In fact, I recommend keeping it installed as a backup. But make NVDA your primary. The data supports it: NVDA is the most commonly used screen reader overall, and it's free. The only reason to stick with JAWS is if you rely on specific advanced features that NVDA lacks, or if your workplace mandates it. But for most users, NVDA offers everything you need. And by switching, you're also supporting a more equitable assistive technology landscape, one where access isn't limited by cost.

Sources

• WebAIM Screen Reader User Survey - https://webaim.org/projects/screenreadersurvey10/
• NV Access - https://www.nvaccess.org/about-nv-access/
• World Health Organization - https://www.who.int/news-room/fact-sheets/detail/assistive-technology
• Apple Accessibility - https://www.apple.com/accessibility/vision/