toggle quoted messageShow quoted text
Its worth noting that I have never had any uia issues with chrome
standard however in edge thats another animal.
Also of interest, shortcuts to online office programs seem to
have got added to the menus as part of edge.
Not sure if these are online or what but it took me a bit to kill
Lets hope that now chrome and microsoft and others are in direct
competition that we can actually see all sides step up just that
little bit higher.
On 14/01/2020 5:13 am, Joseph Lee
This mostly concerns browsers, and Slack
might be affected if accessed from the web.
An important update: the workaround I
described earlier no longer applies if using NVDA 2019.3 or
Any idea if Microsoft Teams app or Slack
are effected by this transition to UIA?
For that matter, is there a way to check
for apps like these that are using Chromium as their base?
email alert: Be wary of links & attachments.
Someone reported on JFW list (hosted on
Groups.IO) that the user cannot interact with certain web
content displayed in Edge 79 beta, along with a thread on
Win10 forum about inability to interact with web content
shown in Edge with other screen readers. This issue can be
traced to the fact that, in Edge 79 (upcoming stable
version), UI Automation is enabled (several reports were
sent to Microsoft about this issue). Unfortunately, as an
NVDA core developer (not me) notes, UIA implementation in
Chromium-based web browsers (including Edge) isn’t solid
To work around this for now, you need to
disable UIA support in Edge and other Chromium-based web
browsers (if your browser exposes this option). To do so in
- Start new
Microsoft Edge (not the old one).
address omnibox (Alt+D), type “edge://flags” (without
quotes and as exactly as shown) and press Enter.
- Type “UI
Automation” into “search flags” and press Tab to move
through resulting content (no, DO NOT PRESS ENTER AFTER
- Go to
“Native UI Automation” combo box and select “disabled”.
- Press Tab
to go to “Restart” button and click it.
Screen reader specifics:
supports native UI Automation
works better with native UI Automation off
works better with UI Automation off and a fix is being
screen readers: contact vendors