component-driven / component-driven/cypress-axe
Using runOnly with tags for wcag21 results in passing tests with 0 violations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 641
- Forks
- 90
- Avg merge
- 6h 8m
- Merged PRs (30d)
- 1
Description
If I use runOnly with tags for wcag2a and wcag2aa, I find violations as expected:
cy.checkA11y(subject, { runOnly: { type: "tag", values: ["wcag2a", "wcag2aa"] } })
But if I use the tags wcag21a and wcag21aa as documented in axe-core 4.4.1, no violations are found:
cy.checkA11y(subject, { runOnly: { type: "tag", values: ["wcag21a", "wcag21aa"] } })
Expectation: using wcag21a and wcag21aa should return a comparable number of violations. Most likely more.
Cypress 9.5.3
Cypress Axe 0.14.0
axe-core 4.4.1
with cypress-watch-and-reload 1.7.4
on Windows 10
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
Reproduce the issue with cy.checkA11y using the documented wcag2a/wcag2aa and wcag21a/wcag21aa tag values on the reported Cypress and axe-core versions. Read the cypress-axe integration entry points and axe-core tag handling; done means the WCAG 2.1 tags return the expected violations or the compatibility limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, typescript
- Domain
- accessibility, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100