component-driven / component-driven/cypress-axe
Cypress axe don't recognize level-one heading after open datepicker
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 641
- Forks
- 90
- Avg merge
- 6h 8m
- Merged PRs (30d)
- 1
Description
I have a page with a datepicker, after opening the datepicker and trying to check A11Y in the page, I get the error "Page must contain a level-one heading", but the page has an h1, but the cypress-axe just see the HTML inside de datepicker, this is a bug or the expected behavior?
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 accessibility check after opening the datepicker in Cypress, using the page's existing h1 and the datepicker HTML shown in the report. Compare the HTML inspected by cypress-axe with the full page and determine whether the missing level-one heading is expected; done means the behavior is clarified or corrected and the scenario is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, typescript
- Domain
- accessibility, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100