#Chrome updated, and now:
* I have to restart #NVDA every single time I launch the browser, otherwise it refuses to read anything in the Chrome window.
* Someone wrapped a bunch of the UI in a landmark region, the name of which includes: the name of the current page, the name of the browser, and the name of the current Chrome profile. NVDA speaks this region's name and role whenever I move focus from the page document to the address bar. E.g. "Some Page Title - Google Chrome - James (<my email address>)".
* When Alt+Tabbing into Chrome, the word "window" is now spoken by NVDA after the window title.
#Google #accessibility strikes again.
This entry was edited (1 week ago)
@jscholes I wonder if any of these issues go away if you explicitly turn off UIA for chromium in NVDA advanced settings. The sounds suggest that's what's happening
in reply to James Scholes
Oddly, I set "Use UIA with Microsoft Edge and other Chromium based browsers when available" to "No", but NVDA's developer info still shows UIA-related attributes for the wordy landmark region I mentioned in my issues list. So I'm wondering if that advanced UIA setting only applies to webpages in browsers, not browser windows as a whole.
in reply to James Scholes
Although... I made a new app module for Chrome, and marked the entire window as bad UIA. And now most of the issues have disappeared.
in reply to James Scholes
Good to know, I bookmarked your addon for the moment when someone inevitably tells me Chrome is broken or I need it for something.
James Scholes
in reply to James Scholes • • •I just submitted the following #Chrome #accessibility bugs, relating to using the latest update with #NVDA, to #Google:
1. I have to restart NVDA every single time I launch the browser, otherwise it refuses to read anything in the Chrome window. I.e. Chrome is not running. I launch it, NVDA doesn't read anything. I restart NVDA, and it works again, until I next close and restart Chrome.
2. A bunch of the UI has been wrapped in a landmark region, the name of which includes: the name of the current page, the name of the browser, and the name of the current Chrome profile. NVDA speaks this region's name and role whenever I move focus from the page document to the address bar, or to other parts of the UI like the menu button by pressing Alt. E.g. "Some Page Title - Google Chrome - James (<my email address>) region".
3. When Alt+Tabbing into Chrome, the word "window" is now spoken by NVDA after the window title, where it wasn't before.
4. While focused on the "Chrome" menu button after pressing Alt, the first press of Up or Down Arrow expands the menu as expected, but doesn't move focus onto the last or first item respectively. The same applies when pressing Space or Enter to expand the menu while focused on the button.
5. Within the Chrome menu, items that have an attached sub-menu do not convey this fact to the screen reader. E.g. NVDA only announces "Help e 19 of 22".
6. The Chrome menu can no longer be opened with Alt+F.
7. When using first-letter navigation to move to a sub-menu within the Chrome menu, where there is only one match for the letter typed, focus doesn't move into the sub-menu when it is expanded. E.g. open the Chrome menu, and press L. NVDA announces, "More tools l 18 of 22", but when I press Down Arrow, it says: "Name window… 1 of 5".
James Scholes
in reply to James Scholes • • •Most of the #Chrome #accessibility issues in my previous post are caused by Microsoft's UI Automation (UIA) API. If you want an #NVDA add-on to completely disable UIA in Chrome windows, here you go:
dropbox.com/scl/fi/sktapipwilh…