run_verification_suite
Test a proposed accessibility patch (search/replace and CSS selector) against a live URL in a sandboxed browser before committing. Compares axe-core scores before and after, returns score delta and rule pass.
Instructions
[audit] PRE-deploy patch verification: test a proposed patch (search/replace + CSS selector) against a live URL in a sandboxed browser BEFORE you commit. Runs before/after axe-core, returns score delta + rule pass. vs verify_fixes: that's POST-deploy URL-vs-baseline comparison; this is patch-vs-live in isolation.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| patch_id | No | ID of a previously generated patch to verify (not yet supported) | |
| patch_content | No | Inline patch content for verification | |
| url | Yes | URL to verify the patch against — must be a live, reachable page (the verifier renders it in a headless browser). | |
| selector | Yes | CSS selector of the element that had the original issue. HOW TO GET IT: (1) call get_findings(audit_id, finding_id) — returns finding.selector directly; (2) or call explain_finding(finding_id) which includes the element selector and context; (3) or read finding.node.target[0] from an axe-core finding. Required — the verifier scopes the before/after check to this element. | |
| rule_id | No | Axe-core rule ID to check is fixed (e.g., 'color-contrast', 'button-name', 'link-name'). When omitted, all rules on the selector element are checked. Strongly recommended for precise pre-deploy verification — source it from `finding.rule` in the audit response. | |
| timeout_ms | No | Verification timeout in milliseconds (default: 60000, max: 120000) |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |