dusk-network / dusk-network/duskit
Investigate automated accessibility testing for components
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
There are libraries like jest-axe to do just that, but don't know how
this one behaves with vitest.
Notes:
- search for alternatives too
- jest-axe hasn't been updated in a while
- there is a vitest-axe fork, but its last update is even older than the last jest-axe one
Seems we can just use axe-core instead.
Investigate also @storybook/addon-a11y.
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 by reviewing the project's Vitest component-testing setup, then compare axe-core with the referenced @storybook/addon-a11y approach. The investigation is complete when it identifies a compatible automated accessibility-testing approach and records the recommendation for this repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100