Orca Screen-Reader Beats Chromevox When Reaching Pass 1200 Words

Although; Orca via Ubuntu via newer versions can really outperform Chromevox via Chrome OS Orca is easy to use and modify. You can really type away your work without slowing down. Google Chromevox via Chrome OS has these flaws what I’ve mentioned earlier. Despite Chromebooks with 4 GB of RAM or more… Chromevox still stall and stutters. Typically, screen-readers must be low in resources, and meet standards to use very less memory. Within this post; I’ll show these experiments as I use these screen-readers.


Orca is really a killer of performing when you write extremely long posts on your website, or working with code. However; Orca,,, named after a species of whale that is part of a dolphin family can really have a thrill of reading content, and using less resources. Right now; I have orca speak typed characters as a way to use less resources. Thanks to Orca; I can resume writing new posts on my website. However; I have 3 Linux machines that perform differently. For this instance, I am using my laptop to write web content from scratch.

With Orca; you can use a Chrome browser, and you can type up a storm, but Chrome is susceptible to crashes because, it relies on too much memory. Typically, I use FireFox to run my website, and write posts. As I use my Chromebook as a rig for viewing text-based games; Chromebox can read just fine, but Orca can read with no effort.

And speaking about orcas… that compares to a pod of 4 orcas attacking 4 moose that are attempting to swim to Russia.

In the future; Orca will be using very less memory, and Ubuntu will be faster than they used to be. And Unlike Chromevox, it can become a new king of all screen-readers.


Chromevox can read just fine. However; if you write content, and you reached over 1000 words; Chromevox uses up all of your available RAM,–causing your screen-reader to stall, or crash altogether. If this is the case; here’s what I’ve researched:

Chromevox has limitations

Chromevox has limitations when writing long posts on your website. As you write; your screen-reader uses more memory. If you reached a specific amount of words, you may experienced the following:

  • Stuttering – Your screen-reader may stutter and stall. This issue can really cause blind software developers to experience difficulties software.
  • Stalling – even you turn off character echo; your screen-reader still stalls and even stutter. This bug is kind of difficult to resolve. If you were attempting to write a very long post on your website in code; you may experience these difficulties when you write content for your viewers.


Crashes occur without actually knowing it! Chromevox itself has a “code erosion” of some sort. Memory gobbling apps, and other bloat inside Chromevox itself can reallyb cause our screen-reader in Chromebooks to faulter each day,–all without any proper fixes. Despite Chromevox is made by Google… it’s still proprietary software!

Orca can use less RAM

Orca is a RAM-saving screen-reader. and it doesn’t rely on cloud a s a dependency. This offline app is built for performance, and reliability.

If you think Chromevox has flaws, you may need to use a different PC with Ubuntu Installed.

Orca is really a winner of handling long posts without crashing. However; Chromevox stalls and crashes when handling long osts.

To perform this experiment

Turn On Chromevox on your Chromebook and write long posts on your website in code mode.

Turn On Orca on your Ubuntu Machine, and do the same way as you write long posts on your website.

Compare how these machine perform.

If Chromevox stall and stutters, most likely Chromevox is defective, and it needs to be reworked.

How many of you experienced Chromevox stalling and Orca beating Chromevox?

Leave a Reply

Your email address will not be published. Required fields are marked *

44 − = thirty nine