cypress-axe VS jest-axe

If you’re setting up automated tests (and you probably should), you can even integrate axe with Cypress

The same engine can be used with Cypress, thanks to the cypress-axe package. It adds several custom commands to the Cypress API, which utilizes “axe-core” under the hood. It makes it possible to perform a11y audits directly while testing.

Cypress

Luckily for us, there’s a new player in town. Cypress is a great tool that provides us with a modern solution for creating, running and maintaining code. Combined with Cypress Testing Library and the accessibility audit tool aXe, you’ll have all the tools you need to gain confidence in your application, and to never deal with manual verifications in prod ever again.

Maybe: https://github.com/component-driven/cypress-axe/issues/82

I usually use a combination of Storybook + Chromatic, Cypress, and Jest + Testing Library + jest-axe. Fairly standard, I think? (Aside from Chromatic, but that's mainly for convenience)

And finally, we can use a cool library called jest-axe. You can use it to assert that your component doesn’t have any accessibility violations:

How to test accessibility issues? Use Jest-axe ​GitHub - nickcolley/jest-axe: Custom Jest matcher for aXe for testing accessibility ♿️🃏​

Tests are another place where plugins can bring more accessibility insights. I've used two, depending on the test setup: jest-axe and cypress-axe. They both add axe-core, Deque's testing solution to the testing environment.