Don,
I don't really know about web browsing on iOS because I seldom use it
for that. I bought an iPad Pro 9.7 with the keyboard/case option, which
is actually impressive for its size. I bought it with the thought that
it could at least replace my old laptop for casual use. In general it's
okay. I stress the word, okay. Overall I'm very disappointed in
VoiceOver. To me it's closer to Narrator than a "real" screen reader.
And Microsoft is on a fast track with Narrator. So who knows how long
before it will be on par with VoiceOver.
I understand that VoiceOver has more to offer on a real Mac, but I'm not
ready to put in all the time it would take, and in a mad rush to meet
the return deadline, to figure it out.
But of course this is highly dependent on what you do and what you want
out of your screen reader. And our personal preferences vary so much
it's almost impossible to give practical advice on it.
Regards,
Tom
On 4/4/2017 9:11 AM, Don H via Talk wrote:
Could the difference between accessibility on a I phone or I Pad and a
Mac book be that the phones and I pads are running the mobile versions
of a web site or ap and the Mac book isn't? I have been considering
purchasing a I Pad but just don't know which one to buy and wether it is
really a solution to avoid having to move to JAWS. I have been using
NVDA and it works fairly well but too has its shortcomings on some web
pages.
On 4/4/2017 8:02 AM, Steve Jacobson via Talk wrote:
Tony,
I share some of your frustrations. I had to use JAWS more during the
past year to do certain things on my job, and I was surprised at all
of what I feel are bugs in JAWS. It always seemed to me that many
JAWS users felt that Window-Eyes had a monopoly on bugs. On my job,
both JAWS and Window-Eyes worked on some older software that I used
while NVDA did not work with it. While I like my iPhone, I have found
myself frustrated there with bugs as well. The pace of change in
technology, particularly web site development, is really putting a
squeeze on our access on all platforms in my opinion. I know of
people who have switched to the MAC and would never switch back, but I
also know of a few who have switched back. Also, some of your
examples are partly due to inconsistent or poor web browser support.
People I have talked to who work on accessibility have told me that if
a web page is at all complicated, it needs to be tested with all
combinations of screen readers and web browsers to know if the page
will work. There is often even browser-specific code in web sites
even without accessibility. It is very possible, for example, that
Netflix is running different code when you access the very same page
with a MAC as you access with a Windows browser. This makes it very
hard to determine where problems exist.
I hope that your switch to Apple works well for you.
Best regards,
Steve Jacobson
-----Original Message-----
From: Talk
[mailto:[email protected]] On
Behalf Of Tony C via Talk
Sent: Tuesday, April 04, 2017 3:46 AM
To: Window-Eyes Discussion List <[email protected]>
Subject: Windows screen readers
Hello, Before I say anything, let me first say that I was a Jaws user
for several years before switching to Window Eyes back in 2004, and
I’ve been a faitful WE user ever since. Why is it that everytime
someone can’t use a certain website or something like I tunes or
Netflix the first thing is they need to fix their website. Why is it
that II a person can go to Netflix on an IOS device and using Voice
Over can use netflix with no problem. Now we are talking about a free
built in screen reader as opposed to an $895 and $1195 third party
screen readers? I can’t use Netflix on my PC because both Jaws and
Window eyes people have told me it isn’t accessible. However I can go
to Netflix using my I phone or my I Pad Mini and use netflix with the
free screen reader? I mean I don’t get it, support at both Jaws and WE
have said it isn’t accessible and they can’t make their screenreaders
work with it, but IOS does???
_______________________________________________
Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/steve.jacobson%40visi.com.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
_______________________________________________
Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/lmddh50%40comcast.net.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
_______________________________________________
Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/tom.kingston%40charter.net.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
_______________________________________________
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
