Type following in Omnibar for version number: chrome://version
toggle quoted messageShow quoted text
On Sat, Mar 26, 2016 at 4:49 PM Gene <gsasner@...
My previous version was 49x it may have been
something like 49.9 and perhaps a few more numbers. I had the same
inability to use quick navigation keys in that version. My program updated
today when I was trying to get my version information. I couldn't get it
properly because such trivial information is no longer visible to
screen-readers, at least not the two I tested with, an older version of NVDA and
an older version of JAWS. I didn't test with a newer version of NVDA but I
doubt it matters. Whatever the newest general release version is, that
should be the one I have.
But don't worry. Evidently, things work
properly in Canary so one of these days, they will probably work properly one or
two versions from now. Then everything will be wonderful again until the
developers break something else, may be six or eight months from now.
I'm sorry, but I have no patience for companies
that profess a strong commitment to accessibility repeatedly and then don't
examine their browser to make sure they don't break things. And to make
matters worse, you don't have any control over updates. You can't turn off
----- Original Message -----
Sent: Saturday, March 26, 2016 4:28 PM
Subject: Re: [nvda] Google Chrome Settings
it’s the standard Chrome release that is causing me greif. I’m using
2016.1 on version 49 of Chrome. NVDA version 2015.4 worked fine with
Chrome version 48, so it would be helpful if you could confirm your Chrome and
NVDA versions and whether quick nav keys work in the settings page for you.
But you said you are
using Canary. I'm not. I believe Canary is many versions ahead of
what most users have. Maybe the developers corrected the problems being
discussed in later versions. That, in my opinion, really doesn't make
it alright for them to break things off and on in their rush to
Sent: Saturday, March 26,
2016 2:25 PM
Subject: Re: [nvda] Google
Settings, about, version, etc. are all accessible with NVDA
2016.1 for me
On Sat, Mar 26, 2016 at 12:19 PM Gene <gsasner@...>
I seem to recall
being able to use quick navigation keys awhile ago. This may be just one
more regression in the Chrome interface because, as I said, I couldn't use
them recently. that was with the same older version of NVDA.
I also found,
recently, that much of the about text was no longer accessible.
It looks as though
you will have to move through everything item by item, thanks to Chrome's
obsession with upgrading the browser frenetically and not having perhaps the
time or perhaps the staff to check to see if they have damaged or broken
accessibility. As I recall, I used to be able to use the search feature
in NVDA so I could move very quickly to something I already knew was on the
page. I couldn't the last time I tried. .
Sent: Saturday, March
26, 2016 2:00 PM
Subject: Re: [nvda] Google
you confirm the Crome version on that? I’m using Chrome version
49.0.2623.87 and when I load the Settings, NVDA lands me in a Search edit box
and even though i have got automatic focus mode for focus changes and
Caret movement checked in the NVDA Browse settings, focus and browse modes do
not engage and if invoked manually via NVDA+spacebar, Quick nav keys such as h
and d will still not work.
loaded Chrome Canary and the quick keys work fine on the settings page.
It’s driving me mad.
Chrome settings seems all accessible with quick-nav keys
Is anyone using Google Chrome and can they
confirm if the settings page is accessible using navigation quick
My chris.mullins4@... address will soon be
Please substitute this new address in your contacts