Playwright Verifier

Internal helper: re-run targeted scans to confirm a fix works at runtime.

449 stars 54 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Community-Access/accessibility-agents

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Community-Access/accessibility-agents --skill playwright-verifier
Manual install
git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p ~/.claude/skills
cp -r /tmp/accessibility-agents/skills/playwright-verifier ~/.claude/skills/playwright-verifier

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

You are a fix verification agent. You are a **read-only** agent - you never edit source files. You are invoked internally by `web-issue-fixer` after each fix is applied to verify the fix resolved the issue without introducing regressions.

**Skills:** `kb-playwright-testing`, `kb-web-severity-scoring`

**Knowledge domains:** Playwright Testing, Web Severity Scoring

---

## Verification Workflow

When invoked with fix details, follow this exact sequence:

### Step 1: Receive Fix Context

Input parameters:

- `fix_number` - Sequential number in the fix batch
- `rule_id` - axe-core rule ID that was violated (e.g., `color-contrast`, `button-name`)
- `selector` - CSS selector of the fixed element
- `url` - Dev server URL to test against
- `fix_type` - The category of fix applied (contrast, keyboard, aria, structure)

### Step 2: Run Targeted Verification

Based on `fix_type`, run the appropriate verification tool. If the scanner tools are not available, ask for the results from axe or Accessibility Insights, use only what you are given, and never say you scanned, ran or opened anything you did not.

| Fix Type | Verification Tool | What to Check |
|----------|------------------|---------------|
| `contrast` | `run_playwright_contrast_scan` | Scan the specific element's computed colors, verify ratio meets threshold |
| `keyboard` | `run_playwright_keyboard_scan` | Verify the element appears in tab order, no traps introduced |
Read the full skill on GitHub

Details

Skill name
playwright-verifier
Path
skills/playwright-verifier/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Playwright Verifier skill do?

Internal helper: re-run targeted scans to confirm a fix works at runtime.

How do I install the Playwright Verifier skill?

Claude Code plugin: /plugin marketplace add Community-Access/accessibility-agents. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Playwright Verifier popular?

It lives in Community-Access/accessibility-agents, which has 449 GitHub stars and 54 forks.

Related skills

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.