I can answer that one, I used windows 95, even back to windows 3.1. :) and it was accessible.
toggle quoted messageShow quoted text
On 3/12/2019 9:48 PM, zahra wrote:
since you are expert and tried different versions of windows,
do you mean that dos and windows 95 were not accessible and the first
accessible version of windows, is windows 98?
did i understand you correctly?
thanks again for any help, God bless you!
On 3/11/19, Shaun Everiss <email@example.com> wrote:
Well to be honest what we really need to remember is why we got jaws,
before freedom scientiffic became the real bad boy it is now, and other
Back in the dos days there was no accessibility at all.
Nothing much came from microsoft's end.
This continued through to windows 95.
In windows 98, microsoft started the active accessibility libraries
which improved things but not that much.
In 2003 or there abouts with help from gwmicro the direct chain manager
was done so you could handle readers in a multiple chained process,
before that you made your own chains but they were unstable.
Basically the first screen reader was your video card, which was part of
the next reader up till the end, the last screen reader was your video
Start one out of sync, run 2 at once, remove and or uninstall things in
an unordered fashion and you broke the chain.
There were 2 ways to fix this.
1. remove the chain, reinstall the video drivers and make another one.
Or just reformat.
Which I did a lot of.
You needed technical experience to make the reg files for the chain and
while I got dolphin support to construct one, it was as fragile as a
glass window, and not that good.
The dcm became mirror drivers in vista and 7 and then in windows 8
microsoft started the universal access librarys we all love and loath.
The reason jaws and others existed was simply because microsoft didn't
come to the party till late.
Even when xp to 7 came up, microsoft never really put much into narator.
It was just after the laws came in going against those that didn't make
It probably also helped that after the death of outspoken and all the
new laws, apple not only showed that it could make an accessible reader
but showed off that it could make something better than waht was about
at the time.
Voiceover has its limits of course but it is in all the programs and
Google, same with talkback but there were others at first in droid.
So eventually microsoft had to move.
The reason we are seeing the reader industry shrinking now is possibly
because microsoft is pulling its weight and attempting to catch up to
all the rest.
Now narator is nothing against nvda but its close.
Narator is not jaws.
But its big enough as a bold new kid on the block, not fully grown mind
you that it is shifting mountains if only smaller ones.
Time will tell with businesses if this means the death of jaws or other
readers, sadly dolphin seem to be in no hurry to improve at any speed so
sadly they may die.
I have used their stuff for ages now but still.
Of course the fact we are using a more or less web based interface both
inside of our oses now and online on websites and web based programs
There was a time where anything went and while there are a few bad
acters about its not as bad a landscape as it was 5 years back.
There is one end of the road in the screen readers though.
And this isn't actually jaws, either we have reached the inovation curve
and thats not likely because nvda is still inovating things.
Its almost like the comercial guys can't be bothered either that or ms
is moving to fast with their current model.
Or maybe we can accept that most of them have just about done everything
they set out to do and who knows.
As an os, while I really like win10's ease of use, search, and a few
other apps, and shortcuts, the only reason I wouldn't go back to 7 is
simply because 10 in some ways needs less shortcuts to get things done
and less key presses.
On the flipside without my hacking tweaking tools win10 would be quite
On the systems I admin which are not mine there are issues, and I hate
Most everything else I can get used to.
On 12/03/2019 3:04 AM, Brian Vogel wrote:
What people need to remember here is that accessibility software,
regardless of platform, has generally arisen due to a couple of
factors, with different emphases:
1. Recognition of lack of accessibility and need for it
2. Desire to make money
3. Desire to provide a real alternative to expensive option(s) many
4. Public relations value
It is no surprise that Windows, the world's most widely used computing
platform, has more than its share of screen readers because all of the
above have been at play with the various players in the field at one
point or another. I leave it to you, the reader, to decide which were
bigger factors for each product.
Factor #1 is utterly lacking on iOS and Android. Whether one likes
VoiceOver or TalkBack, both are fully mature products that do their
job admirably. There can almost certainly be nothing as far as
factors numbers one through three are concerned in these environments,
and given the degree of maturity and broad acceptance of what is
already available, factor number four has almost zero impact. Who's
going to hail "the next VoiceOver/TalkBack"? Not many, that's for
There are limited resources for implementing accessibility software,
both monetary and otherwise. It makes absolutely no sense to try to
open a market that's not really a market in the first place. Choices
have to be made, and the probability of an entity that has the history
of NVAccess doing a radical gear shift to other platforms makes very
little sense from virtually any angle.
My dear departed Aunt Lila used to quote a rather salty old relative
of hers when people brought up wishes such as this, that have all the
odds stacked against them, and for good reason, "Wish in one hand,
s*^t in the other, and see which gets full first." That sums up my
thoughts about the feasibility and likelihood of NVDA leaping across
Brian *-*Windows 10 Home, 64-Bit, Version 1809, Build 17763
*/A great deal of intelligence can be invested in ignorance when the
need for illusion is deep./*
~ Saul Bellow, /To Jerusalem and Back/
W B 6 H E F