oxidecomputer / oxidecomputer/console
a11y testing with Axe
Open
Nobody has claimed this yet.
a11y
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
Should be pretty easy. We can loop through a list of URLs and run the check on each.
https://github.com/dequelabs/axe-core-npm/blob/develop/packages/playwright/README.md
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked axe-core Playwright README to understand the proposed accessibility check. Identify the project's list of URLs and Playwright entry point, then run the check for every URL; done means each listed URL is covered and the results are reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- playwright, typescript
- Domain
- accessibility, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100