Accessibility quality gates for publishing decisions

Accessibility quality gates turn a completed scan into a decision your CMS or release pipeline can consume. Configure blocking severities, finding ceilings, a baseline scan, and manual acknowledgement while preserving the reasons beside the decision.

For platforms that need a governed allow, warn, or block step before publication

Illustrative quality-gate decisionIllustrative
DecisionindeterminateRequired manual checklist acknowledgement is pending
Block on
blocker · critical
New only
true
Max major new
3
Manual acknowledgement
required
Rules
Severity · count · rule · new-only
States
Passed · failed · indeterminate · not configured
Governance
Suppression actor · reason · expiry

Express publishing policy as inspectable configuration.

The gate records why it reached a decision, so an editor or developer can recover without reverse-engineering a score.

Blocking severities
blocker, critical
Finding ceilings
Per severity or normalized rule
Baseline mode
All findings or newly introduced only
Manual acknowledgement
Optional workflow requirement
Suppressions
Actor, reason, and optional expiry
Result
Decision plus machine-readable reasons

Let each outcome travel to the owner who can decide it.

A useful gate does not force deterministic failures, partial signals, and human evaluation into the same pass/fail bucket.

Stop

Machine failure

  • Threshold crossed
  • Evidence attached
  • Build reacts
Review

Indeterminate work

  • Partial coverage
  • Owner assigned
  • Release policy applies
Continue

Configured gate clear

  • No new blockers
  • Record retained
  • Human work still visible

Choose the technical profile behind this capability.

A gate can act only on coverage the selected profile defines. Keep manual requirements and unsupported conditions outside automatic pass decisions.

Put the gate where content changes state.

The same result can drive a document upload, a web release, or an agency approval queue without changing the finding model.

  1. CMS

    Hold an uploaded asset

    Warn or block before a PDF or DOCX becomes public.

  2. CI/CD

    Protect a release

    Fail a check when newly introduced findings cross the project threshold.

  3. Agency

    Route an exception

    Record the owner, justification, expiry, and retained evidence.

Turn configured thresholds into inspectable publishing decisions.

Create a free project, choose a profile, and test a warning or blocking threshold against results your team can inspect.

Check a website freeCreate an account

Automated preflight is not an accessibility certification or legal determination.