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

[Table] TableToolbar not forwarding aria props #2607

Closed
1 of 2 tasks
TheSharpieOne opened this issue Jul 15, 2021 · 0 comments · Fixed by #2860
Closed
1 of 2 tasks

[Table] TableToolbar not forwarding aria props #2607

TheSharpieOne opened this issue Jul 15, 2021 · 0 comments · Fixed by #2860
Labels
severity: 3 Affects minor functionality, has a workaround type: a11y ♿ type: bug 🐛

Comments

@TheSharpieOne
Copy link

What package is this for?

  • React
  • Angular

Describe the bug

The Carbon component accepts aria-label, which must be unique, but the value is not forwarded by the Table component.
When there are multiple tables on a page, this becomes an a11y issue (as well as when there is a single table, there is no way to customize this aria value).

===== Problem Summary =====
Multiple elements with "region" role do not have unique labels.
Each element with a "region" role must have a unique label.
When there are multiple elements with a "region" role, they must have unique labels that clearly describe the region's content. This includes labelled

elements. This label helps people using assistive technologies to quickly find and navigate to each region.

===== EXPECTED RESULT(Accessibility guidance) =====

For each element with a "region" role, either set the value of the aria-labelledby attribute of each region to the id value of any visible text that appropriately and uniquely describes that region's content;
OR, use the aria-label attribute to add an invisible, unique, non-empty label to each element with the "region" role.
image

@kevinsperrine kevinsperrine added type: a11y ♿ severity: 3 Affects minor functionality, has a workaround severity: 2 Affects major functionality, has a workaround and removed status: needs triage 🔍 severity: 3 Affects minor functionality, has a workaround labels Jul 16, 2021
@JordanWSmith15 JordanWSmith15 added severity: 3 Affects minor functionality, has a workaround and removed severity: 2 Affects major functionality, has a workaround labels Aug 11, 2021
@kodiakhq kodiakhq bot closed this as completed in #2860 Sep 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: 3 Affects minor functionality, has a workaround type: a11y ♿ type: bug 🐛
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants