Hello, I'm having trouble using the Phone Link app with my screen reader on Windows 11 (24H2). When I try tabbing or shift-tabbing in the message text field, the app crashes. I've tested this with the latest versions of both JAWS 2025 and NVDA 2024.4, but I'm still experiencing the same issue.
How do I read messages in a conversation? Thanks.
By Knut, 28 December, 2024
Forum
Windows
Comments
RE: NVDA
Hi there,
While I cannot speak on JAWS, I have a recommendation for NVDA. Try restarting NVDA without any add-ons running, and see how that goes for you.
It is a possibility that one or more add-ons are causing the crash, otherwise, try closing out both screen readers, and turning on narrator.
I know nobody likes narrator, but it is great for troubleshooting purposes.
HTH.
R: NVDA
The installation of NVDA I was using didn't have any addons installed.
Checked for updates?
You mentioned version 2024.4 of NVDA, but there has been a more recent update. It is now up to version 2024.4.1. If you already have this version, I'd consider downgrading, but on the flipside if you do not have it, then try updating NVDA and see how Phone Link does.
Also, if you have not already tried, then try accessing your messages with Windows Narrator, just to see if you can.
I am not having these issues with Phone Link on my copy of Windows 11 Build 24H2, and NVDA 2024.4.1, and I have quite a bit of add-ons with my copy of NVDA.
I do not use JAWS however, so someone else will have to advise you on that.
Sure enough
Yep. And, add Narrator to the list. I just tried out the app today. Composing a fresh message from contacts works, but beware hitting enter on a conversation. In fact, it might just be conversations with more than one message in the list. I'm not going back to confirm, though. Unlike certain fruit-centric companies, I think Microsoft will fix it sooner rather than later if we report it...somehow.
Microsoft are generally the…
Microsoft are generally the king of retrocompatibility, and the 3rd party screen are only that strong because they have great backing with the apis. Mac:: appname does not respond. I had already abandoned phone link before getting my mac and even more so after so I can't tell if this bug is there for me but best of luck!
Can you confirm that pressing escape in a call will still hang up?