- FW: [win10] Edge 79: if your screen reader is having trouble working with web content shown in Edge...
Re: FW: [win10] Edge 79: if your screen reader is having trouble working with web content shown in Edge...
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?
Date: Monday, January 13, 2020 at 1:25 AM
To: firstname.lastname@example.org <email@example.com>
Subject: [nvda] FW: [win10] Edge 79: if your screen reader is having trouble working with web content shown in Edge...
External email alert: Be wary of links & attachments.
From: firstname.lastname@example.org <email@example.com>
On Behalf Of Joseph Lee via Groups.Io
Sent: Sunday, January 12, 2020 10:25 PM
Subject: [win10] Edge 79: if your screen reader is having trouble working with web content shown in Edge... #ChromiumEdge
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 yet.
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 Edge 79:
- Start new Microsoft Edge (not the old one).
- From 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 TYPING FLAGS!).
- Go to “Native UI Automation” combo box and select “disabled”.
- Press Tab to go to “Restart” button and click it.
Screen reader specifics:
- Narrator: supports native UI Automation
- JAWS: works better with native UI Automation off
- NVDA: works better with UI Automation off and a fix is being developed
- Other screen readers: contact vendors
Join firstname.lastname@example.org to automatically receive all group messages.