microsoft / microsoft/BotFramework-WebChat

Screen reader is announcing unnecessary hyperlink information.

Open
#5,014 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-accessibility Bot Services bug customer-reported
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 is announcing unnecessary hyperlink information.

What browsers and screen readers do this issue affect?

Windows: Edge with Windows Narrator

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 How do I get a grade C?
Step 3: Verify whether Screen reader is announcing unnecessary hyperlink information or not.

What do you expect?

Screen reader should not announce unnecessary hyperlink information.
Ensure: NVDA should announce as 'Accessibility Inventory Report (AIRT) link.'

What actually happened?

Screen reader is announcing unnecessary hyperlink information.
Observation: NVDA is announcing as 'Accessibility Inventory Report (AIRT) (https://airt.azurewebsites.net/Dashboard)'

Do you have any screenshots or recordings to repro the issue?

MAS 1 3 1 - Screen reader is announcing unnecessary hyperlink information

Did you find any DOM elements that might have caused the issue?

No response

MAS reference

MAS 1.3.1 – Info and Relationships

WCAG reference

No response

WAI-ARIA reference

No response

Adaptive Card JSON

No response

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue at the provided Dashboard URL using Edge with Windows Narrator and verify the announcement for the SAGE chat response. Trace the generated hyperlink and compare its announcement with the expected “Accessibility Inventory Report (AIRT) link” wording; done means the unnecessary URL is no longer announced.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
accessibility, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.