Re: NVDA 2019.3 beta 2 now available
toggle quoted messageShow quoted text
As part of NVDA’s UIA support, a set of bad UIA class names is kept to inform NVDA that windows with class names in that list should not be treated as UIA elements, thus forcing NVDA to switch to MSAA/IAccessible support. Even though UIA is used in Edge 79 Chromium-based), it is not that solid yet, so NVDA 2019.3 will force IAccessible2 mode, which works better (this is done by adding Chromium UIA widget window class name to the aforementioned set of bad UIA class names).
From: email@example.com <firstname.lastname@example.org> On Behalf Of Robert Kingett
I'm extremely confused. If the new Edge uses Chromium by default, how can NVDA work with Edge at all if that option has been removed from the NVDA settings? Darn you, Microsoft! Why couldn't you at least help JAWS, NVDA, etc. Build in UIA? This seems like a huge blunder on Microsoft's part, no? They have more man power, so either, help screen readers work with UIA, or disable it in the new Edge by default.