Re: Article on Screen Reader History (including NVDA)

David Goldfield

As this is a list for the discussion of NVDA I don’t want to wander too far off into JAWS territory out of respect to both the users and developers of NVDA. What I’ll say is that with JAWS you can use the touch cursor to access the screen and with NVDA you have object navigation.


David Goldfield,

Blindness Assistive Technology Specialist

NVDA Certified Expert


Subscribe to the Tech-VI announcement list to receive news, events and information regarding the blindness assistive technology field.



From: <> On Behalf Of Thomas N. Chan
Sent: Thursday, July 28, 2022 8:06 PM
Subject: Re: [nvda] Article on Screen Reader History (including NVDA)


I hear you. The strength of Window-Eyes when I select it as my screen reader is, the reading of mouse movement and what's its under the mouse cursor.

Jaws can't do that. Do we need to use a magnifying software to read it?

What  if the sighted folks wants to show you this particular text, or whatever information on the screen, do they need to use a screen reader to get to it and show us?


Is there a way for us to do things when we support sighted colleagues instead of the other way around?



Thomas N. Chan



On Mon, Jul 25, 2022 at 7:07 AM Russell James <4rjames@...> wrote:

Thank you for sharing this article and for allowing the discussion!


I enjoyed reading the article and was not aware of some of the history.


I was reading the article using Firefox and NVDA

I ran into multiple accessibility issues while reading

Probably because I was reading using explore by mouse...  :-)


I started using screen readers for software development work in the 1980's

That was when GW Micro was selling/supporting Vocal-Eyes for DOS.

I went on for years using DOS based interfaces to other systems to leverage Vocal-Eyes for my work.

Vocal-Eyes and the GW Micro developers and technical support team were incredible!


When Windows 3 was coming I learned that GW Micro would be providing Window-Eyes.

While I was concerned about using agraphical user interface I was confident GW Micro would be there to support me and my work.

Window-Eyes and GW Micro never let me down until they were acquired...

I used Window-Eyes from Windows 3.1 up through Windows 10!


I was spoiled by Window-Eyes and explore by mouse!

I adopted this random access method for reading content on the screen.


When I learned that Window-Eyes may not be available in the future I turned to NVDA.

Eventually I pushed myself to make NVDA my primary screen reader.

I would usually have Window-Eyes installed in case I ran into problems with NVDA.

When I shared my desire for explore by mouse with the NVDA developers

They simply told me I was using it wrong...


As I learned from reading this article, I must still be using NVDA the wrong way...  :-)


I wish GW Micro and Window-Eyes were still a supported option!


I have never used any other screen reader for Windows.




On Sun, Jul 24, 2022 at 4:59 PM David Goldfield <david.goldfield@...> wrote:

I have wanted to participate in this discussion since it started as I clearly remember many of the DOS screen readers and how the Windows accessibility landscape unfolded as I was working in the a.t. industry during that time I avoided doing so as I saw it not relevant to the purpose of this list. However, since Brian has made it clear that he’s permitting it I’m going to respond to messages in this thread.


As for browse mode and virtual cursor functions not being available in early screen readers I think this depends on how you define early. Window-Eyes was the first screen reader that I remember using this paradigm in the late ‘90s and JAWS added it in version 3.3. Window-Eyes implemented it using MSAA and it was so slow that waiting for pages to load was unbearable. JAWS added the capability a year or so later but pages were rendered much faster even on computers which we would now consider to be painfully slow. When I wrote a blog post paying tribute to Window-Eyes I was also advised by a reader that Artic Winvision added a similar feature but not being a Winvision user I can’t verify this.

David Goldfield,

Blindness Assistive Technology Specialist

Error! Filename not specified.

NVDA Certified Expert


Subscribe to the Tech-VI announcement list to receive news, events and information regarding the blindness assistive technology field.



From: <> On Behalf Of Gene
Sent: Sunday, July 24, 2022 5:21 AM
Subject: Re: [nvda] Article on Screen Reader History (including NVDA)


I'm not sure this is the place to go into at length how much screen-readers have advanced since they first came out but they have advanced enormously.  For just one example, there was no Browse Mode or Virtual PC Cursor in early screen-readers. 


On 7/24/2022 4:00 AM, Sean Murphy wrote:

The screen reader for OS2 was released in 1992 Sept. Not sure if this was before Window Bridge or not. The wiki article on Outspoken indicated it was released for the Mac in 1989. This is interesting. Has screen readers really developed beyond what they were like in the 90’s?


From: <> On Behalf Of Brian Vogel
Sent: Wednesday, 20 July 2022 1:16 PM
Subject: Re: [nvda] Article on Screen Reader History (including NVDA)


On Tue, Jul 19, 2022 at 10:41 PM, Dan Thompson wrote:

I would love to read the article on screen readers when it is available.

Uh, it's what started this entire topic.

The Hidden History of Screen Readers: For decades, blind programmers have been creating the tools their community needs

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill


Join to automatically receive all group messages.