Orange-OpenSource / Orange-OpenSource/Orange-Boosted-Bootstrap
Add a new `htmlcs` runner to `pa11y-ci`
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 219
- Forks
- 61
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 12
Description
Prerequisites
- I have searched for duplicate or closed feature requests
- I have read the contributing guidelines
Proposal
Add a runner to pa11y-ci since it could detect some errors that aXe doesn't detect.
The remaining errors may be fixed from https://github.com/twbs/bootstrap/pull/38219.
Motivation and context
Have a better ci. It's not much work compared to what it can detect and avoid. Seems to have a better algorithm to detect color issues. Following #938 to ensure that it won't break.
According to a11y expert, it's better to have as much test as possible since the algorithm are different and can be a bit more accurate to some points. Furthermore, it doesn't add much work to make it work.
Following the closure of #1677
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 how pa11y-ci runners are integrated and compare the existing aXe runner with the proposed htmlcs runner. Read the context in #938 and #1677, then verify the runner against the repository’s accessibility checks. Done means htmlcs runs in CI alongside aXe without breaking the existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html, javascript
- Domain
- accessibility, ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100