Re: Firefox Again
52.5 is working fine here. one thing to check though. i keep getting nagged to install the chrome browser. every time there tool box notification w e browse mode stops working until you can find and close the popup. the firefox pull down menus are another problem. if the screen is miximized they will not open. try pressing f11 to restore the screen size to get the pull down menus back. *** are you useing the 32 or 64 bit version? i use the 32 bit version. you can find out if you open the help pull down then click on about. use the tab keys to read the dialog box i have windows 64 bit but i have had some problems with the 64bit version of firefox for years. -Original Message- From: David via Talk Sent: Wednesday, November 15, 2017 1:28 AM To: WE English Mailinglist Cc: David Subject: Firefox Again A couple of weeks ago, we had the new Firefox breaking the accessibility under WinEyes. It is well known, from version 56 and up, Firefox will no longer operate with WinEyes. Someone kindly pointed us to the business - or ESR - version of firefox, at the time being version 52. I followed their advice, and installed it, greatly enjoying to have my Firefox back on stage. This morning, Firefox notified me there was a security update to my installation. In other words, no new version, just a maintenence update. Hence, I agreed to have it perform the update. Yeah, I take it, you have already guessed what. From now on, my Firefox says version 52.5, and is no longer doable with WinEyes. It no longer goes into the programs Main Window, but says Document Window. Here you can tab around, but the arrow keys produces no real effect, and browse mode is reported to be: Not Available. Oh, how I hate that message. Smiles. OK, if anyone have seen different behavior, or have got to a bit of knowledge on how to get Firefox back, we are all ears. To me, it seems Firefox simply has crept out of all cooperation with our screen reader. Little do I hold it realistic it will ever come back. Some place, I seem to recently have read, that someone from the NVDA team had gone to Mozilla. It then is strange that we are facing this kind of lack of accessibility. It even states, under Help and About, that Firefox is meant to make the web accessible to everyone. I guess, that means except from old-timers with their WinEyes. Smiles and LOL. For some, Chrome might be an alternative. The rest of us, will be back to Internet Explorer. Chrome has its benefits, but so far I have had issues with it under certain operations. Following NVDA discussions lately, even that screen reader seem to have high issues with the newest firefox releases. It is being claimed, things will get better in version 58, but to what extent that will affect WinEyes, I am doubtful. And a recent note I read from VFO, on Jaws, seemed to indicate that even Jaws users are experiencing trouble with Mozilla lately. It was recommended not to use Firefox with Jaws 2018, if I remember correctly. Currently, I am not on that version of Jaws, so cannot confirm. Anyone here has had a chance to test newest releases of the screen reader and browser together? Goodbye to a long-lasting browser, which had numerous and beneficial advantages over any other products. Along with the somehow old-fashioned way of operating the web with Jaws - which to a degree reminds me of where WinEyes was a handful of years ago, the whole Internet browsing experience now seem to be a setback. Sure is going to take a bit of time, to get back to normal browsing speed. Sure, they made it secure? Didn't they. So secure you can't even use it. That is another kind of safety. Well, seems not even sighted users are comfortable with the newest moves from Mozilla. Probably why they tell the next release (58) will have some advancements. Does it remind you of what happened to things like Windows8, and the fact they had to go back on certain of the news, when releasing next versions? So maybe we should not wave totally goodbye to Mozilla all yet. I just wish they would have a setting somewhere, which would let the browser run the old way, even if they make some security adjustments behind the scene. Just wanted to let you know my findings. If anyone have ideas, I for one will be listening. For your info, I am under Win7 64bit, and the Firefox is reported as v52.5ESR 32bit. ___ 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/netbat%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
RE: Firefox Again
Hi Tom and all, Here's a current post by Marco on this: https://www.marcozehe.de/2017/11/07/firefox-57-nvda-users-perspective/#more-851 Best, Rod -Original Message- From: Talk [mailto:talk-bounces+rod_hutton=hotmail@lists.window-eyes.com] On Behalf Of Tom Kingston via Talk Sent: November 15, 2017 7:44 AM To: David via Talk <talk@lists.window-eyes.com> Cc: Tom Kingston <tom.kings...@charter.net> Subject: Re: Firefox Again David, This is the norm for many programs, especially browsers, when they undergo major updates. None of them work out of the box with screen readers. The screen reader developers have always had to do serious work on their end to make them work. the browser developers only give the screen reader developers the information on how to do so. And with Firefox they're in the process of a complete rewrite of the program. So it will never be accessible with Window-Eyes and only accessible with JAWS and NVDA when they make it so. You're right, Jamie Teh, one of NVDA's lead developers went to work for Mozilla. And Google Chrome is flaky. Regards, Tom On 11/15/2017 4:28 AM, David via Talk wrote: > A couple of weeks ago, we had the new Firefox breaking the accessibility > under WinEyes. It is well known, from version 56 and up, Firefox will no > longer operate with WinEyes. > > > Someone kindly pointed us to the business - or ESR - version of firefox, > at the time being version 52. I followed their advice, and installed it, > greatly enjoying to have my Firefox back on stage. > > > This morning, Firefox notified me there was a security update to my > installation. In other words, no new version, just a maintenence update. > Hence, I agreed to have it perform the update. > > > Yeah, I take it, you have already guessed what. From now on, my Firefox > says version 52.5, and is no longer doable with WinEyes. It no longer > goes into the programs Main Window, but says Document Window. Here you > can tab around, but the arrow keys produces no real effect, and browse > mode is reported to be: > > Not Available. > > Oh, how I hate that message. Smiles. > > > OK, if anyone have seen different behavior, or have got to a bit of > knowledge on how to get Firefox back, we are all ears. To me, it seems > Firefox simply has crept out of all cooperation with our screen reader. > Little do I hold it realistic it will ever come back. > > > Some place, I seem to recently have read, that someone from the NVDA > team had gone to Mozilla. It then is strange that we are facing this > kind of lack of accessibility. It even states, under Help and About, > that Firefox is meant to make the web accessible to everyone. I guess, > that means except from old-timers with their WinEyes. Smiles and LOL. > > > For some, Chrome might be an alternative. The rest of us, will be back > to Internet Explorer. Chrome has its benefits, but so far I have had > issues with it under certain operations. > > > Following NVDA discussions lately, even that screen reader seem to have > high issues with the newest firefox releases. It is being claimed, > things will get better in version 58, but to what extent that will > affect WinEyes, I am doubtful. And a recent note I read from VFO, on > Jaws, seemed to indicate that even Jaws users are experiencing trouble > with Mozilla lately. It was recommended not to use Firefox with Jaws > 2018, if I remember correctly. Currently, I am not on that version of > Jaws, so cannot confirm. Anyone here has had a chance to test newest > releases of the screen reader and browser together? > > > Goodbye to a long-lasting browser, which had numerous and beneficial > advantages over any other products. Along with the somehow old-fashioned > way of operating the web with Jaws - which to a degree reminds me of > where WinEyes was a handful of years ago, the whole Internet browsing > experience now seem to be a setback. Sure is going to take a bit of > time, to get back to normal browsing speed. > > > Sure, they made it secure? Didn't they. So secure you can't even use it. > That is another kind of safety. Well, seems not even sighted users are > comfortable with the newest moves from Mozilla. Probably why they tell > the next release (58) will have some advancements. Does it remind you of > what happened to things like Windows8, and the fact they had to go back > on certain of the news, when releasing next versions? So maybe we should > not wave totally goodbye to Mozilla all yet. I just wish they would have > a setting somewhere, which would let the browser run the old way, even > if they make some security adjustments behind the scene. > > > Just wanted to let you know my findings. If anyone have ideas, I for one > will be
Re: Firefox Again
David, This is the norm for many programs, especially browsers, when they undergo major updates. None of them work out of the box with screen readers. The screen reader developers have always had to do serious work on their end to make them work. the browser developers only give the screen reader developers the information on how to do so. And with Firefox they're in the process of a complete rewrite of the program. So it will never be accessible with Window-Eyes and only accessible with JAWS and NVDA when they make it so. You're right, Jamie Teh, one of NVDA's lead developers went to work for Mozilla. And Google Chrome is flaky. Regards, Tom On 11/15/2017 4:28 AM, David via Talk wrote: A couple of weeks ago, we had the new Firefox breaking the accessibility under WinEyes. It is well known, from version 56 and up, Firefox will no longer operate with WinEyes. Someone kindly pointed us to the business - or ESR - version of firefox, at the time being version 52. I followed their advice, and installed it, greatly enjoying to have my Firefox back on stage. This morning, Firefox notified me there was a security update to my installation. In other words, no new version, just a maintenence update. Hence, I agreed to have it perform the update. Yeah, I take it, you have already guessed what. From now on, my Firefox says version 52.5, and is no longer doable with WinEyes. It no longer goes into the programs Main Window, but says Document Window. Here you can tab around, but the arrow keys produces no real effect, and browse mode is reported to be: Not Available. Oh, how I hate that message. Smiles. OK, if anyone have seen different behavior, or have got to a bit of knowledge on how to get Firefox back, we are all ears. To me, it seems Firefox simply has crept out of all cooperation with our screen reader. Little do I hold it realistic it will ever come back. Some place, I seem to recently have read, that someone from the NVDA team had gone to Mozilla. It then is strange that we are facing this kind of lack of accessibility. It even states, under Help and About, that Firefox is meant to make the web accessible to everyone. I guess, that means except from old-timers with their WinEyes. Smiles and LOL. For some, Chrome might be an alternative. The rest of us, will be back to Internet Explorer. Chrome has its benefits, but so far I have had issues with it under certain operations. Following NVDA discussions lately, even that screen reader seem to have high issues with the newest firefox releases. It is being claimed, things will get better in version 58, but to what extent that will affect WinEyes, I am doubtful. And a recent note I read from VFO, on Jaws, seemed to indicate that even Jaws users are experiencing trouble with Mozilla lately. It was recommended not to use Firefox with Jaws 2018, if I remember correctly. Currently, I am not on that version of Jaws, so cannot confirm. Anyone here has had a chance to test newest releases of the screen reader and browser together? Goodbye to a long-lasting browser, which had numerous and beneficial advantages over any other products. Along with the somehow old-fashioned way of operating the web with Jaws - which to a degree reminds me of where WinEyes was a handful of years ago, the whole Internet browsing experience now seem to be a setback. Sure is going to take a bit of time, to get back to normal browsing speed. Sure, they made it secure? Didn't they. So secure you can't even use it. That is another kind of safety. Well, seems not even sighted users are comfortable with the newest moves from Mozilla. Probably why they tell the next release (58) will have some advancements. Does it remind you of what happened to things like Windows8, and the fact they had to go back on certain of the news, when releasing next versions? So maybe we should not wave totally goodbye to Mozilla all yet. I just wish they would have a setting somewhere, which would let the browser run the old way, even if they make some security adjustments behind the scene. Just wanted to let you know my findings. If anyone have ideas, I for one will be listening. For your info, I am under Win7 64bit, and the Firefox is reported as v52.5ESR 32bit. ___ 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
RE: Firefox Again
You should give Waterfox a try. Not sure how well it works with Window-Eyes. It is a simple browser that uses the same commands as Firefox. Just type in the word Waterfox and you should find the free download easy enough. Hope this helps. Martin -Original Message- From: Talk [mailto:talk-bounces+mbrown.brown4=gmail@lists.window-eyes.com] On Behalf Of David via Talk Sent: 15 November 2017 09:28 To: WE English Mailinglist <t...@window-eyes.com> Cc: David <trailerda...@hotmail.com> Subject: Firefox Again A couple of weeks ago, we had the new Firefox breaking the accessibility under WinEyes. It is well known, from version 56 and up, Firefox will no longer operate with WinEyes. Someone kindly pointed us to the business - or ESR - version of firefox, at the time being version 52. I followed their advice, and installed it, greatly enjoying to have my Firefox back on stage. This morning, Firefox notified me there was a security update to my installation. In other words, no new version, just a maintenence update. Hence, I agreed to have it perform the update. Yeah, I take it, you have already guessed what. From now on, my Firefox says version 52.5, and is no longer doable with WinEyes. It no longer goes into the programs Main Window, but says Document Window. Here you can tab around, but the arrow keys produces no real effect, and browse mode is reported to be: Not Available. Oh, how I hate that message. Smiles. OK, if anyone have seen different behavior, or have got to a bit of knowledge on how to get Firefox back, we are all ears. To me, it seems Firefox simply has crept out of all cooperation with our screen reader. Little do I hold it realistic it will ever come back. Some place, I seem to recently have read, that someone from the NVDA team had gone to Mozilla. It then is strange that we are facing this kind of lack of accessibility. It even states, under Help and About, that Firefox is meant to make the web accessible to everyone. I guess, that means except from old-timers with their WinEyes. Smiles and LOL. For some, Chrome might be an alternative. The rest of us, will be back to Internet Explorer. Chrome has its benefits, but so far I have had issues with it under certain operations. Following NVDA discussions lately, even that screen reader seem to have high issues with the newest firefox releases. It is being claimed, things will get better in version 58, but to what extent that will affect WinEyes, I am doubtful. And a recent note I read from VFO, on Jaws, seemed to indicate that even Jaws users are experiencing trouble with Mozilla lately. It was recommended not to use Firefox with Jaws 2018, if I remember correctly. Currently, I am not on that version of Jaws, so cannot confirm. Anyone here has had a chance to test newest releases of the screen reader and browser together? Goodbye to a long-lasting browser, which had numerous and beneficial advantages over any other products. Along with the somehow old-fashioned way of operating the web with Jaws - which to a degree reminds me of where WinEyes was a handful of years ago, the whole Internet browsing experience now seem to be a setback. Sure is going to take a bit of time, to get back to normal browsing speed. Sure, they made it secure? Didn't they. So secure you can't even use it. That is another kind of safety. Well, seems not even sighted users are comfortable with the newest moves from Mozilla. Probably why they tell the next release (58) will have some advancements. Does it remind you of what happened to things like Windows8, and the fact they had to go back on certain of the news, when releasing next versions? So maybe we should not wave totally goodbye to Mozilla all yet. I just wish they would have a setting somewhere, which would let the browser run the old way, even if they make some security adjustments behind the scene. Just wanted to let you know my findings. If anyone have ideas, I for one will be listening. For your info, I am under Win7 64bit, and the Firefox is reported as v52.5ESR 32bit. ___ 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/mbrown.brown4%40gmail.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/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listi
Firefox Again
A couple of weeks ago, we had the new Firefox breaking the accessibility under WinEyes. It is well known, from version 56 and up, Firefox will no longer operate with WinEyes. Someone kindly pointed us to the business - or ESR - version of firefox, at the time being version 52. I followed their advice, and installed it, greatly enjoying to have my Firefox back on stage. This morning, Firefox notified me there was a security update to my installation. In other words, no new version, just a maintenence update. Hence, I agreed to have it perform the update. Yeah, I take it, you have already guessed what. From now on, my Firefox says version 52.5, and is no longer doable with WinEyes. It no longer goes into the programs Main Window, but says Document Window. Here you can tab around, but the arrow keys produces no real effect, and browse mode is reported to be: Not Available. Oh, how I hate that message. Smiles. OK, if anyone have seen different behavior, or have got to a bit of knowledge on how to get Firefox back, we are all ears. To me, it seems Firefox simply has crept out of all cooperation with our screen reader. Little do I hold it realistic it will ever come back. Some place, I seem to recently have read, that someone from the NVDA team had gone to Mozilla. It then is strange that we are facing this kind of lack of accessibility. It even states, under Help and About, that Firefox is meant to make the web accessible to everyone. I guess, that means except from old-timers with their WinEyes. Smiles and LOL. For some, Chrome might be an alternative. The rest of us, will be back to Internet Explorer. Chrome has its benefits, but so far I have had issues with it under certain operations. Following NVDA discussions lately, even that screen reader seem to have high issues with the newest firefox releases. It is being claimed, things will get better in version 58, but to what extent that will affect WinEyes, I am doubtful. And a recent note I read from VFO, on Jaws, seemed to indicate that even Jaws users are experiencing trouble with Mozilla lately. It was recommended not to use Firefox with Jaws 2018, if I remember correctly. Currently, I am not on that version of Jaws, so cannot confirm. Anyone here has had a chance to test newest releases of the screen reader and browser together? Goodbye to a long-lasting browser, which had numerous and beneficial advantages over any other products. Along with the somehow old-fashioned way of operating the web with Jaws - which to a degree reminds me of where WinEyes was a handful of years ago, the whole Internet browsing experience now seem to be a setback. Sure is going to take a bit of time, to get back to normal browsing speed. Sure, they made it secure? Didn't they. So secure you can't even use it. That is another kind of safety. Well, seems not even sighted users are comfortable with the newest moves from Mozilla. Probably why they tell the next release (58) will have some advancements. Does it remind you of what happened to things like Windows8, and the fact they had to go back on certain of the news, when releasing next versions? So maybe we should not wave totally goodbye to Mozilla all yet. I just wish they would have a setting somewhere, which would let the browser run the old way, even if they make some security adjustments behind the scene. Just wanted to let you know my findings. If anyone have ideas, I for one will be listening. For your info, I am under Win7 64bit, and the Firefox is reported as v52.5ESR 32bit. ___ 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
Re: we9.2 and firefox again
FX is my primary browser and has been since FX 2 or three. - Original Message - From: net bat via Talk talk@lists.window-eyes.com To: via Talk talk@lists.window-eyes.com Sent: Tuesday, July 28, 2015 2:55 PM Subject: we9.2 and firefox again i feel firefox has been left out for w e bug fixes. am i the only one that uses firefox? windows 7 premium 64bit. before the browse mode re write i could do a search on ebay and i could read the entire line of results buy useing the header key h. or use a dollar sign with the w e find command to quickly find what i wanted and the price i wanted to pay for something. w e 9.2 is worse now then w e 9.1. useing the header key it reads the title of the auction only. then i have to right arrow to hear the price,buy it now,number of bids etc. on every item in the list. with the w e find command on ebay now w e quotes the price twice for every auction and if shipping is in the list it too is spoken twice. it does this with both the shift control f and the insert f find commands. There's amazing intelligence in the Universe. You can tell because none of them ever called Earth. ___ 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/bricemijares%40att.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
we9.2 and firefox again
i feel firefox has been left out for w e bug fixes. am i the only one that uses firefox? windows 7 premium 64bit. before the browse mode re write i could do a search on ebay and i could read the entire line of results buy useing the header key h. or use a dollar sign with the w e find command to quickly find what i wanted and the price i wanted to pay for something. w e 9.2 is worse now then w e 9.1. useing the header key it reads the title of the auction only. then i have to right arrow to hear the price,buy it now,number of bids etc. on every item in the list. with the w e find command on ebay now w e quotes the price twice for every auction and if shipping is in the list it too is spoken twice. it does this with both the shift control f and the insert f find commands. There's amazing intelligence in the Universe. You can tell because none of them ever called Earth. ___ 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
