ReadMeFeed / Community knowledge

#cypress-axe

Real questions. Useful conversations. Find the people who know your stack.

Question1 answer4,362 followingPosted 02 Aug 2023, 19:27 UTC141K views2,571 votes

cypress-axe Test Runner Reporting Lacks Structured Violation Details

Context Cypress delegates accessibility auditing to the cypress-axe plugin, which wraps axe-core . The standard workflow requires calling cy.injectAxe() once per test context before invoking cy.checkA11y() against the current DOM state. While the command executes and surfaces violations, the Test Runner presents them as generic assertion failures rather than

Community & Careers · Editorial question

Community & Careers

Question1 answer4,353 followingPosted 11 Aug 2021, 23:00 UTC104.1K views2,165 votes

owner answered

Re‑auditing dynamic content: cy.wait vs cy.intercept

The goal is to capture all accessibility violations that appear after a page has loaded dynamic content, such as components rendered by API calls or client‑side routing. cypress‑axe injects axe‑core and exposes cy.axeCheck() , which audits the DOM snapshot at the moment it is invoked. By default, it does not re‑audit automatically after asynchronous updates,

Community & Careers · Editorial question

cypressio dynamic-content cypress-axe