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

[Bug]: While navigating to “Brand” edit field narrator is not announcing the label name of the edit field. #24127

Open
msftedad opened this issue Sep 11, 2023 · 2 comments · May be fixed by #24981

Comments

@msftedad
Copy link

Describe the bug

While navigating to “Brand” edit field narrator is not announcing the label name of the edit field.

Actual Result:
While navigating to “Brand” edit field narrator is not announcing the label name of the edit field.

Expected Result:
While navigating to “Brand” edit field narrator should announce the label name for “Brand” edit field.

To Reproduce

  1. Open URL: Common Navigation - Scrolling Panel ⋅ Storybook (windows.net)
  2. Navigate to “App bar” button at right side of the pane invoke it and navigate to “Default” link invoke it.
  3. Now navigate to “Controls” tab item invoke it and navigate to “Brand” edit field and observe the narrator announcement.

Attachments:
label name for edit field.webm

System

OS: Windows 11
OS version: 22H2 (OS Build 22621.2134)
Edge Version: 116.0.1938.69 (Official build) (64-bit)

Additional context

No response

@MarioKavula
Copy link

Hello, I am new to open source and I would like to help with this issue or other accessibility-related issues.

@abhisheksharma010
Copy link

Hey there! 👋

I'm new to open source and super excited to dive in! I'd love to work on this. Can I be assigned to this issue? 🚀

MarioKavula added a commit to MarioKavula/storybook that referenced this issue Nov 22, 2023
@MarioKavula MarioKavula linked a pull request Nov 25, 2023 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants