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

igx-combo - make it controllable which value to be bound for the "aria-label" attribute to improve accessibility #13594

Closed
jsakamotoIGJP opened this issue Oct 25, 2023 · 6 comments
Assignees
Labels

Comments

@jsakamotoIGJP
Copy link

Is your feature request related to a problem? Please describe.

Yes, it is.

igx-combo always binds the value of a property specified by the [valueKey] parameter to the aria-label attribute of each combo list item. But, a screen reader application such as Windows Narrator will usually read aloud the value of the aria-label. Eventually, a screen reader application will read aloud the unique key value of each combo list item instead of the displayed text. Obviously, reading aloud those the key values is not helpful for that.

image

Describe the solution you'd like

igx-combo should bind the value of a property specified by the [displayKey] parameter to the aria-label attribute of each combo list item.

Or else making it possible to customize which property will bind to the aria-label attribute must be better.

Describe alternatives you've considered

In some cases, using the aria-labelledby attribute might be a workaround. But it can't cover all of the user scenarios.

Additional context

This is the source project I used to investigate this issue:
📦c-00233265-ng-app.zip

Copy link

There has been no recent activity and this issue has been marked inactive.

@github-actions github-actions bot added the status: inactive Used to stale issues and pull requests label Dec 26, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 2, 2024
@jsakamotoIGJP
Copy link
Author

@Lipata @ChronosSF Please reopen this issue since the customer is waiting to improve this issue.

@Lipata Lipata reopened this Apr 11, 2024
@jsakamotoIGJP
Copy link
Author

@Lipata, Thank you so much for your prompt response!

@github-actions github-actions bot removed the status: inactive Used to stale issues and pull requests label Apr 12, 2024
Copy link

There has been no recent activity and this issue has been marked inactive.

@github-actions github-actions bot added the status: inactive Used to stale issues and pull requests label Jun 11, 2024
@Lipata Lipata removed the status: inactive Used to stale issues and pull requests label Jun 11, 2024
Copy link

There has been no recent activity and this issue has been marked inactive.

@github-actions github-actions bot added the status: inactive Used to stale issues and pull requests label Aug 11, 2024
@Lipata Lipata removed the status: inactive Used to stale issues and pull requests label Aug 11, 2024
Copy link

There has been no recent activity and this issue has been marked inactive.

@github-actions github-actions bot added the status: inactive Used to stale issues and pull requests label Oct 11, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants