No argument with what's been written as we consider this subject from many
angles except for one really big misconception. I have been hearing
repeatedly that "such a small market". This is inaccurate. You are all
thinking of only the current JAWS and WE using community in the U.S. Yes,
that is a relatively small group, though big enough. However, you are
forgetting that we are talking in the case of Microsoft of a world market
and in that number is not only those who already use screen reading
software, but all of those who might if it were easy to use and affordable.
WE are talking in that case somewhere around 100 million people based on UN
statistics. By any measure that is a majorly significant and attractive
market. I also don't see any reason why we cannot see two different, but
equal, considerations in screen reading products. That is, I see no reason
why a screen reader cannot be "out of the box" simple for a beginner,
perhaps like System Access, and yet have tools and options like JAWS for
advanced power users. Microsoft Office is like that for instance. It
works, and works simply for a beginner who wants to do basic word processing
or simple spreadsheets. But, if you are a power user who does complicated
documents, or publishing, or multi-level financial analysis, then that same
software has those advanced features to keep you busy and learning for
years.
Seems simple really. It's a matter of a desire on the part of a developer,
Microsoft, or a third party company, to actually make it happen.
Bill
-----Original Message-----
From: Visually Impaired Computer Users' Group List
[mailto:[log in to unmask]] On Behalf Of Dan Rossi
Sent: Friday, December 05, 2008 8:09 AM
To: [log in to unmask]
Subject: Re: [VICUG-L] Microsoft where should it go with regard to screen
readers
I will start out by saying that I have some pretty significant reservations
about Microsoft supplying a fully functional screen reader as part of the
operating system.
I do believe that a free screen reader would eventually kill the current
Windows screen readers. As long as it was a reasonable substitution. The
largest concern I have is how many resources would MSFT be willing to lay
out for such a small population? What incentive would MSFT have to improve
the screen reader, or support non Microsoft products?
Certainly, if the screen reader was closely tied to the OS, and developers
used the Microsoft development platform, then access would be assured.
However, if developers used Windows standards today, the vast majority of
applications would be reasonably accessible out of the box, however, they
don't and I don't see why that would change.
Also, people seem to forget that the reason why a lot of applications quote
appear quote to work so smoothly with JAWS or WindowEyes, is because a lot
of work went into building script files and set files so that certain things
read when you would expect them to, and in a meaningful way, take the spell
checkers for example. They seem to read just what you want to hear at the
right time. JAWS doesn't do that on it's own. That is a customized script.
So, if MSFT was willing to support a screen reader fully, and they had some
leverage on the developers to use a specific development kit, then a
Microsoft screen reader could be quite useful. I have concerns though, that
those requirements would be met.
Lastly, the concept of a screen reader working right out of the box is, for
the time being, a total fantasy. I say that only because, working out of
the box is different for some people than for others. I was recently made
aware of that fact while talking with a friend. I just happened to say in a
conversation that the Internet is about the greatest thing I could imagine
for a blind person. I can read all my utility statements, bank statements,
credit card statements, news papers, online. I can pay all my bills online,
I don't need a sighted person to read my private statements to me.
She, was utterly surprised since she could do none of that. She has been
using JAWS for about two years, has even received some training on it, yet
she is constantly frustrated that she cannot get much out of the internet.
Even if she were using a MAC, I don't believe she would have much better
luck. As far as I am concerned, JAWS works right out of the box with
Internet explorer, yet, others think it is horrible. No one screen reader
will be the same for every person. No two people will have the same exact
experience with any screen reader. Just because one person thinks that JAWS
is the be all and end all, and WindowEyes just isn't as good, probably
hasn't spent enough time with WE to really get used to it, and I am a JFW
user saying this.
If a screen reader doesn't have the ability to modify what it says, IE,
adjust the verbosity, look at all the dozens of verbosity settings in JFW, I
for one love the ability to change how much is spoken depending on my mood,
or if I am working with a new app or on a particularly complex web page. If
a screen reader can't do that, I have some concerns. Thus, the concept of
working out of the box bothers me, because it assumes a lowest common
denominator. Working out of the box for who? Or is that whom?
Anyway, I would never willingly choose to limit my options, thus I would
rather see Microsoft work closer with screen reader developers than put them
out of business.
--
Blue skies.
Dan Rossi
Carnegie Mellon University.
E-Mail: [log in to unmask]
Tel: (412) 268-9081
VICUG-L is the Visually Impaired Computer User Group List.
Archived on the World Wide Web at
http://listserv.icors.org/archives/vicug-l.html
Signoff: [log in to unmask]
Subscribe: [log in to unmask]
VICUG-L is the Visually Impaired Computer User Group List.
Archived on the World Wide Web at
http://listserv.icors.org/archives/vicug-l.html
Signoff: [log in to unmask]
Subscribe: [log in to unmask]
|
