Skip to content

[White Label - Card Wizard]: Narrator is not announcing the label information for Name button. #5720

Open

Description

@Kusum199

Is it an issue related to Adaptive Cards?

No response

What is the PWD impact?

Screen reader users are unable to understand the purpose of the Name button, preventing them from interacting independently with the UI and potentially blocking task completion.

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?

No response

How to reproduce the issue?

Pre-Requisite:
Turn on Narrator

Repro Steps

  1. Open URL: chro and sign in using valid credentials.
  2. 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.
  3. Response will appear.
  4. Navigate to the Name control.
  5. Observe an issue that Narrator announcing incorrect role as toggle button for Name button.

What do you expect?

The element should expose a programmatically determinable accessible name so that Narrator clearly announces the label associated with the Name button.
Observation: When focus lands on Name control narrator should announce please provide the following information Name control.

What actually happened?

Narrator is not announcing the label information for Name button.
Observation: when focus lands on Name button it is announcing as Name toggle button on.

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

Narrator.is.not.announcing.the.label.information.for.Name.button.mp4

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

Activity

  1. added
    bugIndicates an unexpected problem or an unintended behavior.
    customer-reportedRequired for internal Azure reporting. Do not delete.
    Bot ServicesRequired for internal Azure reporting. Do not delete. Do not change color.
    on Feb 18, 2026
  2. OEvgeny commented on Oct 21, 2026

    @OEvgeny
    Collaborator

    Thanks for the report and the video.

    We could not reproduce this as a Web Chat defect. In the video, Narrator says "1. Name, button, collapsed" when focus lands on the control. That is its accessible name (the same as the visible text "1. Name"), its role, and its expanded/collapsed state, which is what WCAG 4.1.2 asks for. "1. Name" is an Action.ShowCard button: it has aria-expanded and has never had a toggle (pressed) state. The issue text also mentions "toggle button on". Older builds did expose other card actions, such as Submit, as toggle buttons. Since #5900, all card action buttons are plain buttons, and an action the user performed is described as "Selected".

    "Please provide the following information:" is a separate text block in the card that the bot sends (MockBot's "Card Wizard" sample, which comes from the Adaptive Cards samples). It is not a label of the "1. Name" button. Adaptive Cards has no way to connect body text to an action, so Web Chat renders it as text right before the button, and Narrator reads it in scan mode. The text fields inside the card ("First Name", "Middle Name", and so on) are labelled correctly.

    If a bot wants this context announced when focus enters the card, it can:

    • set speak on the card: Adaptive Cards uses it as the card's label, and Web Chat then exposes the card (which has buttons) as a form named by that text;
    • set tooltip on the action (Adaptive Cards 1.5): it becomes the button's description;
    • use a more descriptive action title.

    We propose to close this issue as by design.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions