Regression-only web quality gate
A web quality gate your team won’t switch off.
QualityGate compares each preview with the existing baseline. New accessibility issues can block the pull request; known issues stay visible without stopping clean changes.
Automated checks report deterministic findings; your team keeps control of the release policy.
The problem
When every old issue is urgent, none of the output is useful. A gate without context creates alerts, not decisions.
Most web checks report the whole page on every run. Mature codebases get the same wall of failures, clean pull requests stay red, and developers learn to route around the tool.
pull/1042 · account settings
BLOCKEDHow it works
A clear answer on every PR.One check, three predictable steps.
- 01
Add the ActionAdd the Action
Use the preview URL from your pull request.Point QualityGate at the preview URL in your pull request workflow.
- 02
Scan the changeScan the change
Apply the configured severity limit.The runner checks the page, while the backend applies your configured gate.
- 03
Read the commentRead the decision
See only what is new and actionable.A concise PR comment shows what is new, what was already there, and what blocks.
qualitygate-check
commented on pull request #418
Accessibility regression gate
3 new issues in this pull request
The existing backlog stays visible. This decision is based only on findings introduced by the current change.
- Existing
- 47
- New
- 3
- Fixed
- 5
- Limit
- 0 critical
button-name Checkout icon button has no accessible name
/checkout · button.cart-submit
Decision: hold. One new critical issue exceeds the configured limit. Existing issues did not affect this decision.
The difference
Don’t make it worse. Gate the delta.
QualityGate keeps the existing backlog visible, but makes the merge decision from what this pull request changed. Teams keep shipping while the quality bar moves in one direction.
- Existing baseline
- 41 tracked
- New critical / serious
- 0 / 0
- Merge decision
- PASS
For engineering teamsBuilt for teams that need signal in CI
The web-quality delta, attached to the PR.Turn a scan into one reviewable release decision.
Show reviewers the new findings, keep the backlog visible, and enforce a predictable severity limit.Keep the full issue inventory for planning, show reviewers what the pull request introduced, and enforce deterministic severity limits without inventing another opaque score.
0 blocking regressions · merge can proceed
PULL REQUEST QUALITY DELTA / #1042
Pricing preview
Try the gate on one repository first.
Founding access starts with deterministic accessibility checks for one project. Engineering design partners help shape pull-request output, policy controls, and rollout guidance before final limits and pricing are set.
Founding access
One project, PR checks, deterministic decisions.
Engineering design partner
Bring a real CI workflow and help shape the developer experience.
Common questions
Useful automation, honestly framed.
- Does QualityGate provide a legal conformance assessment?
- No. It reports automated findings and helps teams track regressions. Legal and conformance reviews still require qualified human judgment.
- Will it fail every PR on legacy debt?
- No. The regression-only baseline means existing issues can stay visible without blocking work.
- What does the first version check?
- The MVP focuses on deterministic accessibility checks. SEO, headers, and links follow as modular checks.
QualityGate / early access
Give the next pull request a clear decision.Make web quality part of review, not another ignored report.
Start with the new regression. Keep clean changes moving.Block the new regression, keep the existing backlog visible, and give reviewers one deterministic result they can act on.