Along With NVDA I’m Also Now Using JAWS 2019. Here’s Why.

I had initially been a user of the JAWS screen reader since version 1.0 began shipping. I didn’t purchase it at that time but the product came out while I was working for Blazie Engineering in the 1990s. In addition to producing products such as the Braille ‘n Speak and Braille Lite, Blazie Engineering was also a distributor of many third-party products, such as screen readers and speech synthesizers, and the company had been selling JAWS for DOS when I first began working there. When JAWS for Windows, or JFW as it was sometimes called, began to ship Blazie received a copy right away. In January of 1995 I had to have my tonsils removed and was out of work because of this for two weeks. During those two weeks I had the pleasure of unboxing, installing and learning JFW 1.0 while I was recovering and really liked the software. After I left the company I bought my own license but I let it expire while running version 6. Later I began using NVDA and discovered that it was quite a nice screen reader. In the summer of 2009 I began using NVDA exclusively on my home computer and was very happy with it. It continues to offer some nice features and benefits not found in JAWS and, for my needs, I found it to be more than satisfactory.

During this time I was working as a trainer for Associated Services for the Blind where the agency kept their license of JAWS up to date. New versions of JAWS continued to be released and I kept up with what was added. When I left ASB and began working at Comcast as a member of their accessibility team I was able to continue using JAWS with a current license, which is always kept up to date.

As I continued to use and learn more about the newly added features introduced in each annual update I began to encounter features which JAWS had added but which were not available with NVDA. With products such as Office offering a subscription model with their Office 365 packages I really wanted to see Freedom Scientific offer a similar package to its users. With the release of JAWS 2019 FS (now part of Vispero, formerly VFO Group) announced that subscription packages would be available for some of their software packages, with JAWS being the first.

I was quite excited about this as I’d now be able to pay just $90.00 (a bit more with local sales tax) to immediately upgrade from my old license to a new, shiny JAWS 2019 license. This morning I visited Freedom Scientific’s E-store, found the page offering the JAWS annual license, placed it in my shopping cart and then completed my purchase. I immediately received two emails, one confirming my order and the other email containing a link for me to download and activate my software.

I went to the link and downloaded a tiny file which then allowed me to download and activate my software. I opened the program and, with no drama, JAWS was downloaded, installed and activated on my machine. The process was incredibly simple and, upon a restart, my desktop contained the JAWS 2019 icon to start my screen reader. As an added bonus, people who subscribe early as I did actually receive more than one year of use as my subscription officially expires on January 31, 2020, giving me almost fourteen months of actual use.

Now I’ll talk about why I actually decided to start using JAWS at home again. While I was always very happy with NVDA and will continue to recommend and endorse it there were some features and benefits which JAWS offers which are presently not found within NVDA which I really wanted on my home computer. Specifically, these features are:

  • The ability to copy a portion of a Web page into an email message with the formatting retained, including links and headings. I often repost various news articles and press releases to the mailing list for the Philadelphia Computer Users’ Group for the Blind and Visually Impaired. These articles usually contain links and headings which I’d prefer to have preserved in the email message. JAWS is able to preserve the formatting of portions of a Web page which are copied and then pasted into other documents or email messages. Currently, NVDA does not possess this capability. For a while I would use Window-Eyes as a backup screen reader to complete this task but this product is no longer in development. This was a decision made by VFO last year which I still strongly disagree with as it has diminished the screen reader landscape.
  • The ability for quick navigation keys to wrap. As an example, suppose that a Web page contains five headings and my virtual cursor is at the bottom of the page. With NVDA, pressing the letter H causes NVDA to inform me that no more headings exist on the page. This is, of course, correct. However, pressing the letter H using JAWS would cause the navigation to wrap back to the top, moving my focus onto the first heading. I believe this feature can be disabled for users who don’t want navigation to wrap but I found it to be a useful (though not a necessary) feature.
  • Responsiveness. Using Espeak, which is still my favorite synthesizer, NVDA is quite responsive. By responsive I’m referring to the delay between pressing a key and hearing the letter, number or character which was pressed. Even more important is the delay when pressing arrow keys to review a Web page, email message or a document. Again, in nearly all cases NVDA is pretty responsive when doing this when using Espeak. When I use the legally obtained drivers for Eloquence and Nuance voices (such as Tom and Samantha), the responsiveness improves even more, providing performance nearly as good as what you get with JAWS. Notice that I said “nearly.” When using NVDA with Eloquence or with Nuance the responsiveness is quite good and would be fast enough to satisfy nearly any speech user. However, if I’m going to be honest I have to say that the responsiveness with JAWS is just a bit snappier when reviewing a Web page with arrow key navigation. Is it significantly so? Not to me. It’s still somewhat noticeable. However, reviewing Word documents with NVDA, at least on my home computer, is a slightly different matter. The responsiveness when navigating using arrow keys is noticeably slower than what I see when performing the same commands in other programs. My work computer, which has far more RAM and more high-end specs, does not exhibit this type of delay. My admittedly slower Dell OptiPlex, with 8 GB of RAM, exhibits delays that I find annoying and, to be frank, unacceptable. When I compose documents using the open source Libreoffice Writer, performance is what it should be. Using JAWS 2019 on my home system the performance in Word, while still a tad bit slower compared to other programs, is quite good and definitely acceptable, making JAWS an attractive choice for me when using Word.
  • Text Analyzer. For me, this is one of the features which makes JAWS worth paying for. If I’m composing a document where correct formatting is not only desired but essential then I’d prefer to use JAWS with Microsoft Word. It allows me to easily track formatting changes and errors such as changes in font, color, mismatched spaces and other punctuation, etc. It’s very customizable and easy to use. NVDA currently does not offer this capability.

    If we’re going to compare the two screen readers to determine which one contains more features I feel that JAWS is the clear winner. It’s not worth debating; JAWS is, at the time of this writing, more feature-rich than NVDA. I’ve always known and accepted this. However, while I am not at all dissatisfied with NVDA the fact is that there are just a few features which it currently lacks that could really benefit me as a JAWS user. I’ll also say that NVDA continues to offer features which are not currently being offered in JAWS. Examples include:

  • Free of cost. This is pretty obvious. I’ll also admit that just because a piece of software is free doesn’t necessarily mean that it’s good. However, in the case of NVDA the screen reader, while lacking some of the more advanced features of JAWS, is still a very good and capable screen reader. This also means that subsequent updates, of which there are four per year, are also free of cost to the user. This means that there are no SMAs to pay for or keep track of.
  • It can be run portably. NVDA can be run from any folder on your hard drive without installing it. It can also be run from any external drive, such as a USB drive, in the same way. This means that you can take NVDA to just about any Windows machine and run it without the need to install it first.
  • Progress indication tones. This is something that NVDA has had since its early days. Window-Eyes eventually added this feature and it’s a feature that I wish JAWS would add. Essentially, if you’re performing a task such as downloading or copying a file JAWS is able to periodically read the progress in percentages, such as 20 percent, 40 percent, etc. When you hear JAWS say 100 percent then you know that the task is complete. This is fine and NVDA can do this as well. However, NVDA can also report this as ascending tones. Instead of hearing verbal announcements you hear quick tones which raise in pitch as the task nears completion. When the tone gets to its highest pitch then you know that the task is complete. Admittedly, this is not effective or helpful for users who are deaf or who have severe hearing difficulties. However, I have grown used to this feature and really wish JAWS would implement it. Now that I’m becoming more of a JAWS user I will suggest this to Vispero.
  • Works with Kaspersky. Those of you who don’t use or who want nothing to do with Kaspersky’s security tools won’t care about this. However, I use Kaspersky Antivirus and, while it doesn’t work perfectly with NVDA, it works reasonably well enough in that I am able to control the program. JAWS is, frankly, totally blind to any controls within the Kaspersky window, making it completely inaccessible to a JAWS user. This is another issue I want to bring to Vispero’s attention.
  • A more simplified interface. JAWS is running into the same problem that Windows 10 is now running into. Windows used to have all of their settings available via the Control Panel. Windows 10 still offers the Control Panel but now has their new Settings app with most features you’d want to access and change. However, some settings haven’t been migrated over into the Settings app yet and so you still need the Control Panel for some settings, although the Settings app does try to link to Control Panel items where it can. JAWS has a Settings Center, formerly known as Configuration Manager, where many of the JAWS settings are located. Like the Windows 10 Settings app you can even search for items that you’re looking for. However, like Windows 10 JAWS doesn’t have quite all of the settings you might be looking for contained within their Settings Center, such as changing voices or speech parameters, along with other settings. Instead, you need to open the JAWS window and open either the Options or Utilities menus for these items. By contrast, when you run NVDA you press insert-N for the NVDA menu, arrow down to Settings, press enter and all settings for the screen reader are available. To be fair, NVDA is a much newer and admittedly simpler screen reader and so you could argue that these two factors make the interface more manageable. JAWS has been around since 1995 and so they’ve had an additional eleven years to add extra features.
  • Pressing Home or End echoes the character at the cursor. When you use NVDA, pressing the Home key always speaks the first character on the current line, which I find very helpful. JAWS does this when using Microsoft Word but it doesn’t seem to do this in other applications and I think that it should. In fact, I can find no way of changing the behavior of the Home key unless you know scripting.

Many JAWS users will want to point out some feature of JAWS that I haven’t mentioned which is not available in NVDA. Of course, there are many but I’ve mentioned the ones which I would personally want to use. Placemarkers is a feature that I might wind up using but I have no real desire to use it but I may change my mind as I begin to use JAWS more at home. NVDA does actually have a Placemarkers addon but it’s not as intuitive or easy to use as it is with JAWS. Flexible Web is another JAWS-specific feature that I don’t feel a real need for but which I might use more often now that I’m once again a JAWS user at home.

I guess the real question is whether I will switch screen readers and use JAWS as my primary screen reader. My honest response, right now, is that I am not certain. However, even if I do switch over to being a JAWS user there will likely be tasks that I’ll still need NVDA to assist me with, such as accessing Kaspersky. In fact, it’s always good to keep at least two screen readers, along with several Web browsers, on your system, if possible, to deal with accessibility challenges or barriers that you might encounter where one combination of screen reader and browser might prove to be more effective than another. I will also continue to support and endorse NV Access, both with financial contributions as well as continuing to spread the word about their free and excellent screen reader.

For now I am enjoying the process of using and getting reacquainted with JAWS. I will continue to blog more about this as I continue this journey and would love to read your comments about this post.


Some Memories of Fred Noesner

I am sad to report of the recent death of Fred Noesner, who passed away on May 30. Many visually impaired consumers in Philadelphia may have remembered Fred as he worked for Associated Services for the Blind for many, many years. I believe he provided Optacon training in the 1970s and was known for starting Sense-Sations, a store located within the first floor of the agency selling both high-tech as well as lots of low-tech equipment. Fred was later transferred to many other departments within the agency and, for about a year was my supervisor when I first started at ASB’s computer technology center. Most of my memories of Fred, however, were when I wanted to buy adaptive products at the store, such as Braille paper, talking clocks or a replacement cane. Fred knew how to repair canes as well and this was always a welcome service, as all of us have had the experience of having our canes bent or otherwise damaged as a result of regular travel. He also wrote a book, a work of fiction called Fortunate Son, which I admit I have not yet read but it is available through NLS. Years after leaving ASB he worked for a while at an adaptive equipment store in Delaware and was a member of the Delaware Council of the Blind. He contributed years of service to the blindness community and I know that he will be greatly missed.
Here is a link to his obituary.

The Benefits of Assistive Technology Merging With Mainstream Technology

I am the moderator of the Philadelphia Computer Users’ Group for the Blind and Visually Impaired. On our mailing list I regularly post articles covering assistive technology. Not surprisingly, some of the articles that I post come from sites which specialize in this topic, such as news releases from producers of assistive technology hardware and software. However, many of these articles are being published by sources who, until recently, were known for covering the mainstream technology landscape. Articles like this bring out the fact that accessibility isn’t just limited to specialized or esoteric Web sites dealing with that particular topic. Several years ago, I found an article covering the accessibility features of the iPhone. I realized that this article came from IMore, which primarily reports on software and hardware from Apple. It was a weird feeling when I realized that this mainstream Web site was writing a piece covering accessibility and I eventually realized that accessibility was now being reported and documented on regular, mainstream sites which you wouldn’t have thought would cover this subject. Back in the day you had to access a specialized Web site, mailing list  or bulletin board group dealing with adaptive equipment if you had questions about how to use your screen reader or screen magnifier. Nowadays, manufacturers of computers and mobile devices are providing their own built-in assistive software, such as screen readers, screen magnifiers, support for switch devices, Bluetooth hearing aids, eye control devices, etc. The obvious benefit of this is that a user with a disability can purchase a smartphone and tablet and know that it will be accessible as soon as they take it out of the box. That’s not exactly news to us in the blindness community. However, there is another benefit to this in that it has allowed more users, including software developers and technology reporters, to become more aware of these tools since they are included in the product. This causes them, as well as their users and their readers, to become far more aware and knowledgeable when it comes to accessibility, thereby increasing the likelihood that more apps and services will become more accessible to us. Even if we find that a particular app presents accessibility challenges, we can write to the app developer, knowing that we probably won’t receive a response, such as “screen reader? What’s that?” since developers will already have some level of awareness about VoiceOver, Talkback or Narrator. It’s just one reason why having universal accessibility benefits everyone.

Opinion: Could the Amazon Echo Be Our Next Reading Machine?

With Amazon Echo devices which have a camera, such as the Echo Look or the Echo Show, there’s a capability which I think needs to be pursued which I’ve not heard anybody else mention. I’m talking about OCR. In plain English, this is the capability where you place a printed page on a scanner or in front of a camera and run a piece of software which is able to convert that picture of text into actual text which anybody can read or edit, including users who rely on screen readers. In Windows, we use programs such as OpenBook, Kurzweil 1000 or FineReader to perform these tasks for us. We’ve had these capabilities for decades. Recent advances with smartphones and tablets have given us the same capability with a more portable package, using apps such as KNFB Reader or the free Seeing AI app from Microsoft. Amazon is promoting their new Echo Look product as a sort of electronic fashion adviser. If this is all you’ll be able to do with the Echo Look’s camera then I feel we’ve missed a great opportunity to turn the Echo devices into the next print reading machine. Imagine if we had skills for the Echo devices, such as KNFB Reader, Seeing AI and other OCR apps. You could hold out a sheet of paper in front of your Echo’s camera and issue a command, such as “Alexa, ask KNFB Reader to read this for me.” The camera would take a picture and, within less than a minute, Alexa would read the page for you. Specially made stands, like the Fopito, could be manufactured and sold to allow a blind person to conveniently read one page after another of a book or magazine. True, you wouldn’t be able to edit the document on your Echo device but it would give blind people a quick and convenient way to at least hear the information on the page. If you had an Echo Show, Alexa could then allow that particular device to display that document on its screen, allowing you to review it using the built-in VoiceView screen reader. Additionally, you could issue commands to export that document to another location, such as being able to say “Alexa, send this to my OneDrive” or “Send this to my Dropbox”, allowing you to use your PC, phone or tablet to open and/or edit that file.

There are other scenarios which should also be possible, such as currency identification. Imagine how cool it would be to take a bill out of your wallet and say, “Alexa, identify this currency” or “Alexa, ask Seeing AI to identify my money.” The camera would snap a picture and Alexa would respond, “This is a five-dollar bill.”

I can also envision skills used to help us to identify objects. Imagine being able to hold a can of some unknown food items to your Echo’s camera and saying something like, “Alexa, ask TapTapSee about this object.”

Don’t get me wrong. I have nothing against having an Alexa device being used to take pictures of the various outfits which might be hanging up in your closet. However, it strikes me that a voice assistant with a camera could be used for so much more than that, which would tremendously serve both blind and sighted users alike. I would like to encourage software developers to consider writing such a skill, which so many people would benefit from.

How to Install the Google Play Store On An Amazon Fire Tablet

As my wife recently bought an Amazon HD 10, I have now acquired her sixth-generation HD 8. These are nice tablets, but Amazon does not, by default, have the Google Play store installed, instead preferring users to download apps directly from their own app store. This would be fine, except that Amazon’s app store doesn’t offer all of the apps available from the Google Play store, which I find annoying. There are a few methods for installing the Google Play store on a Fire tablet but I’ve found a rather simple method for doing this, which just involves a tiny bit of preparation beforehand on the tablet. What follows is a message I posted to the Visually Impaired Kindle discussion list about how to do this.
First, a few warnings. Amazon offers no support for any of this. Don’t think about calling them if you run into any issues or if you have questions. There is no guarantee that all apps from the Google Play Store will function properly on your Fire tablet, although most of them should. Finally, it’s possible that doing this could void your tablet’s warranty.

There are a few methods for installing the Google Play Store on a Fire tablet. The way that I’ve done this in the past was to run a file which, essentially, installs all 4 files at once, without the user needing to download and install each file one at a time. This tool has worked for me in the past but it did not work reliably on my HD 8 with Fire OS However, after doing some searching I found a similar tool from the same source, which worked.
First, here’s the instructions for how to do this.

Although the article advises that you extract the zip file into a specific folder, this is not necessary for just installing the Play Store.
The only preparation you need to do for your tablet is to enable a few settings in Developer Options within Settings/Device Options. However, if you go into Device Options you’ll see that Developer Options is not shown, as it’s hidden, by default.
To unhide Developer Options, go into Settings/Device Options.
Look for the serial number.
You’re supposed to tap it 7 times, which means that VoiceView users need to double-tap it seven times.
Once you do this, you should see a new tenth option called Developer Options.
If this still isn’t showing and if you only see nine options in Device Options, try double-tapping Serial Number 7 or more times again. Eventually, you’ll see Developer Options.
Double-tap Developer Options and look for the option USB Computer Connection. Double-tap this and set this for Camera, ptp.
Go back to the previous screen.
Next, look for Enable ADB, which will be off, by default. Double-tap to turn it on.
Next, run the tool. Here’s a direct link to it.

Extract the zip file to a place where you can easily find it.
Open the folder containing the files and you will see two folders.
The first folder is for the Mac, which you can ignore if you’re using Windows.
The second folder is the Supertool folder, which is what you want to open. Even though it has the phrase "fifth gen" in the title, I can tell you this worked on my sixth generation tablet.
Within this folder, look for the file called 1-Amazon-Fire-5th-gen.bat, which is what you want to run. Make sure the tablet is connected to your PC before you run this file.
Choose option 2 by pressing the number 2, followed by enter, which should, if all goes well, install the Google Play Store.
During the installation process, you may hear VoiceView say "Google Play Services error" several times but just ignore this.
Once the files are installed, it is recommended that you completely power off your tablet.
Once it’s powered back on, Google Play Store should appear in what is called the app grid (the list of apps) on your home screen.
At some point while downloading your first app, you will likely be prompted to update your Google Play Services, which you can safely do.
At this point, I would go back to Settings/Device Options/Developer Options and turn off ADB Debugging.
I would also recommend going into Developer Options and setting the USB connection to Media Device.

I hope this method will be of some help.