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 #13748

Closed
2 tasks done
Tracked by #13745
sstrubberg opened this issue May 5, 2023 · 0 comments
Closed
2 tasks done
Tracked by #13745
Labels
adopter: strategic-product Work-stream that directly effects the Product-led Growth initiative. planning: umbrella Umbrella issues, surfaced in Projects views role: dev 🤖 type: a11y ♿ type: infrastructure 🤖 Issues relating to devops, tech debt, etc.
Milestone

Comments

@sstrubberg
Copy link
Member

sstrubberg commented May 5, 2023

Acceptance criteria

  • Configure automated keyboard navigation tests for high value components

Tasks

  1. role: dev 🤖 type: a11y ♿
    guidari
  2. 61 of 61
    planning: umbrella role: dev 🤖
    andreancardona guidari

As part of the audit of problematic states in #13780 we found a number of components that had issues relating to keyboard navigation defects. We've included these as part of #13747. Writing e2e keyboard navigation tests for these could be a proving ground for the approach we take for testing all components' keyboard nav in this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
adopter: strategic-product Work-stream that directly effects the Product-led Growth initiative. planning: umbrella Umbrella issues, surfaced in Projects views role: dev 🤖 type: a11y ♿ type: infrastructure 🤖 Issues relating to devops, tech debt, etc.
Projects
Archived in project
Archived in project
Development

No branches or pull requests

2 participants