component-driven / component-driven/cypress-axe
cypress-axe fewer issues than the Axe Coconut browser plugin
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 641
- Forks
- 90
- Avg merge
- 6h 8m
- Merged PRs (30d)
- 1
Description
cypress-axe finds only a subset of issues found by the Axe Coconut browser plugin. For example, the browser plugin found 57 issues for one page, whereas cypress-axe found only 28 issues. Is there any particular reason for this? Note that I am running the checkA11y function with the default settings. Since they both run axe-core, I'm puzzled as to the discrepancy.
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 reviewing the checkA11y function's default settings and comparing the axe-core execution context used by cypress-axe with the Axe Coconut browser plugin. Reproduce the reported 57-versus-28 discrepancy, identify the cause, and document or test the expected matching behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, typescript
- Domain
- accessibility, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100