rohitmengji/RegLayer Accessibility Gate
Scan your deployed URL for accessibility issues and gate PRs on compliance thresholds
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jul 9, 2026
- License
- None
Pinned Snippet
uses: rohitmengji/reglayer@3c2e04cbfbb17b160ed10d629b0def721eecf63b # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| api-key | Your RegLayer API key (from Settings → API Keys) | yes | — |
| url | The URL to scan for accessibility issues | yes | — |
| fail-on-score | Fail if accessibility score drops below this threshold (0-100) | no | 80 |
| fail-on-critical | Fail if critical violations exceed this count | no | 0 |
| fail-on-serious | Fail if serious violations exceed this count | no | 3 |
| reglayer-url | RegLayer instance URL (default: https://reglayer.com) | no | https://reglayer.com |
Outputs
| name | description |
|---|---|
| passed | Whether the accessibility gate passed (true/false) |
| score | The accessibility score (0-100) |
| violations | Total number of violations found |
| critical | Number of critical violations |
| report-url | Link to the full scan report on RegLayer |