Verify
Know what a pull request could affect before it ships.
Guardian reads a pull request or a list of changed files and shows which Applications, pages and WCAG requirements it could affect, so you know what to re-check. It labels every link as confirmed or inferred, and never claims a change caused a problem.
Included in
Guardian comes with Business Pro and Enterprise Pro, for repositories connected through the Pallyfi GitHub App.
Pull request: update checkout form
- Checkout pageConfirmed
- Account settingsInferred
1.3.1 Info and Relationships3.3.2 Labels or Instructions
What Guardian does
Change impact
From a pull request or file list to the Applications, pages and requirements it touches.
What to re-check
A focused list of pages and criteria worth testing again, instead of everything.
On the pull request
Optionally, a Pallyfi Guardian check and one summary comment, updated in place, turned on per repository.
How it works
Step 1: Open a pull request
Or paste the files you changed.
Step 2: Read the impact report
Affected Applications, pages and WCAG requirements, each marked confirmed or inferred.
Step 3: Re-check what matters
Scan the pages it points to before or after you merge.
What it does, and what it doesn’t
Accessibility evidence only helps when it’s honest about its limits.
- Does: Separates what it confirmed from what it inferred.
- Does: Keeps one report per commit, so you can see how a change evolved.
- Doesn’t: Doesn’t fail or block your build: its check is informational.
- Doesn’t: Doesn’t scan automatically or check preview deployments yet.
- Doesn’t: Doesn’t say a change caused a violation.
Part of one connected workflow
Pallyfi’s products share the same evidence, so a finding moves from discovery to a verified fix without being re-entered.
Start with your own site.
Free to start. Paid plans include a 7-day trial, once per account; your card is charged only when it ends.