-
Notifications
You must be signed in to change notification settings - Fork 162
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
Comments
There has been no recent activity and this issue has been marked inactive. |
@Lipata @ChronosSF Please reopen this issue since the customer is waiting to improve this issue. |
@Lipata, Thank you so much for your prompt response! |
There has been no recent activity and this issue has been marked inactive. |
There has been no recent activity and this issue has been marked inactive. |
There has been no recent activity and this issue has been marked inactive. |
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 thearia-label
attribute of each combo list item. But, a screen reader application such as Windows Narrator will usually read aloud the value of thearia-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.Describe the solution you'd like
igx-combo
should bind the value of a property specified by the[displayKey]
parameter to thearia-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
The text was updated successfully, but these errors were encountered: