microsoft / microsoft/BotFramework-WebChat
Screen readers are not narrating the descriptive information for 'here' link while navigating using tab key.
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Description
Is it an issue related to Adaptive Cards?
No.
What is the PWD impact?
Screen reader users will be impacted as focus moves to hidden element and announces Unnecessary information which might confuse users. The user will get confused, and the issue will lead to disorientation.
What browsers and screen readers do this issue affect?
Windows: Chrome with NVDA
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?
How to reproduce the issue?
Step 1: Open the above URL in Edge Chromium Browser. > Sign in with valid credentials
Step 2: Type 'How can I support someone on my team who is contributing through the program? in edit field.
Step 3: Verify whether Screen readers are narrating the descriptive information for 'here' link while navigating using tab key or not.
What do you expect?
Screen readers should narrate the descriptive information for 'here' link while navigating using tab key.
What actually happened?
Screen readers are not narrating the descriptive information for 'here' link while navigating using tab key.
Screen reader only announces it as: link here
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the issue at the provided SharePoint URL with Edge Chromium and NVDA, then locate the rendered “here” link in the Web Chat output. Done means the screen reader announces the link’s descriptive information rather than only “link here.”
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100