What it does: scans every pull request for WCAG 2.1 / 2.2 AA accessibility violations using axe-core 4.11 and, optionally, generates source-code fix diffs via Claude Sonnet. Posts a sticky PR comment with findings; exits non-zero at a configurable severity threshold so you can require it as a merge check.
Why this list / this section: it's a static analyzer for HTML/CSS accessibility, same category as the PHPStan / tfsec / GraphQL Inspector entries right above it. Composite Action, published to GitHub Marketplace as axle-accessibility-compliance-ci.
Differentiator from "accessibility overlay" widgets (which don't belong on this list): axle never injects runtime JavaScript. It scans, suggests source-code diffs in the PR comment, and lets your merge button decide. Overlay widgets were the subject of the $1M FTC settlement against accessiBe in January 2025.
Happy to adjust wording / placement if another section fits better.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/sdras/awesome-actions/pull/772
**Author:** [@asafamos](https://github.com/asafamos)
**Created:** 4/20/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `main`
---
### 📝 Commits (1)
- [`ee25202`](https://github.com/sdras/awesome-actions/commit/ee25202604a21d7b4b49b8356a8cf286f87fd1a7) Add axle (accessibility compliance CI)
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
Adds [axle](https://github.com/asafamos/axle-action) to the Static Analysis section.
**What it does:** scans every pull request for WCAG 2.1 / 2.2 AA accessibility violations using axe-core 4.11 and, optionally, generates source-code fix diffs via Claude Sonnet. Posts a sticky PR comment with findings; exits non-zero at a configurable severity threshold so you can require it as a merge check.
**Why this list / this section:** it's a static analyzer for HTML/CSS accessibility, same category as the PHPStan / tfsec / GraphQL Inspector entries right above it. Composite Action, published to GitHub Marketplace as `axle-accessibility-compliance-ci`.
**Differentiator from "accessibility overlay" widgets (which don't belong on this list):** axle never injects runtime JavaScript. It scans, suggests source-code diffs in the PR comment, and lets your merge button decide. Overlay widgets were the subject of the $1M FTC settlement against accessiBe in January 2025.
Happy to adjust wording / placement if another section fits better.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/sdras/awesome-actions/pull/772
Author: @asafamos
Created: 4/20/2026
Status: 🔄 Open
Base:
main← Head:main📝 Commits (1)
ee25202Add axle (accessibility compliance CI)📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
Adds axle to the Static Analysis section.
What it does: scans every pull request for WCAG 2.1 / 2.2 AA accessibility violations using axe-core 4.11 and, optionally, generates source-code fix diffs via Claude Sonnet. Posts a sticky PR comment with findings; exits non-zero at a configurable severity threshold so you can require it as a merge check.
Why this list / this section: it's a static analyzer for HTML/CSS accessibility, same category as the PHPStan / tfsec / GraphQL Inspector entries right above it. Composite Action, published to GitHub Marketplace as
axle-accessibility-compliance-ci.Differentiator from "accessibility overlay" widgets (which don't belong on this list): axle never injects runtime JavaScript. It scans, suggests source-code diffs in the PR comment, and lets your merge button decide. Overlay widgets were the subject of the $1M FTC settlement against accessiBe in January 2025.
Happy to adjust wording / placement if another section fits better.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.