Potential NVDA issue with Google Chrome
Chris Mullins
About the same time as I updated NVDA from 2015.4 to 2016.1, Google Chrome was updated from version 48 to 49. I am now experiencing problems accessing the the Google Settings page and I’m struggling to determine if it’s a NVDA or Chrome problem. Note in my NVDA Browse Mode settings, ‘Automatic Focus Mode for focus changes’ and ‘Automatic Focus Mode for Caret movement’ are both checked. This is the problem:
Press the alt key, then press spacebar to open the Chrome menu, then press the s key to open the Google settings. The page opens, NVDA makes the camera sound indicating Focus Mode and focus is in a settings search edit box. Tab or arrow out of the edit box, NVDA does not make the Clang sound indicating Browse mode. Press NVDA key+space to manually enter Browse mode None of the browsing quick keys like h or d work even though I know these items exist on the page.
I’m leaning toward it being a Chrome issue rather than NVDA because standard web pages work fine. When I used NVDA 2015.4 with Chrome 48 the Settings page was very accessible but things have drastically altered. Is there anyone with version 48 of Chrome who can verify that Focus/Browse modes operate as designed and the Browser quick keys operate properly in the Google Settings page?
Cheers Chris
|
|
Gene
It sounds like typical Chrome inattention to
accessibility. They seem to break something every number of months.
I was recently upgraded to a version of Chrome in which the about page is not
properly accessible. I can't read a lot of the information. This
sounds like an expansion of the same sort of problem. I really doubt that
this is a screen-reader problem.
Gene
From: Chris Mullins
Sent: Saturday, March 19, 2016 8:25 PM
To: nvda@groups.io
Subject: [nvda] Potential NVDA issue with Google
Chrome About the same time as I updated NVDA from 2015.4 to 2016.1, Google Chrome was updated from version 48 to 49. I am now experiencing problems accessing the the Google Settings page and I’m struggling to determine if it’s a NVDA or Chrome problem. Note in my NVDA Browse Mode settings, ‘Automatic Focus Mode for focus changes’ and ‘Automatic Focus Mode for Caret movement’ are both checked. This is the problem:
Press the alt key, then press spacebar to open the Chrome menu, then press the s key to open the Google settings. The page opens, NVDA makes the camera sound indicating Focus Mode and focus is in a settings search edit box. Tab or arrow out of the edit box, NVDA does not make the Clang sound indicating Browse mode. Press NVDA key+space to manually enter Browse mode None of the browsing quick keys like h or d work even though I know these items exist on the page.
I’m leaning toward it being a Chrome issue rather than NVDA because standard web pages work fine. When I used NVDA 2015.4 with Chrome 48 the Settings page was very accessible but things have drastically altered. Is there anyone with version 48 of Chrome who can verify that Focus/Browse modes operate as designed and the Browser quick keys operate properly in the Google Settings page?
Cheers Chris
|
|
Kevin Chao
It may be fixed in Chrome Canary: For direct access to settings and about (type following into omnibar): chrome://settings and chrome://about
On Sat, Mar 19, 2016 at 6:33 PM Gene <gsasner@...> wrote:
|
|
Scott VanDeWalle
Well, I can access the settings pretty well, but here is an odd
issue.
toggle quoted messageShow quoted text
I use chicken nugget, and when trying to open a link from chicken nugget, when chrome launches, nothing reads, however if i copy from the address bar the address of the website to my clipboard, then load the page in chrome manually from the address bar after restarting chrome, the page works spectacularly. \I hope you got all that smile. If not let me know But i can do settings pretty good, but yes, the about thingie seems a bit funky. Scott
On 3/19/2016 9:33 PM, Gene wrote:
|
|
Kevin Chao
Does same happen when opening link from a win32 app? i.e. can you open links from your email client, word processor, etc.?
On Sat, Mar 19, 2016 at 7:34 PM Scott VanDeWalle <scottvandewalle2@...> wrote:
|
|