If you're a developer, it's worth testing to make sure your code works in both (if you can only pick one, I'd suggest NVDA).
NVDA came into the picture after the Windows MSAA accessibility API was introduced, so it tends to do things more "by the book", which in my opinion leads to it finding bugs that JAWS may employ a workaround for.īut both are completely separate, complex, mature codebases that hundreds of thousands of people rely on. Going above and beyond like that isn't an easy feat for JAWS's developers to code and maintain, so I'd say that explains the cost to a degree.
JAWS started before the Windows OS offered accessibility APIs (like MSAA) to programmatically understand what was on the screen, so JAWS has a history of creative solutions to "get the job done", at any cost.įor example, JAWS installs a custom display driver which it can use to scrape raw graphics data (via OCR and other methods) to gather information from programs that don't expose any information over the OS accessibility APIs. JAWS was originally released in 1995, while NVDA started development in 2006.
0 kommentar(er)
