Re: curious about today's update for JAWS 2018
toggle quoted messageShow quoted text
We’re still in 2018. I don’t know what the cut-off point is, but it’s somewhat over a year from the previous JAWS release. It was promised that jAWS 2018 would work with Firefox Quantum; until now it’s been almost-but-not-quite-there, as many people (including me) have been experiencing persistent crashes. I believe they have addressed the issue in this update (I hope so, still testing), thus keeping their promise. I don’t know what else has been fixed, but I suspect this will be close to the last JAWS 2018 update.
From: firstname.lastname@example.org <email@example.com> On Behalf Of Dean Martineau
Sent: November 16, 2018 10:22 AM
Subject: Re: curious about today's update for JAWS 2018
People tend to complain about the JAWS company, whatever name it goes by, for their upgrade policies. (Nobody has done so here at present.) So they have annual upgrades, but still make some efforts to maintain the experience of those who, for whatever reason, don’t or can’t upgrade. So it is with this upgrade to 2018.
Thought-provoking reading: http://bahaiteachings.org
The purpose is to improve the experience for people who are still using Jaws 2018 because they have for some reason not yet upgraded. This could be because they don't have an SMA left and currently can't afford or don't want to buy one or maybe they work at larger organisations where often such updates take longer. One of my best friends in Germany used to work at HP and each time he needed an update he had to go through a big application process to get HP to authorize it.
I don’t remember ever getting an update the same month a new version of JAWS has been released. What’s up? Does anyone know the purpose of this update? In other words, what did it fix?