microsoft / microsoft/BotFramework-WebChat

Incorrect role is defined for the ‘Snooze’ and ‘dismiss’ control.

Open
#5,750 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A11ySev2 A11yWCAG Accessibility area-accessibility Bot Services BotFrameworkWebChat_Web bug customer-reported HCL-BIC
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?

Yes, this is related to Adaptive Card. However, it does not repro on Adaptive Cards Designer.

What is the PWD impact?

When an incorrect role is defined for the ‘Snooze’ and ‘dismiss’ controls, screen reader users receive misleading or incomplete information. For example, if these controls are marked as role="link" but actually behave like buttons, users may expect navigation instead of an action.

What browsers and screen readers do this issue affect?

No response

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?

No response

How to reproduce the issue?

Repro Steps: ​

  1. Open URL: Web Chat in edge browser.
    2.Ask query 'Card Breakfast'.
  2. Navigate to ‘Place to buy’ and ‘Related product’ control.
  3. Observe the issue that Incorrect role is defined for the ‘Snooze’ and ‘dismiss’ control.
What do you expect?

Role as button should be defined for the ‘Snooze’ and ‘dismiss’ control.

What actually happened?

Incorrect role is defined for the ‘Snooze’ and ‘dismiss’ control.

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

https://github.com/user-attachments/assets/a7e6b544-3088-4396-8adc-18a23734205a

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

No response

MAS reference

No response

WCAG reference

https://www.w3.org/WAI/WCAG21/Understanding/name-role-value

WAI-ARIA reference

No response

Adaptive Card JSON

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

Start with the Web Chat Adaptive Card flow described in the reproduction steps and inspect the DOM for the ‘Snooze’ and ‘dismiss’ controls. Confirm that both controls expose button roles to assistive technology and verify the result using the reported Web Chat scenario.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.