hi,
yes, I am a eexpert user of nvda window eyes and jaws. after using
these screen readers I can say that there is really no difference in
commands.
the difference is how they work with windows and other applications.
jaws is the most popular and widely used screen reader, while window
eyes and nvda remains on second and third places.
I use nvda when I'm going on youtube, because af far as I know jaws
doesn't tell me the video duration. window eyes, well, I may use it
when I find any application that is not accessible with jaws (I know a
few).
everyone has their own liking, but I prefer JAWS as my primary screen reader.
Best regards,
Amit



On 12/31/15, Kevin Wollenweber <[email protected]> wrote:
> You know, in some ways I, too, find JAWS 15 more stable than JAWS 16 or 17.
> That is why I havcen't as yet upgraded to WINDOWS 10.  I don't dare get rid
> of JAWS 15.
>
> I don't know what I'll do should a good portion of the internet change to
> the extreme where older versions of WINDOWS are no longer compatible.
>
> Kevin
>
> -----Original Message-----
> From: Maria Campbell [mailto:[email protected]]
> Sent: Wednesday, December 30, 2015 7:26 PM
> To: [email protected]
> Subject: Re: Are there any NVDA (or WindowEyes) and JAWS "dual users" or
> people who've used both here?
>
> I just send an email to tech support with any problems.  Not submitting bug
> reports, I wonder if these are at all addressed personally, as the emails
> certainly are.
> Strangely, I find JAWS 15 to be more stable than either 16 or 17.
>
>
> On 12/30/2015 6:15 PM, Brian Vogel wrote:
>> Thanks for the continuing input, I appreciate it more than I can say.
>>
>> Note to Maria:  I have not as yet even touched JAWS 17.  I've got two
>> clients who are having some major problems with JAWS 15 and I'm slated
>> to update both to JAWS 17 in the near future.  The one client is
>> licensed to go up through the not-yet-in-existence JAWS 18, but JAWS
>> 17 has been hateful about installing so I need to involve Freedom
>> Scientific technical support on the next try.  I've typically not had
>> this sort of crankiness with installation in the past.
>>
>> Also, since this is the group that can answer this question best, do
>> you all feel that it is a worthwhile exercise for me to teach my
>> clients how to submit a trouble report via the Freedom Scientific
>> website, or should I just encourage them to use e-mail and teach them "the
>> essentials"
>> about what must be included in a technical support request message?
>>   Over time I have come to feel quite strongly that it is an essential
>> skill to be able to interact with FS tech support completely
>> independently since the end user is always going to encounter issues I
>> never will when I'm training them and these aren't, in most cases, in
>> the "optional to resolve" category.  What say you all?
>>
>> Brian
>>
>>
>
> --
>
> Sunny Day
> Maria Campbell
> [email protected]
>
> Be patient with God:  Be patient with yourself:  Be patient with others.
>
>
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
--
JFW related links:
JFW homepage: http://www.freedomscientific.com/
JFW List instructions:
To post a message to the list, send it to [email protected]
To unsubscribe from this mailing list, send a message to 
[email protected]
Archives located at: http://www.groups.io/g/jfw/threads
Alternative archives located at: 
http://n2.nabble.com/JAWS-for-Windows-f2145279.html

If you have any concerns about the list, posts received from the list, or the 
way the list is being run, do not post them to the list. Rather contact the 
list owner at [email protected].
-=-=-
Groups.io Links:

You receive all messages sent to this group.

View This Message (#36001): https://groups.io/g/jfw/message/36001
Mute This Thread: https://groups.io/mt/308336?uid=21656

Change Your Subscription: https://groups.io/g/jfw/editsub?uid=21656
Unsubscribe: https://groups.io/g/jfw/leave/46502/1292106160/xyzzy

Group Home: https://groups.io/g/jfw
Contact Group Owner: [email protected]
Terms of Service: https://groups.io/static/tos
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to