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

Component Accessibility Status: Automated Keyboard Navigation Tests Audit #5361

Closed
Tracked by #4625
sstrubberg opened this issue May 28, 2024 · 1 comment
Closed
Tracked by #4625
Labels
role: dev type: a11y ♿ Issues not following accessibility standards type: infrastructure 🤖 Issues related to devops, builds, packaging
Milestone

Comments

@sstrubberg
Copy link
Member

sstrubberg commented May 28, 2024

  • Make a list of which components already have keyboard nav avt tests
  • Make a list of which components don't have keyboard nav avt tests
  • Setup time with IBMa/Gower to prioritize the list of components that don't have keyboard nav avt tests.
    • This could be components are higher value and/or have the most complex/rigorous keyboard navigation requirements
  • Add the final prioritized list of components that need tests added to the parent issue, Component Accessibility Status: Add keyboard navigation AVT tests for each component #5362
@sstrubberg sstrubberg added type: infrastructure 🤖 Issues related to devops, builds, packaging role: dev and removed status: needs triage 🕵️‍♀️ labels May 28, 2024
@sstrubberg sstrubberg changed the title Component accessibility status: Automated Keyboard Navigation Tests Component accessibility status: Automated Keyboard Navigation Tests Audit May 28, 2024
@sstrubberg sstrubberg changed the title Component accessibility status: Automated Keyboard Navigation Tests Audit Component Accessibility Status: Automated Keyboard Navigation Tests Audit May 28, 2024
@sstrubberg sstrubberg added the type: a11y ♿ Issues not following accessibility standards label May 28, 2024
@sstrubberg sstrubberg added this to the 2024 Q2 milestone May 28, 2024
@matthewgallo
Copy link
Member

We'll include this audit as part of the complex state audit, so we no longer need two issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
role: dev type: a11y ♿ Issues not following accessibility standards type: infrastructure 🤖 Issues related to devops, builds, packaging
Projects
Archived in project
Development

No branches or pull requests

2 participants