Re: NVDA in Employment
toggle quoted messageShow quoted text
Productivity is a different story, and the answer will depend on the user and what they do at work. For me, NVDA seems more limiting than productive, especially with software/web design because unless you take the time to create your own features in an add-on like I do, then I don’t get much work done. Then again, JAWS is limiting in this aspect of accessibility as well.
Aside the user interface design, NVDA is a deal breaker with software/web development because the autocomplete features of most IDEs like VS Code, Notepad++, and Visual Studio don’t work with screen readers, or lack in usability. NVDA’s support for autocomplete in these editors/IDEs is lacking at best and adds almost 30 seconds of time to the additional time it takes to edit each line of code. Considering it takes 30 seconds to type a line of code and another 30 seconds to use autocomplete, 1 minute to type a line of code is quite slow. JAWS speeds up time with autocomplete. It only takes me 10 seconds a line of code on average because autocomplete can finish most lines of code for me, and I know what autocomplete is doing as well.
From: kelby carlson
Sent: Sunday, August 25, 2019 8:39 AM
Subject: Re: [nvda] NVDA in Emploandenp
I do actually use NVDA at work; my IT department didn't have an issue with it, so I wasn't aware that this was even a problem.
My real question is whether NVDA leads to noticeably less productivity in employment based on user experience of those who use it at work. I don't think it does for me, but I haven't used JAWS in a long time, so I'm not sure.
That skim reading feature doesn't look quite as advanced as the one JAWS has; no text rules etc.