Re: Safari Annoyance in Latest Build

On 5 Apr 2016, at 03:01, Kevin Chao wrote: > On Mon, Apr 4, 2016 at 6:21 AM Sabahattin Gucukoglu wrote: >> Well, to be fair, ChromeVox would be a better extension if it could actually >> announce the chrome in Chrome. > > It's built using web technology (HTML5/JavaScript) and content scripts ar

Re: Safari Annoyance in Latest Build

On Mon, Apr 4, 2016 at 6:24 PM Michael Marshall wrote: > try navigating to a heading with quicknav in crome, > Which Mac OS X and Chrome version? quick-nav, web rotor, web spots, and heading nav works here for me with Chrome+VoiceOver. > you can't move once you get to it. > the only way you can

Re: Safari Annoyance in Latest Build

On Mon, Apr 4, 2016 at 9:48 AM Seyoon Choi wrote: > I switch back and forth between Chrome and Safari simply because I need to > use Google Chrome for using any Google apps, drive, docs. These apps seem > to work a lot better on Chrome. But the only thing that Chrome is not > accessible with is w

Re: Safari Annoyance in Latest Build

On Mon, Apr 4, 2016 at 9:46 AM John Panarese wrote: >I’ve found that VoiceOver functionality in Safari does not work > consistently in Chrome. Sometimes, it works as expected, but other times, > it simply doesn’t. > Do you have specific examples? It'd be great to see if this has been fixed i

Re: Safari Annoyance in Latest Build

On Mon, Apr 4, 2016 at 8:21 AM Brian Fischler wrote: > Hi Kevin, > > Thanks for your input about chrome. My only hesitation to using chrome is > the site that I go to daily works fantastic with my personal web spots, and > I do not think you can create web spots in chrome. I use auto and persona

Re: Safari Annoyance in Latest Build

On Mon, Apr 4, 2016 at 6:21 AM Sabahattin Gucukoglu wrote: > Well, to be fair, ChromeVox would be a better extension if it could > actually announce the chrome in Chrome. It's built using web technology (HTML5/JavaScript) and content scripts are injected to each page, so this was done by design.

Re: Safari Annoyance in Latest Build

the one site that is shocking because it keeps changing so much is facebook. you can not tag with VO even on the main site i have discovered. > On 5 Apr 2016, at 2:48 AM, Seyoon Choi wrote: > > I switch back and forth between Chrome and Safari simply because I need to > use Google Chrome for usi

Re: Safari Annoyance in Latest Build

try navigating to a heading with quicknav in crome, you can't move once you get to it. the only way you can get around crome is using tab from my experience. since firefox do not cair about mac accessibility i still think Safari is the way to go. > On 5 Apr 2016, at 2:48 AM, Seyoon Choi wrote: >

Re: Safari Annoyance in Latest Build

I switch back and forth between Chrome and Safari simply because I need to use Google Chrome for using any Google apps, drive, docs. These apps seem to work a lot better on Chrome. But the only thing that Chrome is not accessible with is when you have to login to your google account. Seyoon Cho

Re: Safari Annoyance in Latest Build

I’ve found that VoiceOver functionality in Safari does not work consistently in Chrome. Sometimes, it works as expected, but other times, it simply doesn’t. I guess you can try your site and see what happens, but I’ll personally stick with Safari. Take Care John D. Panarese Director Mac fo

Re: Safari Annoyance in Latest Build

Hi Kevin, Thanks for your input about chrome. My only hesitation to using chrome is the site that I go to daily works fantastic with my personal web spots, and I do not think you can create web spots in chrome. Would love to hear if I am wrong. Not sure why Apple did away with enter performing

Re: Safari Annoyance in Latest Build

Well, to be fair, ChromeVox would be a better extension if it could actually announce the chrome in Chrome. You’d have to leave aside the fact that using a dedicated screen reader just for your web browser was kind of crazy to start with, but it’s basically the reality on ChromeBooks. -- The

Re: Safari Annoyance in Latest Build

On Sun, Apr 3, 2016 at 1:33 PM Anders Holmberg wrote: > Hi! > THere must have been a lot of updating since i last used chrome so i take > back evrything i said. > Curious, when ndid you last use it? Chrome has been great with VoiceOver for a while. > It seems to work as smooth as expected. > Gre

Re: Safari Annoyance in Latest Build

Hi! THere must have been a lot of updating since i last used chrome so i take back evrything i said. It seems to work as smooth as expected. Nice because i like chrome very much. Does it have a reader like in safari? /A > On 03 Apr 2016, at 22:16, Kevin Chao wrote: > > > > On Sun, Apr 3, 2016

Re: Safari Annoyance in Latest Build

On Sun, Apr 3, 2016 at 1:11 PM Anders Holmberg wrote: > Hi! > Exept from that its stuck after each list view > Hmmm...Is there a site or example of where this can be observed? > and you have to press tab after each list view to get things working again. > Which Mac OS X and Chrome version? Hope

Re: Safari Annoyance in Latest Build

Hi! Exept from that its stuck after each list view and you have to press tab after each list view to get things working again. /A > On 02 Apr 2016, at 23:46, Kevin Chao wrote: > > I've been using Chrome and it works great. > > On Thu, Mar 31, 2016 at 11:19 AM Brian Fischler

Re: Safari Annoyance in Latest Build

On Sun, Apr 3, 2016 at 6:48 AM Devin Prater wrote: > I hate that Chromevox can't access the chrome menues > ChromeVox is intended for the HTML content, so VoiceOver works for chrome of chrome (e.g. menus, omnibar, etc.) > though. Really makes Chrome hard for me. > It's possible to fully use Voic

Re: Safari Annoyance in Latest Build

I hate that Chromevox can't access the chrome menues though. Really makes Chrome hard for me. Add to that that every time I launch it Chrmovox starts a loop of wrapping to top sounds, and yeah, Chrome is unusable. Sent from my iPhone > On Apr 2, 2016, at 4:46 PM, Kevin Chao wrote: > > I've b

Re: Safari Annoyance in Latest Build

I've been using Chrome and it works great. On Thu, Mar 31, 2016 at 11:19 AM Brian Fischler wrote: > I am still running Yosemite and running the latest build of safari and > wanted to see if anyone else noticed this. I use a website every day where > I will get a pop up to perform another action.