|
osdir.com mailing list archive |
|
Subject: Jaws and Firefox2 - dropdown combo and about:config - msg#00001List: mozilla.accessibilityexactly the same results. Firefox is version 2.0. Just saw the posts on the ajax dropdown combobox and Jaws. What I've found is that the dropdown does work as described. I think some of the confusion may come from the fact that having carret browsing turned on while using Jaws can cause major weirdness. Pressing f7 will toggle carret browsing mode, but knowing whether its on or off can be an issue. Normally, the system will tell you when you press f7 whether its enabling or disabling the feature, but if you've disabled this warning via javascript or about:config, then it'll be more difficult to know whether carret browsing is on or off. See notes on about:config below. There is just a feeling of sluggishness and flakeyness while using Jaws and Firefox. I've been trying to switch, but things just aren't quite right. Hard to put into words... One issue is that moving from heading to heading doesn't always work. Sometimes, if there is a URL just before the target heading, Jaws will land on that element instead of the heading. While investigating this, I found a potentially bigger problem: if you have Jaws running when you do "about:config", speech just completely stops. You have to goto task manager and kill Firefox to get it back. Sometimes pressing control+alt+delete will bring back speech enough to kill firefox, other times you have to press appKey+u (to turn on narrator). The act of turning on narrator usually frees up Jaws enough so that you can then kill firefox (and turn off narrator). This happens with all versions of Jaws greater than or equal to version 7.1. I did not actually try 7.0, but I tried 5.1, 6.1, and 6.2. It also happens with both firefox 1.5.x and 2.0. Thanx. -- Rich I find television very educating. Every time somebody turns on the set, I go into the other room and read a book. Groucho Marx (1890 - 1977) Thread at a glance:
Previous Message by Date: click to view message previewFirefox crop circle now on Google MapsA bit of fun courtesy of Oregon State University's Linux Users Group. http://tinyurl.com/yx2fas -- Steve Lee www.oatsoft.org www.schoolforge.org.uk www.fullmeasure.co.uk Next Message by Date: click to view message previewRE: Jaws and Firefox2 - dropdown combo and about:configAs another jaws user, I must agree with the below comments. IE is fluid, fast, and responsive as anything with jaws. Firefox seems slower, not as responsive, and buggy. Not firefox itself, mind you, but the interaction with firefox and jaws. Take care, Sina -----Original Message----- From: dev-accessibility-bounces@xxxxxxxxxxxxxxxxx [mailto:dev-accessibility-bounces@xxxxxxxxxxxxxxxxx] On Behalf Of Rich Caloggero Sent: Tuesday, December 05, 2006 12:31 PM To: dev-accessibility@xxxxxxxxxxxxxxxxx Subject: Jaws and Firefox2 - dropdown combo and about:config Note: using Jaws 8.0.423U and winXP home edition. Used winXP pro with exactly the same results. Firefox is version 2.0. Just saw the posts on the ajax dropdown combobox and Jaws. What I've found is that the dropdown does work as described. I think some of the confusion may come from the fact that having carret browsing turned on while using Jaws can cause major weirdness. Pressing f7 will toggle carret browsing mode, but knowing whether its on or off can be an issue. Normally, the system will tell you when you press f7 whether its enabling or disabling the feature, but if you've disabled this warning via javascript or about:config, then it'll be more difficult to know whether carret browsing is on or off. See notes on about:config below. There is just a feeling of sluggishness and flakeyness while using Jaws and Firefox. I've been trying to switch, but things just aren't quite right. Hard to put into words... One issue is that moving from heading to heading doesn't always work. Sometimes, if there is a URL just before the target heading, Jaws will land on that element instead of the heading. While investigating this, I found a potentially bigger problem: if you have Jaws running when you do "about:config", speech just completely stops. You have to goto task manager and kill Firefox to get it back. Sometimes pressing control+alt+delete will bring back speech enough to kill firefox, other times you have to press appKey+u (to turn on narrator). The act of turning on narrator usually frees up Jaws enough so that you can then kill firefox (and turn off narrator). This happens with all versions of Jaws greater than or equal to version 7.1. I did not actually try 7.0, but I tried 5.1, 6.1, and 6.2. It also happens with both firefox 1.5.x and 2.0. Thanx. -- Rich I find television very educating. Every time somebody turns on the set, I go into the other room and read a book. Groucho Marx (1890 - 1977) _______________________________________________ dev-accessibility mailing list dev-accessibility@xxxxxxxxxxxxxxxxx https://lists.mozilla.org/listinfo/dev-accessibility Previous Message by Thread: click to view message previewFirefox crop circle now on Google MapsA bit of fun courtesy of Oregon State University's Linux Users Group. http://tinyurl.com/yx2fas -- Steve Lee www.oatsoft.org www.schoolforge.org.uk www.fullmeasure.co.uk Next Message by Thread: click to view message previewRE: Jaws and Firefox2 - dropdown combo and about:configAs another jaws user, I must agree with the below comments. IE is fluid, fast, and responsive as anything with jaws. Firefox seems slower, not as responsive, and buggy. Not firefox itself, mind you, but the interaction with firefox and jaws. Take care, Sina -----Original Message----- From: dev-accessibility-bounces@xxxxxxxxxxxxxxxxx [mailto:dev-accessibility-bounces@xxxxxxxxxxxxxxxxx] On Behalf Of Rich Caloggero Sent: Tuesday, December 05, 2006 12:31 PM To: dev-accessibility@xxxxxxxxxxxxxxxxx Subject: Jaws and Firefox2 - dropdown combo and about:config Note: using Jaws 8.0.423U and winXP home edition. Used winXP pro with exactly the same results. Firefox is version 2.0. Just saw the posts on the ajax dropdown combobox and Jaws. What I've found is that the dropdown does work as described. I think some of the confusion may come from the fact that having carret browsing turned on while using Jaws can cause major weirdness. Pressing f7 will toggle carret browsing mode, but knowing whether its on or off can be an issue. Normally, the system will tell you when you press f7 whether its enabling or disabling the feature, but if you've disabled this warning via javascript or about:config, then it'll be more difficult to know whether carret browsing is on or off. See notes on about:config below. There is just a feeling of sluggishness and flakeyness while using Jaws and Firefox. I've been trying to switch, but things just aren't quite right. Hard to put into words... One issue is that moving from heading to heading doesn't always work. Sometimes, if there is a URL just before the target heading, Jaws will land on that element instead of the heading. While investigating this, I found a potentially bigger problem: if you have Jaws running when you do "about:config", speech just completely stops. You have to goto task manager and kill Firefox to get it back. Sometimes pressing control+alt+delete will bring back speech enough to kill firefox, other times you have to press appKey+u (to turn on narrator). The act of turning on narrator usually frees up Jaws enough so that you can then kill firefox (and turn off narrator). This happens with all versions of Jaws greater than or equal to version 7.1. I did not actually try 7.0, but I tried 5.1, 6.1, and 6.2. It also happens with both firefox 1.5.x and 2.0. Thanx. -- Rich I find television very educating. Every time somebody turns on the set, I go into the other room and read a book. Groucho Marx (1890 - 1977) _______________________________________________ dev-accessibility mailing list dev-accessibility@xxxxxxxxxxxxxxxxx https://lists.mozilla.org/listinfo/dev-accessibility Loading Comments...
|
|
