Automated findings
Detected on the intentionally broken demo page.
Client-safe demo
AccessPatch Demo Report
A public-safe summary of what the local proof report demonstrates. Raw reports stay in the private project workspace unless a client-safe copy is reviewed first.
Executive summary
What the controlled demo proves.
Safe fixes
Deterministic fixes with enough source context.
Edit groups
Grouped patch suggestions for developer review.
Fixed demo issues
The controlled fixed demo scans clean for automated issues.
Developer handoff
Source-code patch context, not an overlay promise.
AccessPatch separates safe deterministic fixes from review-required and manual-only findings. The developer gets a report and patch context; semantic and legal judgment stay human.
Before / after
The demo is useful because it is narrow.
Before
Broken demo page with predictable issues such as missing names, missing title/lang, image alt review, and contrast review.
After
Controlled fixed demo page with automated issues cleared while manual-review boundaries remain explicit.
Boundary
Automated testing cannot prove full WCAG/legal compliance. AccessPatch identifies automatically detectable issues and suggests or applies safe fixes. Manual review remains required.