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

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

Component Accessibility Status: Automated Keyboard Navigation Tests #13748

sstrubberg opened this issue May 5, 2023 · 0 comments
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
2023 Q4

Comments

@sstrubberg
Copy link
Member

sstrubberg commented May 5, 2023 •
edited by tay1orjones
Loading

Acceptance criteria

  • Configure automated keyboard navigation tests for high value components

Tasks
Preview Give feedback
  1. AVT Keyboard Tests: Work with IBMa to audit and determine what components need keyboard avt tests #14513
    role: dev 🤖 type: a11y ♿
    guidari
  2. Add keyboard navigation AVT tests for each component #14522
    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.
@sstrubberg sstrubberg mentioned this issue May 5, 2023
Closed
@sstrubberg sstrubberg added type: infrastructure 🤖 Issues relating to devops, tech debt, etc. adopter: strategic-product Work-stream that directly effects the Product-led Growth initiative. type: a11y ♿ role: dev 🤖 and removed status: needs triage 🕵️‍♀️ labels May 5, 2023
@sstrubberg sstrubberg moved this to ⏱ Backlog in Design System May 5, 2023
@sstrubberg sstrubberg moved this from ⏱ Backlog to 🪆 Needs Refined in Design System May 5, 2023
@sstrubberg sstrubberg added this to the 2023 Q2 milestone May 5, 2023
@github-project-automation github-project-automation bot moved this to Triage in Roadmap May 10, 2023
@sstrubberg sstrubberg moved this from Triage to Now in Roadmap May 10, 2023
@tay1orjones tay1orjones modified the milestones: 2023 Q2, 2023 Q3 Jun 15, 2023
@tay1orjones tay1orjones mentioned this issue Jul 27, 2023
Closed
2 tasks
@tay1orjones tay1orjones mentioned this issue Aug 24, 2023
Closed
@sstrubberg sstrubberg modified the milestones: 2023 Q3, 2023 Q4 Oct 2, 2023
@tay1orjones tay1orjones moved this from 🪆 Needs Refined to 🏗 In Progress in Design System Oct 17, 2023
@tay1orjones tay1orjones added planning: umbrella Umbrella issues, surfaced in Projects views and removed status: blocked 🙅‍♀️ labels Oct 17, 2023
@github-project-automation github-project-automation bot moved this from Now to Completed in Roadmap Nov 16, 2023
@github-project-automation github-project-automation bot moved this from 🏗 In Progress to ✅ Done in Design System Nov 16, 2023
@sstrubberg sstrubberg mentioned this issue May 28, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Design System
Archived in project
Roadmap
Archived in project
Milestone
2023 Q4
Development

No branches or pull requests
2 participants
@tay1orjones @sstrubberg