-
Notifications
You must be signed in to change notification settings - Fork 9
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
GitHub Actions: Run accessibility checks on additional pages #1278
Comments
@machikoyasuda The other day you mentioned we are running Lighthouse checks, so I believe we can close this issue? |
@indexing This issue is referring to adding automation to run Lighthouse checks on every page on every PR. So far, we're only running it on the home page and the help page. Not sure if this Issue is a priority anymore though. |
@indexing To me, this seems like something that could be a 1-week |
@thekaveman What are you thoughts? Is it worth expanding the views we're checking via Lighthouse? |
I agree with @machikoyasuda this seems like a good exercise to timebox for a Stretch week. Generally it would be good to do more automated checking like this (I rarely if ever remember to run Lighthouse myself locally). Let's see what we can accomplish in a reasonable amount of time using just Cypress and one of the plugins above, but without worrying about mocking all the external services or getting through e.g. Login.gov just yet. |
Beginning preliminary research on this. May continue it into next week/stretch week. |
After extensive testing #1675 last week, I've come to the conclusion that, at this time, we shouldn't add the Steps we can take now:
Either way, we have to remember that automated testing only provides so much reassurance - and we'll always need some manual testing. And also, that certain accessibility issues (like color contrast) should be detected earlier at the design level. As an example, both of the aforementioned tools weren't able to catch that a button had insufficient color contrast - because aria was set to |
@machikoyasuda what do you think about closing this issue now that you've done the research and made recommendations? |
We currently run Lighthouse on a couple pages:
benefits/.github/workflows/tests-ui.yml
Lines 44 to 49 in f2503e5
It would be helpful to have it (or some other automated accessibility checker run against other pages as well.
Acceptance Criteria
Additional context
Some options:
The text was updated successfully, but these errors were encountered: