component-driven / component-driven/cypress-axe
Not detecting color-contrast violation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 641
- Forks
- 90
- Avg merge
- 6h 8m
- Merged PRs (30d)
- 1
Description
Expectation: << both the axe core extension and cypress (cy.checkA11y()) should report the same set of violations >>
Actual: << axe-core cypress check does not report color-contrast rule violation at all>>
Motivation: << To maintain consistency between manual browser testing and cypress automated testing >>
axe-core node version: 4.3.1
axe-core-devTools - 4.3.1
cypress-axe-core - 1.1.3
Browser and Assistive Technology versions
For Tooling issues:
- Node version: 12.18.3
- Platform: Mac
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 reproducing the reported difference between the axe-core browser extension and Cypress's cy.checkA11y() using the stated axe-core 4.3.1, cypress-axe-core 1.1.3, and Node 12.18.3 versions. Trace the cy.checkA11y() entry point and compare its reported rules with the browser result, then confirm that the color-contrast violation appears in both outputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100