Is there a way to use Chromevox Next on the Mac?

[Parham Doustdar]

Hi,
I’ve been struggling with Google Docs on the Mac for a while now, and all the instructions for VoiceOver and Google Chrome seem to be for a long time ago, because Google Chrome and VoiceOver and Gooogle Docs don’t play nicely together any more.
So that’s why I started to look into ChromeVox, but everything seems to have moved to ChromeVox Next, and my previous confused messages to this mailing list haven’t gotten me any replies.
So, is there a way to use ChromeVox reliably in a way that works better than it already does on Google Chrome?
Thanks.

[Nimer Jaber]

Nope. But what issues are you having with VoiceOver? Maybe we can file some bugs.

Sent from my iPhone

> --
> You received this message because you are subscribed to the Google Groups "axs-chrome-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to axs-chrome-disc...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Parham Doustdar]

Well, for starters, pressing command+shift+z, which turns accessibility on and off, says nothing. VoiceOver does mention announce something like “Frame 1” and “Text” when I toggle it, but that’s it. It appears like the aria announcements that Google Docs uses to announce things isn’t working for some reason.

[Nimer Jaber]

What would be helpful would be to gather a list of all of these issues so that we can either look at the bug tracker to see if they have been reported, or to actually report them. I will have a play, and you can as well. As you run into issues, maybe post them on to this list. And or go onto the bug tracker and report them.

Sent from my iPhone

[Piotr Machacz]

Chrome’s accessibility implementation seems to be rather unoptimised with VoiceOver. For the most part it works, but it’s very easy for it to get bogged down and lag, especially when moving into objects containing other elements like frames or lists, and there’s quite a lot of lag when working with edit fields (for me it’s right now on average Half to a full second when moving by character or word, and word echo is completely broken.

When it comes to Live regions, a friend of mine just made a game in JS that uses a live region for speech which is both an electron app and available standalone at Cyclepath.dragonapps.org. On the Mac, for some reason the live region doesn’t initially work, it only does after you toggle VoiceOver off and back on. I just went onto Google Docs (Chrome Canary and Mac OS 10.13) and also initially had no speech, not even after clicking the “screen reader support” link that I found on the page. So I turned voiceOver off and back on, still initially got nothing, moved the VO cursor onto an “explore” pop-up button, hit escape which put me in the document I had open and then I finally had speech.

So, my suggestion would be to turn VO off and back on, it might very well fix your issue. Some issues will definitely have to be filed, outside of the fact Chrome should be a responsive web browser this lack of optimisation really hurts electron-based apps which are getting incredibly common. Most recently, the new Skype Preview just moved to Electron, and the experience on the Mac is that every time you move into a list, IE of messages in a chat, the application freezes for a few seconds with a “busy” message.

[Jason White]

Piotr Machacz <pite...@gmail.com> wrote:
> Chrome’s accessibility implementation seems to be rather unoptimised with
> VoiceOver. For the most part it works, but it’s very easy for it to get
> bogged down and lag, especially when moving into objects containing other
> elements like frames or lists, and there’s quite a lot of lag when working
> with edit fields (for me it’s right now on average Half to a full second
> when moving by character or word, and word echo is completely broken.

On the Mac, I generally run Chrome as my browser (with a few Web site-specific
exceptions). I'm not experiencing any of the issues taht you describe. I don't
know what the relevant differences are - but, for me, it's fast and
responsive.

I don't use Mac OS a lot currently; it's mostly Linux and Microsoft Windows at
the moment, for various reasons, including my work environment.

[Nimer Jaber]

Same.... I don't experience these issues with CHrome on the Mac either... in fact, I find the experience to be superior to Safari, which constantly says busy, busy, bloody busy.

Thanks.

--
You received this message because you are subscribed to the Google Groups "axs-chrome-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to axs-chrome-disc...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Cordially,

Nimer Jaber

My mission is to bring love and peace to everyone around me with all tools available to me.
My core values are integrity, innovation, loyalty, excellence, and 100% personal responsibility.

The message above is intended for the recipient to whom it was
addressed. If you believe that you are not the intended recipient,
please notify me via reply email and destroy all copies of this
correspondence. Action taken as a result of this email or its contents
by anyone other than the intended recipient(s) may result in civil or
criminal charges. I have checked this email and all corresponding
attachments for security threats. However, security of your machine is
up to you. Thanks.

Registered Linux User 529141.
http://counter.li.org/

To find out about a free and versatile screen reader for windows XP
and above, please click here:
http://www.nvda-project.org

You can follow @nimerjaber on Twitter for the latest technology news.

To contact me, you can reply to this email or you may call me at (218-606-0475) and I will do my best to respond to you promptly. Thank
you, and have a great day!