Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows 10 build 14366: Toasts are not announced #6096

josephsl opened this issue Jun 20, 2016 · 0 comments

Windows 10 build 14366: Toasts are not announced #6096

josephsl opened this issue Jun 20, 2016 · 0 comments
blocked p1 Priority 1: highest


Copy link


A user using Insider build 14366 reports that toasts are no longer announced.


  1. Using Insider build 14366/14367, perform an action that causes toasts to appear, such as connecting hardware.
  2. Listen for toast sound.

Expected: NVDA announces toasts.
Actual: NVDA does not announce toasts.
Cause: Accessibility event Checker (accevent) says toasts do not fire tooltip open event, only window open event is fired. This does not happen with Narrator: when toasts appear, because it listens to window open event, it announces them. I was able to reproduce this on 14366/14367, and can confirm that toasts are announced in build 10586.

Technical: NVDA's UIA handler has a map of which UIA events corresponds to NVDA events. This map does not contain window open event, yet tooltip open event is assigned to alert event. We don't want to listen to window open event, as it causes a flood of events to come through, especially for objects that we do not wish to announce. One workaround would be to tell NVDA that certain windows are safe, thereby allowing window open event from objects such as toasts to be accepted. All this changes if Microsoft fixes this before Anniversary Update (Version 1607) is released (feedback sent to Microsoft).


@nvaccessAuto nvaccessAuto added p1 Priority 1: highest blocked labels Jul 5, 2016
josephsl added a commit to josephsl/nvda that referenced this issue Jul 21, 2016
… timer. re nvaccess#6096

In Redstone, one can set priority to notifications, and if this happens, automation ID changes to PriorityToastView. To handle both normal and high priority toasts, use substrings.
@jcsteh jcsteh added this to the 2016.3 milestone Aug 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
blocked p1 Priority 1: highest
None yet

No branches or pull requests

3 participants