For years, JAWS (Job Access With Speech) was the screen reader in North America, alongside the built-in VoiceOver on macOS. Then came NVDA, shaking things up. Finally, we have the ubiquitous ChromeVox, the built-in screen reader on all Chrome OS devices. Let’s explore my experiences with each, considering their platforms and target users.
JAWS: Sink or Swim?
This shark-themed screen reader was one of the first on Windows. I remember it running on DOS/Windows 3.1 as a separate piece of hardware – talk about ancient history! Today, you can download it… after paying a hefty price. Last I checked, a license cost around $1,000 Canadian, not including updates.
Personally, I found JAWS incredibly frustrating. It always seemed slower than me, struggling to keep up with my typing and lagging during simple tasks. I later realized it’s a resource hog, demanding massive amounts of RAM. While they recommend 4GB, I’d suggest nothing less than 8GB, preferably 12GB. Anything less leads to lag, slowdowns, and crashes.
VoiceOver: A Breath of Fresh Air
Just as I was about to give up on JAWS, I discovered VoiceOver thanks to the iPhone. I fell in love with its ease of use, clean functionality, and ability to keep pace with me. This led me to buy a Mac. I lived in the Apple ecosystem for several years during university, using a MacBook Air and a MacBook Pro. It was incredibly liberating to use a system that thrived on 8GB of RAM, felt fast and responsive, and rarely crashed. VoiceOver on Mac was, and still is, one of my favorite screen readers.
NVDA: Free, Adaptable, and Flexible
NVDA is FREE! This amazing open-source software is flexible, adaptable, and highly functional, and it won’t break the bank. They do accept donations, and you can choose how much (or nothing) to give.
NVDA breathed new life into Windows for me. It’s fast, responsive, adaptable, and smoother than JAWS. Dare I say it’s the Windows equivalent of VoiceOver? I’ve been using NVDA on my personal Windows laptop for five years and love it. It can do everything JAWS could, and even allows for reprogramming (if you know Python, which I don’t).
ChromeVox: My New Love
Okay, enough with the sappiness… but ChromeVox on Chrome OS is truly smooth and unique. It operates within Chrome OS and provides the same system-level access as other screen readers. The key difference? It runs amazingly well even on sub-$500 Chromebooks. Whether you have 4GB or 16GB of RAM, a 12-inch or 16-inch screen, ChromeVox performs. It connects to most mainstream braille displays and has a built-in magnification system, though the built-in magnifier isn’t as flexible as I’d like for my dual-screen setup. Still, we’re focusing on ChromeVox’s fluid function.
From the moment you power on your Chromebook, you’re a key command away from independent system setup. Just press Ctrl+Alt+Z, and you’ll hear that familiar Google voice.
I’ve been daily driving ChromeVox for several weeks now, and intermittently for years, and I can honestly say it will soon be my primary screen reader. I’m not even sure a traditional PC has a place in my life anymore.
Conclusion
The world of screen readers has evolved significantly. From the expensive and resource-heavy JAWS to the streamlined VoiceOver, the adaptable NVDA, and the surprisingly powerful ChromeVox, users now have a range of choices. My journey has highlighted the importance of accessibility, performance, and cost-effectiveness. While each screen reader has its strengths and weaknesses, the rise of free and efficient options like NVDA and ChromeVox has democratized access to technology for visually impaired users. Ultimately, the “best” screen reader depends on individual needs and preferences, but the availability of diverse options is a huge win for accessibility.
Unapologetically Blind 