Re: FW: [win10] Edge 79: if your screen reader is having trouble working with web content shown in Edge...
toggle quoted messageShow quoted text
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 later.
From: email@example.com <firstname.lastname@example.org> On Behalf Of Cohn, Jonathan
Sent: Monday, January 13, 2020 7:09 AM
Subject: Re: [nvda] 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?
From: email@example.com <firstname.lastname@example.org>
External 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 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:
Screen reader specifics: