Hi Anatoliy, Agreeing on all of the points here. The HP navigation menu is a pretty nice example how not to design a menu. Also pretty interesting is the download center at times though i got around that now. I have read that the communication between browsers and screenreader is a pretty complex mechanism. Seems it doesn't like it when switching between screenreaders especially maybe when one api has not successfully unloaded or stays in use until the program that was heavily communicating over it was also closed to properly unload. though that could be just a idea. Am 13.04.2019 um 23:55 schrieb Anatoliy Shudrya:
Simon,
Real world stuff here. LOL. When things need to be done, I will jump to anything that will read screen to me. Believe it or not, but there is still tun of websites that won’t respond to JAWS or NVDA. Just one recent example from recent work experience.
I needed to find HPs point of sale section on their website. It would require me to browse through their navigation menu and find appropriate section. I use by default Firefox with JAWS, navigate to hp.com, jaws read top menu, but not the sub menu. I am stuck here. I turn off JAWS, start NVDA and use my mouse to try to use menu and sub menu to find appropriate section. Well, apparently, I find out that top menu is read by NVDA and the sub menu won’t be read by NVDA on Firefox browser. Well, I need to switch browsers now to somehow get to a place that I need to. It is just one very simple example why I constantly switch screen readers.
Second big example I was filling out an application for merchant account, everything seemed to be working fine with JAWS, but suddenly in the middle of application, it stops to read some elements, what am I supposed to do? Sighted help? Whip out my magnifier? Try Second screen reader? Of course, I would give a chance for NVDA and in 98% cases it helped, but it is almost impossible to go back to JAWS afterwards, it won’t be responsive.
I suppose I can give it a try and try to use NVDA as my primary one but that would be difficult since I used JAWS since the days of windows 95-98, JAWS 3.0 or 4.0.
I am not very technical with APIs/ bridges, it does not tell me much.
Sometimes I thought it might be because of my ancient home PC HP XW8600, but it happens on a new Z240 SFF Workstation as well.
Glen: I wouldn’t say it happens always; it always happens on the most important things I am doing online. LOL. A lot of times on the shopping cart forms, applications, I can’t come up with one right now, but I will keep an eye to spot something that can be replicated. JAWS 2019.1903.47
Kind Regards
Anatoliy
-----Original Message----- From: Simon Eigeldinger <simon.eigeldinger@vol.at> Sent: Saturday, April 13, 2019 1:41 PM To: blind-sysadmins@lists.hodgsonfamily.org Subject: [Blind-sysadmins] Re: JAWS is not responsive on the browser after using NVDA
Hi Anatoliy,
I use NVDA for some years now in the office and at home without any issues or accessibility problems. at least not that i would need to switch screenreaders.
i guess that constant switching of screenreaders doesn't do good to the browsers communication between the various APIs. So the browser doesn't know to which screenreader it should now talk to. because it talked a few seconds to one and a few secs later it should talk to a different one. Maybe some bridges haven't been unloaded and when the browser gets closed the dll can unload itself.
Greetings, Simon
Am 13.04.2019 um 22:06 schrieb Anatoliy Shudrya:
Hello everyone,
Probably not a sys admin topic, sorry. I have tried posting this to the JAWS list but maybe admins use different screen readers more often and can relate.
I have been long time user of JAWS and it seams to me that the problem that I experience started with the latest windows and latest browsers.
JAWS would stop reading anything on the browser after I make a switch from different screen reader such as NVDA. I am visually impaired and use both screen readers to navigate on the webpages. Sometimes NVDA would read things that JAWS won't and vice versa. So, for example in the middle of my cession on the web browser, I would decide to switch to NVDA, turn off JAWS, turn on NVDA, get my business done with NVDA and then turn on JAWS back again. After this series of steps JAWS would not read browser window no matter what, the only way to have JAWS read the browser window is to close it down and restart it. Many times it is impossible because I am in the middle of application fill out, purchase order or configuration page.
I have tried to refresh the page, using insert escape to no avail. Using tab won't help as well. Tried to turn off and turn on JAWS several times, still no luck.
Has anybody experienced similar kind of behavior with JAWS? Is there any trick getting it back to read?
I get this with Chrome, Internet Explore and Firefox. Latest Win 10 Pro. OS and latest browsers.
Also noticed that it happens often on the heavy coded pages with lots of JAWA code and forms.
Any help appreciated.
Anatoliy
_______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org
--- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.avast.... _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org
--- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus