Today is the day. I've switched my default browser from Safari to Chrome.
It will be a bumpy transition. But as we all know after the past several years, staying on Safari is also bumpy. And I think I'm being kind when I describe Safari as bumpy.
Here are two immediate improvements I've already noticed.
One, when I land on the AppleVis main page and click log in, both the username and password fields show up on the VO+U web rotor list of form fields. Pretty amazing, huh?
Two, as I compose this post, if I arrow up and down through the text, VoiceOver does not randomly decide to read my entire post from the beginning. Another remarkable technological advance that Safari is simply unable to pull off.
I think we've all been more than fair and patient. But after the agony I went through yesterday working with the ISBN database, right on top of my discovery that the Wordpress block editor is unusable with current Safari, I've finally reached my breaking point. For those of you still using Safari on MacOS, I wish you good luck. You're going to need it.
Comments
Verbosity is weird
I noticed a while ago that on applevis, in the comment headings for example VO would say level 2 only on chrome. For whatever reason it's linked with the verbosity setting of status for the link item, turning this off remove this announcement b but then you are also unable to know if a link is visited or not. I still don't know what type is for.
My guess is that on chrome when there is a link in a heading, it would mark this content as in another content, thus level 2. Could be related to the annoying bug of VO only reading heading 3 3 items instead of reading those like it was doing before.
Re: clickable
I read your comment above and launched Chrome and went to About. When I moved around I was hearing Clickable but it updated and I relaunched... and now... so far, no clickables. I will be very, very happy if that has been fixed. I think Chrome is always updating in the background, so I suspect that is what happened to you.
Yeah so my guess was right…
Yeah so my guess was right it was a, chromium issue.
The clickable thing
It is resolved after the update here as well.
Maybe Chrome is trying to keep me
Happy to see that the clickable issue is gone.