I have been using Chase and WE for a long time with no problem. But with the new beta I had a problem, I was getting a blank screen after logging on, chase said I was logged on when I called customer service. I did everything I was told and nothing fixed the problem. Finely I reset IE and everything started to work right again. I don't know if WE caused the change in IE or if it was just a coincidence. However in Firefox, I could just type in the URL for Chase and Firefox would crash. GWMicro was able to duplicate this and are working on a fix. ----- Original Message ----- From: Rick Thomas To: 'Loy' Sent: Sunday, November 30, 2014 3:18 AM Subject: RE: WE beta and Chase.com
Hi: As you noted I have used chase for years and it still works with WE 8.4 or whatever level I have - version prior to 9. For me it is not an option whether I can access my bank or brokerage accounts - it just flat out has to work. It is rather unnerving that there is the comment on the J.P. Morgan / Chase site that WindowEyes may not work with their platform. It is incumbent on the WindowEyes staff to ensure that the bank site works with their screen reader me thinks and that the bank pulls that warning against using WindowEyes. If you wat one piece of huge anti-quality publicity have J.P. Morgan / Chase or other financial world leaders put an explicit warning against using your product on their home page! Call Chase and see if they have an alternate logon page. A while back we would roll over the speak spanish link and trigger the site to be the Spanish Language version. There was no way I could get it to stay in English, not searching for text, tabbing or arrowing to content on the page. Chase gave me another url to use to log into their site and it worked. I think they, Chase, have found a fix since I can log onto Chase now using the standard logon url without getting Spanish but I think Chase fixed the problem rather than WindowEyes. Anyway, keep prodding the staff at WE to ensure their product works with Chase and any other sites peoples family security or finances are involved on list. Getting at your Bank information, or brokerage information or government websites should not be optional in my opinion but rather a necessary feature. Health Care is another area where accessibility should be a slam-dunk up front. Rick USA From: Loy [mailto:[email protected]] Sent: Tuesday, November 25, 2014 3:25 PM To: GW-info Subject: WE beta and Chase.com I am beginning to believe that the beta is causing the problem with the Chase.com site. I go to chase.com, I enter my User ID and Password and log in. and a blank screen comes up. According to Chase Internet customer service they say I am susseccfully logged on. but the screen is blank. I did a system restore to a time before I installed the beta and the site worked as it should. Then I reinstall the WE Beta and the Problem is back. Win 7 and IE 10. I had also deleted all Internet History and temp files. Internet files.and rand Spybot and malware bites. I am very frustrated. I need this site to work. "For God sent not his Son into the world to condemn the world; but that the world through Him might be saved." John 3:17 If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
