Review existing a11y tests

Open
  • Is something wrong?
#398 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
playwright, typescript
Domain
accessibility, frontend, testing-qa

Research direction

Start by running the existing Playwright test suite and locating the accessibility specifications for the main pages. Review how keyboard navigation and focus are currently tested, then extend the relevant tests to cover tabs, menus, trees, and one tab-through check per main page. Done means every listed control is verified as reachable with visible focus and no keyboard trap, arrow-key behavior is covered, and the updated tests run successfully in CI.

Written by the indexing model from the issue text.

Description

  • One Playwright test per main page: tab through it, check that every control is reachable, has visible focu and that there's no trap.
  • Arrow-key navigation in the tabs, menus and tree.
  • Improve a11y tests for keyboard nav coverage
  • Fix remaining issues
  • Run automated tests in ci
Dominant language
TypeScript
Stars
1
Forks
1
Avg merge
2d 16h
Merged PRs (30d)
39

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/cockpit

All issues in stackabletech/cockpit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.