Re: I'm dissappointed


Hi Susan,

Ah, you brought up important points, and a justification for what I’m about to do soon.

Google applications: there were several seminars/sessions during NVDA Users and Developers Conference (NVDACon) where Google apps were discussed. The most recent one was done by a Google engineer (NVDACon 2017) and talked about what Google is doing to make Chrome and other applications accessible.

You say you’re using Firefox? Which version is it and which NVDA version did you get? I highly recommend using NVDA 2017.3 or later and Firefox 52 or later for improved accessibility to Google applications. Also, bare in mind that Google apps do change from time to time, and in some cases, using Google Chrome (or Microsoft Edge on Windows 10) might offer a slightly better experience.

As for what I’m planning to do: sometime in 2018, I plan to hold a seminar that goes over how to provide a more proper technical support offline. It’ll involve talking about some NVDA internals, as well as common issues and troubleshooting tasks, user-centric questions, etiquette and what not.

Tech support over the phone: as much as I’d like to offer phone support, I’m a college (undergraduate) student and a forensics (speech and debate) competitor, so my schedule is tight. I’m also teaching two related courses on NVDA development (one on Python and another on NVDA internals) along with my Windows Insider duties, so there’s not a lot of time I can devote to phone support. I do agree that as much as online support system is valuable, tech support over the phone is something we cannot forget. I’ll keep an eye out for news on that front and see what can be done.

To the rest of the community: you know what to do: please help a college student by stepping up to this challenge. I don’t want to hear words alone: I want action please.




From: [] On Behalf Of susan@...
Sent: Sunday, December 24, 2017 6:55 AM
Subject: Re: [nvda] I'm dissappointed


Hi Joseph,
My expectations for tech support are all formats: email, dedicated tech support, hands on guide and youtubes. The students I am working with and teaching screen readers are generally 10 years old and up. We teach students the basics of screen readers at the younger age and also start to teach them about tech support and where to get support. We always teach them to look online for support and love you tubes. However, there are times that the online resources don't answer the questions at which point my students call a tech support number. The reality of the situations is I have usually a 30 minute block to work on screen readers so when a problem comes up I am looking for the most direct way to get an answer. Sometimes the fastest way is to have a dedicated tech support number.

The issues I have been having are around google docs and google classroom. All my schools are everything google and many times NVDA commands do not execute the way they are supposed to. For example, we are using Firefox and working on a google doc and when using the command to read all it doesn't always execute. I do have the accessibility feature turned on. The same command does work with NVDA in microsoft word. Issues like this are time consuming to figure out and spend hours at home trying different possibilities. If there was a dedicated number or  live person to speak with it might make this process more usable for teachers like myself. Screen readers are one part of what we teach our students with visual impairments during the day and it is very difficult to find time to do this work during the school day. 


Join to automatically receive all group messages.