Lighthouse or other accessibility testing on CI
Open
Nobody has claimed this yet.
accessibility
standardisation
technical debt
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Explore adding Lighthouse or other accessibility testing to CI so that after the workshop we make sure to always catch accessibility issues: https://developers.google.com/web/tools/lighthouse#programmatic
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's CI configuration and the linked Lighthouse programmatic-testing documentation. Compare Lighthouse with other accessibility-testing options, then define a CI check that runs after the workshop and reliably reports accessibility regressions; done means the check executes in CI and catches the intended issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100