microsoft / microsoft/BotFramework-WebChat
[white Label- Card Wizard]: Name control is visually appearing as button but acting like expandable control.
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 response
What is the PWD impact?
Users form expectations based on visual cues. When the control looks like a button but unexpectedly reveals form fields, keyboard‑only and cognitive users may become disoriented. This mismatch increases cognitive load and may cause users to mistakenly assume they clicked the wrong control or triggered an unintended action.
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?
ARIA roles
What is the public URL for the website?
No response
How to reproduce the issue?
Repro Steps
- Open URL: chro and sign in using valid credentials.
- Navigate to web chat page and select 4.18.1-main.20240927.ea7a875 (30/9/2024) version and then select mockBot link under present label and then select open web chat in new window link at bottom.
3.Navigate to white label experience chat page and type Card Wizard word in type your message text box. - Response will appear.
- Navigate to the Name control and activate it.
- Observe an issue that Name control is visually appearing as button but acting like exapandable control.
What do you expect?
The element should expose a role and visual appearance that matches its actual behavior. If activating the control expands form fields, it should be represented as an expandable control (e.g., accordion) rather than a button.
What actually happened?
Name control is visually appearing as button but acting like expandable control.
Do you have any screenshots or recordings to repro the issue?
https://github.com/user-attachments/assets/10513299-8245-41e9-a9ee-fe5a9a9b962c
Did you find any DOM elements that might have caused the issue?
No response
MAS reference
No response
WCAG reference
No response
WAI-ARIA reference
No response
Adaptive Card JSON
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
Start by reproducing the issue in the white label Card Wizard flow and inspect the Name control's exposed ARIA role and expansion behavior with Edge and Windows Narrator. Done means the control's role and visual appearance accurately match whether activating it expands form fields.
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
- Needs clarification
- Newbie friendliness
- 35/100