You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cypress-axe is a plugin for Cypress that integrates Axe-core, an accessibility testing engine, to automate web accessibility testing. It allows developers to run accessibility checks within their end-to-end Cypress tests, identify WCAG violations
As a developer,
I would like to be able to run a11y tests to check the a11y state of the components
to ensure their best quality.
Proposed Solution
For a first step manual on-demand run and simple report is completely enough.
On a second step, we can schedule regular runs.
Proposed Alternatives
No response
Organization
No response
Additional Context
No response
Priority
None
Privacy Policy
I’m not disclosing any internal or sensitive information.
The text was updated successfully, but these errors were encountered:
After syncing with accessibility experts, the following steps need to be taken:
Implement a reporting mechanism for manually preprocessing all accessibility issues, as some require validation.
Write accessibility tests separately to ensure comprehensive coverage, since testing accessibility only at the end may overlook certain scenarios. Additionally, Axe Core requires specific configurations in some cases due to browser limitations.
Feature Request Description
Background
cypress-axe is a plugin for Cypress that integrates Axe-core, an accessibility testing engine, to automate web accessibility testing. It allows developers to run accessibility checks within their end-to-end Cypress tests, identify WCAG violations
As a developer,
I would like to be able to run a11y tests to check the a11y state of the components
to ensure their best quality.
Proposed Solution
For a first step manual on-demand run and simple report is completely enough.
On a second step, we can schedule regular runs.
Proposed Alternatives
No response
Organization
No response
Additional Context
No response
Priority
None
Privacy Policy
The text was updated successfully, but these errors were encountered: