BotFramework-WebChat
BotFramework-WebChat copied to clipboard
microsoft
NVDA is announcing the place holder information twice.
Is it an issue related to Adaptive Cards?
No.
What is the PWD impact?
Visually challenged users who rely on screen readers are getting impacted if NVDA is announcing the place holder information twice.
What browsers and screen readers do this issue affect?
Others
Are there any code-based customization done to Web Chat?
No, I am using Web Chat without any customizations except "styleOptions".
What version of Web Chat are you using?
Latest production
Which area does this issue affect?
Others or unrelated
What is the public URL for the website?
https://airtuserexpdev.azurewebsites.net/Dashboard
How to reproduce the issue?
Step 1: Open the Url: https://airtuserexpdev.azurewebsites.net/Dashboard in Edge Browser->SAGE chat window will display. Step 2: Type “What is the accessibility process”->Invoke “Dislike” button. Step 3: Verify whether NVDA is announcing the place holder information twice or not.
What do you expect?
NVDA should announce the place holder content only once. Ensure: NVDA should announce as "Please let us know what information we could have provided to help you better edit multi line blank".
What actually happened?
NVDA is announcing the place holder information twice. Observation: NVDA is announcing as "Please let us know what information we could have provided to help you better edit multi line Please let us know what information we could have provided to help you better blank".
Do you have any screenshots or recordings to repro the issue?
Did you find any DOM elements that might have caused the issue?
No response
MAS reference
WCAG reference
No response
WAI-ARIA reference
No response
Adaptive Card JSON
No response
Additional context
No response
#A11yusable;#A11ySev4;#MAS1.3.1;#HCL;#Accessibility;#FeatureBotframeworkwebchat-Apr23;
This is related to Adaptive Cards. The input box is rendered by Adaptive Cards.
Please file a bug to their repo. If they think otherwise, please open a new bug and tag their response.
