-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
a11y: Create Accessibility test suite using Cypress #8986
Labels
Milestone
Comments
Closed
Closed
nwmac
added
QA/None
and removed
QA/manual-test
Indicates issue requires manually testing
team/area1
Team Neo
labels
Dec 4, 2024
nwmac
changed the title
a11y test: preparation
a11y: Create Accessibility test suite using Cypress and Axe
Dec 4, 2024
nwmac
changed the title
a11y: Create Accessibility test suite using Cypress and Axe
a11y: Create Accessibility test suite using Cypress
Dec 4, 2024
This PR #12900 fits the issue |
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
We're looking at working on accessibility issues, such as #7968
Describe the solution you'd like
It's important that once the changes are made, we implement some a11y tests to make sure no new issues are introduced.
Since we already use Cypress for E2E testing, we could make use of the AXE plugin which allows to test for some WCAG standards such as
color-contrast
,heading-order
,image-alt
& `label.The first step would by to get the configuration ready to write those tests.
There is an Axe plugin for Cypress and also one from IBM (https://www.npmjs.com/package/cypress-accessibility-checker)
Also see: https://www.deque.com/blog/how-to-test-for-accessibility-with-cypress/
Additional context
AXE: The Standard in Accessibility Testing
WCAG: Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible.
The text was updated successfully, but these errors were encountered: