Open heybran opened 9 months ago
Would it be helpful to add this kind of code directly to the repo for you to more easily use them on Pods itself?
At the moment, it's easier for me to do it on a separate local repo, but it would make sense to move these test specs into Pods code base in future.
Problem to Solve
Hey @sc0ttkclark
I want to automate my accessibility testing on Pods (moving on from manual testing that I did before today) with
Cypress
andcypress-axe
. And, I have created a repo for me to store testing files, a single test file looks like this: https://github.com/heybran/pods-a11y-tests/blob/main/cypress/e2e/edit-pod-screen/add-new-group.cy.jsSo I need to create an new issue to share the accessibility reports from Cypress and then move on to fix those issues.
Manage pods screen
1. Color contract
2. Link accessible name
Edit pod screen
1. Accessible name
2. Color contract
3. nested-interactive
Edit pod screen - add new group
1. Accessible name
2. aria-required-children
3. Ensures all ARIA attributes have valid values
4. Color contract
5. Heading order
TODO: Will have more reports once more testing specs are run
Proposed Solution
I will go through them one by one and fix them.