Many people who are blind rely on SSI funds to help themselves pay for utilities, purchase food, pay for online services, and other uses. But some payees who were helping blind website owners often steal their SSI funds! It’s illegal to misuse anyone’s SSI funds for other purposes that are NOT intended for. Well, it did happened to me. And the Independent Connection Services has to help me get out of the abusive situation. This can happen to any blind person who owns a website via a web-hosting service, or domain ownership. However; this can be your worse nightmare,–if your funds were stolen.
Recently; I was waiting for Draft2Digital to implement more accessible controls that are easy to use. However; the vendor selector has been changed so far, and the publishing wizard has been changed, and the edit boxes are accessible. But the “Rights Confirmation” section is NOT accessible for the blind. This section is really important for the blind person to operate because, if the section is NOT accessible… bad things will occur. Since I don’t have any screenshots to show you what’s exactly happening.
Many blind webmasters don’t want sexualized content on their websites. This is usual for some people who don’t want sexual content on their servers. Almost all of these website owners who were blind often host free platforms to enable users to create websites for free… all without traditional payment that goes first. However; blind webmasters are so concerned if porn has been spreading around their website,–all without any special software to keep pornography out of their website. This is kind of scary if you are blind, and you don’t know what image is being displayed on your website.
I experimented on a screen-reader on my Android phone, TalkBack. I logged into my Draft2Digital account to navigate around the interface, such as “Advanced Settings” and varify if these controls are accessible. But I discovered something that is NOT right! Like Chromevox, this screen-reader can’t locate checkboxes because, these elements on Draft2Digital’s website itself isn’t designed to be screen-reader accessible.
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.