windos 7 will soon stop being supporting by Microsoft u need 2 get
toggle quoted messageShow quoted text
windos 10 and hier after Janurary 14 2019
On 1/13/20, Joseph Lee <@joslee
From: firstname.lastname@example.org <email@example.com> On Behalf Of Joseph Lee
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:
1. Start new Microsoft Edge (not the old one).
2. From address omnibox (Alt+D), type "edge://flags" (without quotes
and as exactly as shown) and press Enter.
3. Type "UI Automation" into "search flags" and press Tab to move
through resulting content (no, DO NOT PRESS ENTER AFTER TYPING FLAGS!).
4. Go to "Native UI Automation" combo box and select "disabled".
5. 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
* Other screen readers: contact vendors