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.

Continue reading “Orca Screen-Reader Beats Chromevox When Reaching Pass 1200 Words”

Chromevox Magic: Use Search-M to open acontext menu when using CPanel via GreenGeeks

You still don’t wondering you still have trouble opening a file on your CPanel via your hosting account via GreenGeeks.

There’s no trusted visual person available for you to enable you to work with this interface via this control panel.

However, there’s a magic trick to go around this issue. That applies to using a newer version of Chromevox on a Chromebook.

Continue reading “Chromevox Magic: Use Search-M to open acontext menu when using CPanel via GreenGeeks”

Chromevox Next Is Now A Default Version Of Chromevox… But Classic Chromevox Is Breaking Down

Many people who toggle between Classic, and the newer version of Chromevox to use both version for common applications, and activities. For this instance; you use Classic Chromevox for web development, or adjusting an online vault on your Walmart debit card. However; what you’re about to encounter… is these following issues what you never struck before.

The Experiment With Classic Chromevox

If you switch back to the Classic version of Chromevox, and you opened your browser tab, and go to your favorite social networking accounts what you use via any social media site; you used your arrow keys to navigate Chromevox; there’s no feedback when you try to use Classic Chromevox. I tried clearing out some cache, images, files, and other junk from my browser,–along with turning off some of these extensions and apps to free up memory on my Acer C7 Chromebook. I had this 5 year-old Chromebook still working like normal. But overtime; Chromevox Classic begins to have a software rot,–meaning the code becomes corrupted, and it takes up more memory than any other software.

I worked around the issue by using Chromevox Next first…. and toggling different versions to ensure Chromevox is doing its job.

If you want Chromevox to announce the URL behind the link; you need to use Chromevox Classic,–rather than Chromevox Next because, the newer version of Chromevox doesn’t have this feature,–making it too difficult to varify if any of these links are valid URLs. If the newer version of Chromevox has this feature, that will make it easier for blind users to spot suspicious links that are linked to malware. This is pretty scary if you were a web developer who is good at writing code, and protecting your website from serious harm.

Problems What I Found With Details:

  • Chromevox is NOT reading webpages when the page is done loading. No feedback when Chromevox Classic returns focus to the inside of webpages.
  • Chromevox is NOT capable of keeping resource usage at low amount of memory.
  • Stalling Points.

Chromevox Next Gets Improved when newer versions of Chrome OS are released

If you use Chromevox Next; and you were about to write documents, or long posts; you may still experience stalling, and crashing when you write extremely long codes that are built to run your plugins on your website, you may need to change out memory on your Chromebook, or use a Linux machine to develop your website even further. Not all screen-readers are equal, some interact with web elements differently. However; Chromevox still have these flaws that are indeed getting worse overtime.

What makes it really difficult with Chromevox Next is a missing feature; use a mouse to change focus, for blind users who prefer to use a mouse to navigate with Chromevox. Common uses with this mouse are other functions what Chromevox isn’t able to perform. That simulates a visual person who wanted to rely on this instrument. NVDA,–this screen-reader only available to Windows machines… hasn’t been arriving to the Chrome OS platform at this time. If Chromevox has a feature, work like NVDA, that will be easier for a Chromebook user. You can visit NVDA’s website and find out more about this open-source screen-reader. If Chromevox developers has integrated NVDA mode for their screen-reader,–it will NOT take up more memory.

Overtime; in the future; Chromevox Next will be better than ever; if any of these flaws has been fixed. Since a long time ago; Chromevox was performing without any trouble since Chrome 24, and below, this the best of Chromevox when I had my first Chromebook as a way to keep Windows out of my system. And I left Windows out of use.

Common Problems With Chromevox Next

Like Chromevox Classic… it still stall or stutters when you write an extremely long content what you were just writing on your website, or posting comments anywhere on a website. These text fields play an important role for blind webmasters who were serious about creating something new,–especially new WordPress Plugins, software code, website templates, etc.

  • URLs can’t be announced behind links.
  • Interactive elements can’t be activated when using features found on websites,–such as Walmart Debit card online vault.
  • Still take up lots of memory.

If you found new Issues with Chromevox, you can always file a bug with your Chromebook.

Update: Chromevox Still Stalls & Stutters When Writing Posts With Over 5700 Words

Okay… I experimented with writing and editing a post on my website. I managed to reach up to 5700 words on my post via WordPress,–editing stories. This is the another issue what Chromevox developers didn’t say to us. You thought Chromevox is getting better… but this is a sign of false-advertising.

Continue reading “Update: Chromevox Still Stalls & Stutters When Writing Posts With Over 5700 Words”