OS: Windows 10
WebChat: v. 4.9.0 CDN version
Screen reader: JAWS, Narrator
Browser: MS Edge Version 83.0.478.37, IE 11, Chrome Version 81.0.4044.138
Describe the bug
When the screen readers in general read the content of a bubble, they do not announce the element as being a link and allow the user to press enter and navigate to Url. Activating links is possible only after tabbing back and forth, but only with Narrator. JAWS fails most of the time to open the link.
I was able to observe that if a link is contained within an adaptive card, once focused JAWS will activate it all the time.
OS: Windows 10
WebChat: v. 4.9.0 CDN version
Screen reader: JAWS, Narrator
Browser: MS Edge Version 83.0.478.37, IE 11, Chrome Version 81.0.4044.138
Describe the bug
When the screen readers in general read the content of a bubble, they do not announce the element as being a link and allow the user to press enter and navigate to Url. Activating links is possible only after tabbing back and forth, but only with Narrator. JAWS fails most of the time to open the link.
I was able to observe that if a link is contained within an adaptive card, once focused JAWS will activate it all the time.