component-driven / component-driven/cypress-axe
Configure includedImpacts in cy.configureAxe instead of cy.checkA11y
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 641
- Forks
- 90
- Avg merge
- 6h 8m
- Merged PRs (30d)
- 1
Description
It is now possible to use a custom includedImpacts key in the cy.checkA11y() function. Is it possible to use this key in cy.configureAxe()?
Such as:
cy.configureAxe({
includedImpacts: ['critical']
})
or
cy.configureAxe({
rules: [{ id: 'includedImpacts', value: ['critical'] }]
})
This would avoid some duplication.
Contributor guide
No contributing guide indexed for this repository
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 comparing the cy.configureAxe() and cy.checkA11y() entry points, focusing on how includedImpacts is currently accepted by cy.checkA11y(). Determine whether cy.configureAxe() can accept the same option or rules form, and consider the change complete when configuration avoids the described duplication and the existing checks still behave correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, typescript
- Domain
- accessibility, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100