607950 - Issues with Jaws 12: Elements not being read out correctly, jaws not switching to forms mode.

Status: RESOLVED INVALID

(Firefox :: Disability Access, defect)

Description

[ramya_sethuraman]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.11) Gecko/20101012 Firefox/3.6.11
Build Identifier: Firefox/3.6.11

I see several issues with FF 3.6.11 and Jaws 12. The browser crashes often when Jaws is running. When a dialog opens, Jaws does not switch to forms mode. Links and buttons on the page are not read correctly sometimes. These issues are not found with earlier versions of FF.

Reproducible: Sometimes

Steps to Reproduce:
1. Launch Jaws 12
2. Navigate a page using FF 3.6.11
3. Links/buttons may not be read correctly. The browser might crash.
Actual Results:  
Browser crashes when jaws is running. I have to restart jaws for it to read the page correctly on the browser. Did not see these issues with earlier versions of FF.

Expected Results:  
Jaws should read the page correctly -- links, buttons. The browser should not crash while jaws is running.

Comment 1

[alexander :surkov (:asurkov)]

Is it valid for JAWS 11 too? Do you see this behavior on any web page? 

I'm aware of some issues when some plugins are installed but it shouldn't be completely broken. Marco, did you try JAWS 12?

Comment 2

[ramya_sethuraman]

No, I do not see these issues with Jaws 11. I am testing my internal product web page which uses Dojo and AJAX to create a rich user interface on the web. But sometimes, even basic links and menus on the page are not read  correctly by Jaws 12 on FF 3.6.11. For eg: it reads "Graphic 32" when it encounters a basic link. Inspect 32 shows the right name/role/value.

Comment 3

[ramya_sethuraman]

Correction: I do not see these issues with Jaws 11 on FF 3.5.x. I DO see these issues with Jaws 11 and FF 3.6.11.

Comment 4

[alexander :surkov (:asurkov)]

Could you please try to turn off the pref 'dom.ipc.plugins.enabled'?

Comment 5

[ramya_sethuraman]

dom.ipc.plugins.enabled is already false in my browser and dom.ipc.plugins.enabled.x.dll (4 of those) are set to true. Should I turn those to false?

Comment 6

[alexander :surkov (:asurkov)]

yes, please

Comment 7

[alexander :surkov (:asurkov)]

(In reply to comment #6)
> yes, please

and if doesn't help then try to disable plugins at all

Comment 8

[ramya_sethuraman]

I set all the dom.ipc.plugins.enabled.x.dll entries to false. Will test further with Jaws 12 and let you know if I see any improvements.

Comment 9

[David Bolter [:davidb] (NeedInfo me for attention)]

Ramya, please do let us know how that works for you.

Additionally, can you please try typing about:crashes in the location bar, the first link will be information about your most recent crash. Could you post that link here?

Comment 10

[ramya_sethuraman]

Most recent link: http://crash-stats.mozilla.com/report/pending/caf16a27-f0d2-46d9-abc3-6cd912101028

Next link: http://crash-stats.mozilla.com/report/pending/1a1d051e-8736-4817-9be5-de8642101027

Comment 11

[alexander :surkov (:asurkov)]

these aren't Gecko core crashes, crashes inside of rpc and dcom. It makes me feel there are some incompatibles between firefox/jaws or wrong firefox installation or wrong dll registration (ia2 or something).

David, who could know more about this?

Comment 12

[David Bolter [:davidb] (NeedInfo me for attention)]

I'll ping FS.

Comment 13

[David Bolter [:davidb] (NeedInfo me for attention)]

Ramya, could you please see if the problem persists in safe mode?
http://support.mozilla.com/en-US/kb/Safe+Mode

Comment 14

[Brett Lewis]

3.6.11 seems to be working fine for me.  I have not experienced the issues described here.  As Alex mentioned there is the issue with flash but apart from that I am not aware of any problems.  
I think the not reading certain controls is particularly strange.  Could you try resetting all your firefox prefs (remove your prefs.js file)?  Are there problems with JAWS in any other apps?
If you can provide some steps to reproduce the issue I will definitely take a look.

Comment 15

[ramya_sethuraman]

Hi, I saw a crash again today morning after disabling the dom.ipc.plugins.enabled plugins. This is the link: http://crash-stats.mozilla.com/report/index/bp-eb02e4b7-85bd-4d6c-93a7-890832101029

I haven't had a chance to try FF in safe mode yet. I am mainly using Jaws to test the web page but it seems to be reading native window apps correctly. You could try testing the dojo toolkit test pages with Jaws since our apps mainly use the dojo toolkit. For eg: http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/test_Dialog.html

Comment 16

[ramya_sethuraman]

Another crash when I tried to close Jaws: http://crash-stats.mozilla.com/report/index/bp-b76584fc-2af7-47e4-a5a9-33f702101029

Comment 17

[ramya_sethuraman]

Separated the crash issue to a new bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=611316

Comment 18

[Liz Henry (:lizzard) (relman/hg->git project)]

Hi ramya, Thanks so much for reporting this and including crash reports and other information! It looks like this has been overlooked for a while since the last activity was in 2010. 

Are you still experiencing this problem? Would you mind letting us know in comments if you are using a new version of Firefox and/or JAWS and if elements are being read out correctly at this point?

Comment 19

[James Teh [:Jamie]]

This concerns very old (now unsupported) versions of JAWS and Firefox. Our recent testing with JAWS and Firefox has not shown any of these issues. Closing.