[jawsscripts] Re: JAWS with Internet Explorer 11, Google Chrome, Or Firefox

  • From: "Octavian Rasnita" <orasnita@xxxxxxxxx>
  • To: <jawsscripts@xxxxxxxxxxxxx>
  • Date: Tue, 25 Feb 2014 07:54:08 +0200

This is very bad then. Chrome which is the most used browser in some parts of 
the world is pretty bad accessible even after so much time since it was 
launched, Internet Explorer obviously offers a worse and worse accessibility, 
and if Firefox also becomes harder accessible.. it is not good at all.

--Octavian

----- Original Message ----- 
From: "Geoff Chapman" <gch@xxxxxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Tuesday, February 25, 2014 12:21 AM
Subject: [jawsscripts] Re: JAWS with Internet Explorer 11, Google Chrome, Or 
Firefox


> Last time I looked, couple weeks back on what I think was about firefox 
> version 24 or something like it, Jaws couldn't read a single thing on the 
> firefox screen with jaws cursor!
> So routing jaws to pc to try and click on anything, seemed to be a totally 
> lost cause to me.
> 
> 
> ----- Original Message ----- 
> From: "Octavian Rasnita" <orasnita@xxxxxxxxx>
> To: <jawsscripts@xxxxxxxxxxxxx>
> Sent: Tuesday, February 25, 2014 3:31 AM
> Subject: [jawsscripts] Re: JAWS with Internet Explorer 11, Google Chrome, Or 
> Firefox
> 
> 
>> Chrome is the worst browser, or better said it may be good, but the screen
>> readers are bad.
>>
>> I have just downgraded from IE11 to IE10 under Win 7 64bit because with 
>> IE11
>> when I needed to write large pieces of text in a textarea, after writing
>> more lines, say 20 or 30, Jaws became very sluggish.
>> Also in those textareas Jaws didn't read well as "blank" the empty lines,
>> but use to read the previous or next line, so I couldn't find where were 
>> the
>> blank lines to write there.
>> Plus that for many times it was hard to use the web page using the Jaws
>> cursor, because sometimes the cursor couldn't see the entire screen or 
>> route
>> jaws to pc cursor command didn't put the Jaws cursor right at the PC 
>> cursor
>> location.
>>
>> IE10 is a little better, but not great.
>>
>> Firefox also has problems when trying to read the screen using the Jaws
>> cursor, similar to the ones in IE11, so routing Jaws to PC doesn't work 
>> very
>> well, but sometimes it works OK.
>>
>> I told you what I found and I am curious what others say, because 
>> regarding
>> IE11, I am not sure if Jaws was my problem or that Jaws didn't like the
>> video card and its driver... so I can't make a very good recommendation, 
>> but
>> anyway, in any case, IE10 is better than IE11.
>>
>> -Octavian
>>
>> ----- Original Message ----- 
>> From: "Chad Foster" <chad.foster@xxxxxxxxxx>
>> To: "Scripting" <jawsscripts@xxxxxxxxxxxxx>
>> Sent: Monday, February 24, 2014 4:59 PM
>> Subject: [jawsscripts] JAWS with Internet Explorer 11, Google Chrome, Or
>> Firefox
>>
>>
>>> All, I am working on a scripting project and need to find the  best
>>> browser to use. The customer preferences are: (1) Google Chrome; (2)
>>> Internet Explorer 11; and, (3) Firefox.
>>>
>>> Does anyone have success using JAWS with Google Chrome? If so, what
>>> version?
>>>
>>> What about IE11? Firefox?
>>>
>>> Any and all suggestions are appreciated.
>>>
>>>
>>> Thank you,
>>>
>>> Chad
>>> What is the best version of Firefox to use with JAWS?
>>> __________�
>>>
>>> View the list's information and change your settings at
>>> //www.freelists.org/list/jawsscripts
>>>
>>
>> __________�
>>
>> View the list's information and change your settings at
>> //www.freelists.org/list/jawsscripts
>> 
> 
> __________�
> 
> View the list's information and change your settings at 
> //www.freelists.org/list/jawsscripts
>
__________�

View the list's information and change your settings at 
//www.freelists.org/list/jawsscripts

Other related posts:

  1. Home
  2. jawsscripts
  3. Archive
  4. 02-2014