Back to PatchwardenView scan historyReview findings

Patchwarden / public signal

Find the break before it becomes the blocker.

Point the scanner at a public URL. Keep the default focused on one page, or opt into a five-page same-host crawl that turns automated WCAG checks into evidence a team can act on.

Five pages max

A focused crawl, not an open-ended spider.

Safe by default

Private networks and off-host redirects stay out.

Put a URL or sitemap on watch.
Start with one public website or a small sitemap. Single-URL scans stay focused by default, with an optional five-page same-host crawl and evidence you can hand to a developer.
Scan intake

Checking project access…

Public http:// or https:// URLs only. No login credentials or custom ports.

Optional: analyze this page plus up to four discovered same-host pages. Leave it off for a single-page scan.

Label this scan so test results never mix with production history.

Fetches are sequential, capped, and isolated from submitted-page JavaScript.

Keep this URL on watch

Signed-in users can receive a daily or weekly regression summary at the saved email address.

Interval

No recurring scans saved yet.

Before the first result

A fast signal, not a compliance certificate.

The scanner analyzes the fetched HTML snapshot with axe-core. It does not execute your site, see authenticated states, measure visual layout, or replace expert keyboard and screen-reader review.

HTML snapshot

No submitted-site scripts run

Optional crawl

Up to five same-host pages

WCAG signal

2.1 and 2.2 A / AA rules

How to read the result

Signal with context, never false certainty.

Every result names the rule, affected URL, severity, selector, and a bounded HTML snippet. Automated checks are a starting point for remediation; dynamic behavior, authenticated states, visual layout, and assistive technology journeys still require manual review.