microsoft / microsoft/BotFramework-WebChat

Buttons options function as a list and should be indicated as such to screen reader users.

Open
#4,990 1 comment 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?

No response

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?

Keyboard navigation

What is the public URL for the website?

https://edfinancial.com

How to reproduce the issue?

This is feedback from the accessibility company Allyant who has been testing our website and has people who use screenreaders and other assistive technologies as a part of their testing team.

button-list

What do you expect?

When a series of similar items is grouped together in a meaningful or deliberate way, this should be conveyed to screen reader users. Use standard HTML to mark up all such content as a list.

What actually happened?

The buttons are not conveyed as a list to screen reader users.

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

No response

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/WCAG22/Understanding/info-and-relationships

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

Start by reproducing the button group at https://edfinancial.com with a screen reader and inspect its rendered HTML. Compare the grouping with the WCAG 2.2 Info and Relationships reference; done means the related buttons are announced as a list without changing their keyboard behavior.

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.