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.

Sign up for GitHub

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

Jump to bottom

Refactor Datatable in Accordance with W3C Authoring Practices Guidelines #4761

Closed
dakahn opened this issue Nov 22, 2019 · 1 comment
Closed

Refactor Datatable in Accordance with W3C Authoring Practices Guidelines #4761

dakahn opened this issue Nov 22, 2019 · 1 comment
Labels
severity: 1 https://ibm.biz/carbon-severity type: a11y ♿

Comments

@dakahn
Copy link
Contributor

dakahn commented Nov 22, 2019

closes #3740
closes #3741
closes #3805
closes #4225

The current implementation of our Datatable has serious usability/accessibility issues for both screen readers and keyboard users. A refactor in accordance with the W3C Authoring Practices Guidelines 1.2 example for a Data Grid is the the way forward here.

Worth noting is that this implementation and refactor would not include advanced Data Grid features (Excel/spreadsheet like funcntionality). We'd need to figure out some kind of strategy for teams to opt-in to those advanced (and potentially less accessible) features.
@dakahn dakahn added type: a11y ♿ priority: high severity: 1 https://ibm.biz/carbon-severity labels Nov 22, 2019
@dakahn dakahn added this to the ♿Carbon WCAG Compliance♿ milestone Nov 22, 2019
@joshblack
Copy link
Contributor

@dakahn what are the features of data table that we're currently finding are inaccessible?

@mattrosno mattrosno removed this from the ♿Carbon WCAG Compliance♿ milestone Dec 13, 2019
@dakahn dakahn closed this as completed Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
severity: 1 https://ibm.biz/carbon-severity type: a11y ♿
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mattrosno @joshblack @dakahn