component-driven / component-driven/cypress-axe
Region landmark errors
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 641
- Forks
- 90
- Avg merge
- 6h 8m
- Merged PRs (30d)
- 1
Description
A few days ago I started to receive violations from our accessibility tests. The code for the markup has not changed so I am not sure why I all of a sudden started to receive these errors.
I was using version 0.12.2.
Here is a screenshot of the errors I am now receiving:-
I can fix the 2 HTML elements so that they are in more appropriate places in the markup.
But the tags (which have never sat inside any landmark HTML tag), do not seem to be able to be ignored..
So I have 2 questions.
- Was there some update a few days ago that might have introduced these new failures for me?
- Is there any way to ignore the tags (Akamai Edge side includes)?
Thanks
David
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 reported accessibility-test violations with cypress-axe 0.12.2; the issue provides only a screenshot and no file or test path. Done means identifying whether an update caused the landmark failures and determining whether ESI tags can be ignored, or documenting that no such option exists.
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
- 25/100