Start Skype for Business 2016 on two separate machines, logged into separate accounts with the same organisation
From machine A: Find the account logged into on machine B, and type a message to that account.
Note that machine B should not have an open chat window with the first account while you do this.
a toast notification will appear on machine b notifying the user they have a pending chat.
Expected behavior:
NVDA should report the content of the toast notification in speech and braille.
Actual behavior:
NVDA reports nothing at all.
Technical info:
Skype for business uses a non-standard toast notification. It fires a systemAlert UI Automation event on the accept button which contains the content of the message including the shortcut key to activate it.
NVDA should handle UIA systemAlert by reporting the element that received the event.
The text was updated successfully, but these errors were encountered:
Hi, is it shellexperiencehost that fires this object (i.e. the app module for this toast is that executable), and do we have the automation ID and other info?
From: Michael Curran [mailto:notifications@github.com]
Sent: Tuesday, June 13, 2017 9:21 PM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [nvaccess/nvda] Support toast notifications in Skype for Business (#7281)
Steps to reproduce:
With NVDA running:
1. Start Skype for Business 2016 on two separate machines, logged into separate accounts with the same organisation
2. From machine A: Find the account logged into on machine B, and type a message to that account.
Note that machine B should not have an open chat window with the first account while you do this.
3. a toast notification will appear on machine b notifying the user they have a pending chat.
Expected behavior:
NVDA should report the content of the toast notification in speech and braille.
Actual behavior:
NVDA reports nothing at all.
Technical info:
Skype for business uses a non-standard toast notification. It fires a systemAlert UI Automation event on the accept button which contains the content of the message including the shortcut key to activate it.
NVDA should handle UIA systemAlert by reporting the element that received the event.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#7281> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkMwNWFY13M53i1eb677Dn_am6KMoks5sD1-RgaJpZM4N5Xdz> .
Steps to reproduce:
With NVDA running:
Note that machine B should not have an open chat window with the first account while you do this.
Expected behavior:
NVDA should report the content of the toast notification in speech and braille.
Actual behavior:
NVDA reports nothing at all.
Technical info:
Skype for business uses a non-standard toast notification. It fires a systemAlert UI Automation event on the accept button which contains the content of the message including the shortcut key to activate it.
NVDA should handle UIA systemAlert by reporting the element that received the event.
The text was updated successfully, but these errors were encountered: