Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Automatically report incoming messages in Skype for Business When in a chat window #7286
Note this is different to #7281 as this is dealing with automatic reporting of incoming messages from within an already active chat window, rather than a global notification.
Steps to reproduce:
With NVDA running:
Hi, for Edge, when alerts appear, one needs to traverse the children to find out what the message is. Happy to donate my Edge app module code to NV Access. Thanks. From: Michael Curran [mailto:firstname.lastname@example.org] Sent: Wednesday, June 14, 2017 10:38 PM To: nvaccess/nvda <email@example.com> Cc: Subscribed <firstname.lastname@example.org> Subject: [nvaccess/nvda] Report incoming messages in Skype for Business When in a chat window (#7286) Note this is different to #7281 <#7281> as this is dealing with automatic reporting of incoming messages from within an already active chat window, rather than a global notification. 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. Expected behavior: NVDA should report the new message as it appears in the chat history, on both machines. Actual behavior: NVDA reports nothing at all. Technical info: Skype for business fires a liveRegionChanged UIAutomation event on each new message. Therefore NVDA should support UIA live region events in general... which will be useful also in places such as when no results are available when searching in settings, the MS Edge notification bar, and Windows update progress on the logon screen. However, Skype for Business has a strange implementation where it concatinates recent messages (from the same person and same minute) into one message. Therefore Some custom code for Skype for business will also be needed here. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#7286> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkGJocUN9jjogAwYZynZyFKB-iQJ5ks5sEMMfgaJpZM4N6wIu> .