Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Visual requirement - Bot Framework Web Chat - Card Input]: The visual labels are not defined for all form fields under 'Card Input' screen. #5344

Open
manojs5 opened this issue Oct 30, 2024 · 1 comment
Labels
area-accessibility Bot Services Required for internal Azure reporting. Do not delete. Do not change color. bug Indicates an unexpected problem or an unintended behavior. customer-reported Required for internal Azure reporting. Do not delete. external-adaptive-cards

Comments

@manojs5
Copy link

manojs5 commented Oct 30, 2024

Is it an issue related to Adaptive Cards?

No.

What is the PWD impact?

User Experience:

If a label is not defined for users with visual disabilities and will not get the proper information, then the users will not be able to find out what kind of information is needed in the fields and will face difficulties while navigating on the page.

Note:

User credentials should NOT be included in the bug.

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?

Suggested action, Others or unrelated

What is the public URL for the website?

https://compulim.github.io/webchat-loader/

How to reproduce the issue?

  1. Open URL: https://compulim.github.io/webchat-loader/ 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
  3. and then select open web chat in new window link at bottom.
  4. Navigate to white label experience chat page and type Card Input word in type your message text box.
  5. Navigate to the search results and fill details and then navigate to submit results and show card results.
  6. Verify whether the visual labels are provided or not.

What do you expect?

The visual labels should be defined for all form fields under 'Card Input' screen.
Ex: for name edit field the visual label should be defined as 'Name'.

What actually happened?

The visual labels are not defined for all form fields under 'Card Input' screen.
Observation: Screen reader (Narrator, nvda, jaws) announcing as 'Name edit'

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

Image

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

No response

MAS reference

MAS 3.3.2 – Labels or Instructions

WCAG reference

3.3.2 Labels or Instructions

WAI-ARIA reference

No response

Adaptive Card JSON

No response

Additional context

No response

@manojs5 manojs5 added area-accessibility Bot Services Required for internal Azure reporting. Do not delete. Do not change color. bug Indicates an unexpected problem or an unintended behavior. customer-reported Required for internal Azure reporting. Do not delete. labels Oct 30, 2024
@manojs5
Copy link
Author

manojs5 commented Oct 30, 2024

#A11yMAS;#A11ySev2;#Accessibility;#Benchmark;#BotFrameworkWebChat-Oct24;#HCL;#MAS3.3.2;#Win11-Edge(Chromium);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-accessibility Bot Services Required for internal Azure reporting. Do not delete. Do not change color. bug Indicates an unexpected problem or an unintended behavior. customer-reported Required for internal Azure reporting. Do not delete. external-adaptive-cards
Projects
None yet
Development

No branches or pull requests

2 participants