microsoft / microsoft/BotFramework-WebChat

Verify screen reader behavior on Adaptive Card

Open
#3,740 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backlog bug external-adaptive-cards front-burner team-agility
Dominant language
HTML
Stars
1.8k
Forks
1.6k
Avg merge
22h 58m
Merged PRs (30d)
2

Description

Screenshots

Version

4.12.0-0 with AC 2.5.0.

Describe the bug

While testing transcript navigation, one of the screen reader behaviors around Adaptive Cards seems off.

We would need to repro this on a page outside of Web Chat. If it still repro, will bring it to the accessibility team to verify.

Steps to reproduce

AC card should be read if the user focus into it

  1. Build a plain HTML page
  2. Put a button "Hello"
  3. Append a AC container with a card, with at least one textblock "Aloha", followed by one button (e.g. card breakfast)
  4. Run the page with screen reader
  5. TAB into the first button "Hello"
  • Expect: AT should narrate the content of the button, i.e. "Hello button".
  1. Press TAB again and it should focus the first input element in the AC
  • Expect: AT should narrate the content of the card, i.e. "Aloha".

Additional context

[Bug]

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 plain HTML reproduction described in the issue: place a Hello button before an Adaptive Card containing a text block and button, then test TAB navigation with a screen reader. Compare the spoken output with the stated expectations and determine whether the behavior reproduces outside Web Chat; if it does, bring the result to the accessibility team for verification.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.