Does QualityGate provide a legal conformance assessment?

No. It reports automated findings so teams can act on them earlier. Legal and conformance reviews still require qualified human judgment.

What happens to the issues that were already there?

Choose a regression gate to compare the scan against a matching baseline and apply severity limits to new findings. Existing and fixed findings remain visible. Absolute gates apply limits to every finding instead.

What can QualityGate check?

Ten bundles cover accessibility, the WCAG A/AA profile, page SEO, security headers, broken links, performance, exposed credentials, AI-search readiness and bounded deep SEO. full combines accessibility, SEO, security and links; advanced bundles run separately.

Where does the check run?

Run checks in GitHub, GitLab or Bitbucket CI against the deployed preview URL. You can also scan locally with the CLI or queue a public HTTPS target from the app. Private or authenticated targets require your own CI environment.

What does a failing check look like?

The pull request receives one comment listing the findings by severity against the limit you configured, plus the decision the gate reached. Nothing else in the workflow changes.

EAA accessibility / agency delivery

Ship with a clear quality decision.

Check accessibility and web quality on the deployed preview. Give your team and clients evidence before every release.

Start free See how it works

Automated checks find issues and track progress; they do not provide legal advice or a conformance assessment.

Check the actual previewScan the deployed page your reviewers open.
Make the gate explicitApply your project’s configured severity limits.
Share the evidenceReview findings in pull requests and client reports.

qualitygate-check

commented on pull request #418 · example

FAILED GATE

Signal Summary

2 serious findings exceed the configured limit

Scanned deploy-preview-418 and applied this project’s severity limit.

Findings by severity for this example scan
Severity	Found	Limit
Critical	0	0 allowed
Serious	2	0 allowed
Moderate	5	reported
Minor	9	reported

Show the 2 serious findings

SERIOUS button-name

Checkout icon button has no accessible name

/checkout · button.cart-submit

SERIOUS color-contrast

Sale badge text falls below the 4.5:1 contrast ratio

/checkout · span.badge-sale

Decision: failed gate. Two serious findings exceed the limit set for this project.

Built for your workflow GitHub Actions · GitLab CI · Bitbucket Pipelines

Scans the deployed preview, not a local approximation
Deterministic pass/fail against limits you configure
One clear result in the pull request, before the merge

How it works

From preview to a clear decision.

01
Connect your repository
Create a project and connect your CI workflow with a scoped project key.
02
Scan the deployed preview
Choose your check bundle and scan the URL attached to the pull request.
03
Review the quality decision
See the gate verdict, affected elements, and evidence before you merge.

Check the release. Follow the whole workflow.

From the preview URL to the pull request decision, QualityGate brings checks, policy and evidence together. Choose a bundle for each scan.

Accessibility

Automated accessibility checks and the WCAG A/AA profile. These checks are not a legal or conformance assessment.

a11y · ada

Release quality

Page SEO, security headers, broken links and exposed credentials. full combines accessibility, SEO, security and links; advanced scans run separately.

seo · security · links · full · secrets-exposure

Performance and search visibility

Lighthouse performance, deterministic AI-search readiness and bounded site-level SEO. No rankings or AI citations are guaranteed.

perf · geo · seo-deep

Ten scan bundles: Choose accessibility, release quality, performance and search visibility checks for each URL.
GitHub, GitLab and Bitbucket: Run checks in your CI pipeline and publish findings on pull or merge requests.
Regression gates: Compare against a baseline and gate changes on new findings or absolute severity limits.
Local CLI: Scan locally with text or JSON results and exit codes for automation.
Cloud scans: Queue public HTTPS scans from your project and follow their progress in the app.
Scheduled scans: Check projects on a recurring schedule using a separate monthly allowance.
Repository quality checks: Combine secret detection, lint, types, tests, build and PR policy with merge readiness.
Account access: Use email or GitHub, GitLab and Bitbucket sign-in, with connected methods and session controls.
Organizations and roles: Invite teammates, assign roles and switch between organization workspaces.
Project controls: Configure repositories, allowed hosts, default branches and scoped API keys.
Packages and usage: Review scan allowances, reserved runs and your subscription in the app.
Run history and findings: Review project trends, scan outcomes, selectors and guidance for individual findings.
Reports and client sharing: Export branded HTML and PDF reports. Paid packages add private client links; Agency adds custom report domains.
Email and Slack notifications: Receive gate failures, quota alerts and weekly digests through your configured channels.

For agencies and teams

Give clients evidence, not empty assurances.

Agencies find accessibility problems late, usually after a client review or an EAA question that arrives with a deadline. QualityGate moves the check to the moment the work is already on screen: the deployed preview attached to the pull request.

Explore the docs

CLIENT RELEASE REPORT / EXAMPLE

Preview release

Failed gate · 0 critical · 2 serious findings

Preview checked: deploy-preview-418
Findings: 0 critical · 2 serious
Gate decision: Failed gate

Branded HTML and PDF reports keep the evidence easy to share.

All the checks. Room to grow.

Every paid package includes all ten bundles. Choose your scan allowance and project capacity. Start with automated accessibility on Free.

Free

No subscription required

25 scans/month
5 scheduled scans/month
1 project

Accessibility bundle

Accessibilitya11y

Developer

Current price in the app

View current pricing in the app

100 scans/month
60 scheduled scans/month
3 projects
Private client report links

All ten bundles

Accessibilitya11y, ada
Release qualityseo, security, links, full, secrets-exposure
Performance and search visibilityperf, geo, seo-deep

Team

Current price in the app

View current pricing in the app

1,000 scans/month
300 scheduled scans/month
10 projects
Private client report links

All ten bundles

Accessibilitya11y, ada
Release qualityseo, security, links, full, secrets-exposure
Performance and search visibilityperf, geo, seo-deep

Agency

Current price in the app

View current pricing in the app

5,000 scans/month
1,500 scheduled scans/month
Unlimited projects
Private client report links
Custom report domain

All ten bundles

Accessibilitya11y, ada
Release qualityseo, security, links, full, secrets-exposure
Performance and search visibilityperf, geo, seo-deep

One scan covers one URL and bundle. full combines accessibility, SEO, security and links; performance, GEO, deep SEO and secrets scans run separately. Scheduled scans have their own monthly allowance. Manual cloud scans use the normal allowance.

Paid prices load from the current billing catalog. You can also view them in the app.

How packages and scan allowances work

Common questions

Know what your gate checks.

Does QualityGate provide a legal conformance assessment?: No. It reports automated findings so teams can act on them earlier. Legal and conformance reviews still require qualified human judgment.
What happens to the issues that were already there?: Choose a regression gate to compare the scan against a matching baseline and apply severity limits to new findings. Existing and fixed findings remain visible. Absolute gates apply limits to every finding instead.
What can QualityGate check?: Ten bundles cover accessibility, the WCAG A/AA profile, page SEO, security headers, broken links, performance, exposed credentials, AI-search readiness and bounded deep SEO. full combines accessibility, SEO, security and links; advanced bundles run separately.
Where does the check run?: Run checks in GitHub, GitLab or Bitbucket CI against the deployed preview URL. You can also scan locally with the CLI or queue a public HTTPS target from the app. Private or authenticated targets require your own CI environment.
What does a failing check look like?: The pull request receives one comment listing the findings by severity against the limit you configured, plus the decision the gate reached. Nothing else in the workflow changes.

Your next release