Topics

NVDA becoming unresponsive in Microsoft Teams


Luke Robinett
 

The conferencing/chat app Microsoft Teams is generally fairly accessible, but I’m experiencing a recurring issue. After a certain amount of time with the app loaded, eventually NVDA will no longer narrate the contents of the Teams GUI when using the tab key and Teams shortcut keys. When this happens, the only way to navigate the app is with object navigation. If I close and relaunch Teams it starts working again.

This happens frequently, but I can’t quite pin down a specific condition or amount of time that triggers it. Sometimes it happens out of the blue, other times it seems to happen after I’ve shared my desktop on a call.

I’ve tried restarting NVDA but it doesn’t fix it. I’ve also tried NVDA key + F5 to refresh the virtual buffer but still nothing. Can anyone think of any other troubleshooting steps I can try? Having to restart Teams is not ideal, as I’m often in the middle of a work conference and that’s akin to walking out of the room. Lol. Especially annoying/embarrassing when I’m trying to share content.

 


Sarah k Alawami
 

This I believe has ben discussed on this group, if not it has ben discussed on my ttwitter feed as well. I would search at least on the group to see and on github as well.

Take care

Sarah Alawami, owner of TFFP. . For more info go to our website.

to subscribe to the feed click here and you can also follow us on twitter

Our discord is where you will know when we go live on [twitch.](http://twitch.tv/ke7zum] Feel free to give the channel a follow and see what is up there.

For stream archives, products you can buy and more visit my main lbry page and my tffp lbry page You will also be able to buy some of my products and eBooks there.

Finally, to become a patron and help support the podcast go here

On 2 Jun 2020, at 21:29, Luke Robinett wrote:

The conferencing/chat app Microsoft Teams is generally fairly accessible, but I’m experiencing a recurring issue. After a certain amount of time with the app loaded, eventually NVDA will no longer narrate the contents of the Teams GUI when using the tab key and Teams shortcut keys. When this happens, the only way to navigate the app is with object navigation. If I close and relaunch Teams it starts working again.

This happens frequently, but I can’t quite pin down a specific condition or amount of time that triggers it. Sometimes it happens out of the blue, other times it seems to happen after I’ve shared my desktop on a call.

I’ve tried restarting NVDA but it doesn’t fix it. I’ve also tried NVDA key + F5 to refresh the virtual buffer but still nothing. Can anyone think of any other troubleshooting steps I can try? Having to restart Teams is not ideal, as I’m often in the middle of a work conference and that’s akin to walking out of the room. Lol. Especially annoying/embarrassing when I’m trying to share content.

 


David Goldfield
 

This problem is not just an NVDA issue but is more of a problem with Teams and it's one which Microsoft is aware of, although I'm somewhat mystified that it's taken this long for a fix to be deployed to production.

One way to get Teams to cooperate when accessibility seems to break down is to resize the window. In other words, press Windows-down arrow to minimize it and then restore or maximize it again. This should get Teams to resume communicating with your screen reader.

David Goldfield,
Blindness Assistive Technology Specialist
JAWS Certified, 2019

WWW.DavidGoldfield.org
On 6/3/2020 12:52 AM, Sarah k Alawami wrote:

This I believe has ben discussed on this group, if not it has ben discussed on my ttwitter feed as well. I would search at least on the group to see and on github as well.

Take care

Sarah Alawami, owner of TFFP. . For more info go to our website.

to subscribe to the feed click here and you can also follow us on twitter

Our discord is where you will know when we go live on [twitch.](http://twitch.tv/ke7zum] Feel free to give the channel a follow and see what is up there.

For stream archives, products you can buy and more visit my main lbry page and my tffp lbry page You will also be able to buy some of my products and eBooks there.

Finally, to become a patron and help support the podcast go here

On 2 Jun 2020, at 21:29, Luke Robinett wrote:

The conferencing/chat app Microsoft Teams is generally fairly accessible, but I’m experiencing a recurring issue. After a certain amount of time with the app loaded, eventually NVDA will no longer narrate the contents of the Teams GUI when using the tab key and Teams shortcut keys. When this happens, the only way to navigate the app is with object navigation. If I close and relaunch Teams it starts working again.

This happens frequently, but I can’t quite pin down a specific condition or amount of time that triggers it. Sometimes it happens out of the blue, other times it seems to happen after I’ve shared my desktop on a call.

I’ve tried restarting NVDA but it doesn’t fix it. I’ve also tried NVDA key + F5 to refresh the virtual buffer but still nothing. Can anyone think of any other troubleshooting steps I can try? Having to restart Teams is not ideal, as I’m often in the middle of a work conference and that’s akin to walking out of the room. Lol. Especially annoying/embarrassing when I’m trying to share content.

 


Eilana Benish
 

Shalom all

this is a known issue for quite some time now and as I understood the problem is with the platform for making apps like Microsoft Teams and WhatsApp For Windows .

in the meantime , I suggest you work with Microsoft Teams from the browser. I guess that the best experience would be with the new Microsoft Edge based chromium.

I tested Microsoft team with the Mozilla Firefox browser and NVDA And I did not experience any problems with NVDA stops Speaking .in fact I think that in the browser Microsoft teams works better due to the high level of Accessibility using ARIA correctly.

 



‫בתאריך יום ד׳, 3 ביוני 2020 ב-15:41 מאת ‪David Goldfield‬‏ <‪david.goldfield@...‬‏>:‬

This problem is not just an NVDA issue but is more of a problem with Teams and it's one which Microsoft is aware of, although I'm somewhat mystified that it's taken this long for a fix to be deployed to production.

One way to get Teams to cooperate when accessibility seems to break down is to resize the window. In other words, press Windows-down arrow to minimize it and then restore or maximize it again. This should get Teams to resume communicating with your screen reader.

David Goldfield,
Blindness Assistive Technology Specialist
JAWS Certified, 2019

WWW.DavidGoldfield.org
On 6/3/2020 12:52 AM, Sarah k Alawami wrote:

This I believe has ben discussed on this group, if not it has ben discussed on my ttwitter feed as well. I would search at least on the group to see and on github as well.

Take care

Sarah Alawami, owner of TFFP. . For more info go to our website.

to subscribe to the feed click here and you can also follow us on twitter

Our discord is where you will know when we go live on [twitch.](http://twitch.tv/ke7zum] Feel free to give the channel a follow and see what is up there.

For stream archives, products you can buy and more visit my main lbry page and my tffp lbry page You will also be able to buy some of my products and eBooks there.

Finally, to become a patron and help support the podcast go here

On 2 Jun 2020, at 21:29, Luke Robinett wrote:

The conferencing/chat app Microsoft Teams is generally fairly accessible, but I’m experiencing a recurring issue. After a certain amount of time with the app loaded, eventually NVDA will no longer narrate the contents of the Teams GUI when using the tab key and Teams shortcut keys. When this happens, the only way to navigate the app is with object navigation. If I close and relaunch Teams it starts working again.

This happens frequently, but I can’t quite pin down a specific condition or amount of time that triggers it. Sometimes it happens out of the blue, other times it seems to happen after I’ve shared my desktop on a call.

I’ve tried restarting NVDA but it doesn’t fix it. I’ve also tried NVDA key + F5 to refresh the virtual buffer but still nothing. Can anyone think of any other troubleshooting steps I can try? Having to restart Teams is not ideal, as I’m often in the middle of a work conference and that’s akin to walking out of the room. Lol. Especially annoying/embarrassing when I’m trying to share content.

 



--

 ובכבוד רב | Sincerely,

אילנה בניש מורשה נגישות שירות 2200 | Eilana Benish, service Accessibility authorized (2200)

ניהול פרויקטים – נגישות ושמישות אינטרנט וטכנולוגיות מידע  | Projects manager – Accessibility & usability on internet and ICT

📱 +972-50-7100367 | 📧 benish.ilana@...