Re: Windows 10 Anniversary Update/Microsoft Edge and UWP: one change affects everyone

Joseph Lee <joseph.lee22590@...>

For Windows 10 Home users, you cannot delay it indefinitely. For Windows 10 Pro, Enterprise (regular update) and Education, you can delay it for several months (defer upgrades). For Windows 10 Enterprise LTSB, you'll only get security updates until October 2025.

-----Original Message-----
From: [] On Behalf Of Bharat
Sent: Wednesday, July 6, 2016 1:00 AM
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and UWP: one change affects everyone

does it mean, we should delay updating to the anniversary edition as it is released? should i put it on no update or whatever it is called in Windows 10? with around 25 days to go for the anniversary update rollout, i don't quite think these things would be fixed so soon as that & that, we may then have to struggle with things...? isn't it?

On 7/6/16, Carolyn Arnold <> wrote:
Thank you, Joseph. Good to know that there is someone like you with
your know-how working with Microsoft. I hope they will be accepting of
your recommendations.

Bye for now,


-----Original Message-----
[] On Behalf Of Joseph Lee
Sent: Tuesday, July 5, 2016 6:46 PM
Subject: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and
UWP: one change affects everyone

Hi all,

As a follow-up to a thread on Edge and what not, here's the story
behind it:

Back in 2015, when Microsoft was working on Edge, it used a specific
info in a UI Automation attribute. In a recent Windows 10 Anniversary
Update Preview builds, this information has changed. Not only it broke
Edge for some screen readers, it also broke search results
announcement in Start menu among other controls. I and other
developers have been working with Microsoft on understanding what's
going on and provide needed fixes in our screen readers.

In regards to Edge support: Edge is a UIA universe.
Therefore a reasonable support for Edge will require good UIA support
from screen readers (termed UIA clients). Recent screen readers do
include UIA support facility (UIA handler in NVDA, FSUIA in JAWS).
However, it is known that Microsoft includes broken UIA
implementations in some apps (including Office 2013, and in older
releases, Edge), and MS is known for changing UIA attributes without
notice, giving screen reader vendors (NV Access, VFO and others) a
headache when it comes to writing workarounds (hence Eric Damery's
statement on difficulty in supporting Edge in JAWS is justified). I
can go on about UIA stuff and workarounds that screen reader
developers came up with (I think it should be a separate thread), as
part of my recent work has been hunting for weirdness in UIA and
writing workarounds for it in NVDA (my patch on UAC redesign
workaround is a good example, something that taught me not to trust MS
completely when it comes to certain UIA information).

In regards to UWP: due to security mechanism in place, some screen
readers will not announce typed characters (it was observed in NVDA).
Screen reader vendors and Microsoft were told about this problem.

Third, about toasts: when toasts appear, they usually fire a tool tip
event, letting screen readers know that they should announce new
notifications. In a more recent Insider Preview build, toasts do not
fire this event, which means toasts will not be announced by
third-party screen readers automatically (exception is Narrator). I
raised this issue with Microsoft and with NV Access, and at least NV
Access has put this as a high priority issue.

New UAC: Due to redesigned look of User Account Control in Anniversary
Update, some screen readers would not announce UAC prompts. This
affects not only third-party screen readers, but also affects Narrator
(turns out there is some misunderstanding between MS and screen reader
developers when defining what exactly a dialog is). At least for NVDA,
this was resolved and is going through active testing in the
next/alpha snapshots.

Lastly, about so-called OneCore: According to Peter Bright (Ars
Technica) and various talks given by Microsoft staff, OneCore is a
group of shared components that power Windows 10. This include
essential components all variants of Windows 10 come with, with each
variant including variant-specific layer on top of that. For example,
10 for PC's include oneCore, and on top are desktop and UWP (Universal
Windows Platform) components and other support routines, whereas
Windows 10 Mobile include OneCore and phone functionality. An
interesting variant is Windows Holographic, which includes OneCore
plus holographic user interface and UWP.

The high-level overview of components included in each variant of
Windows 10 (to be seen in Anniversary Update)

* OneCore: Windows NT kernel (ntoskrnl.exe),
subsystems support.

* PC's: OneCore, desktop experience, UWP, features
for different versions of Windows 10 (Home, Pro, Enterprise/Enterprise
LTSB, Education), Windows Subsystem for Linux if enabled (for 64-bit

* Windows 10 Mobile: OneCore, telephony stack,
cellular connectivity components, UWP.

* Windows 10 IoT (Internet of Things): OneCore, UWP,
IoT-specific components.

* Windows Holographic (Microsoft HoloLens and
friends): OneCore, Windows Holographic interface, UWP.

* Xbox One: OneCore, game/OS hypervisor control
routine (called Nanovisor according to Peter Bright), UWP, gaming

* Windows Server 2016: OneCore, choice of components
for server roles.


* OneCore to rule them all (Ars Technica):

* UAC prompt not announced by NVDA:

* UIA frameowkr ID for Edge has changed:

* Toasts not announced by NVDA in build 14366:

The NVDA issue references are included as they contain useful
background info.



Join to automatically receive all group messages.