Playwright Scanner
Internal helper: behavioral scans via Playwright for keyboard and state.
Install
/plugin marketplace add Community-Access/accessibility-agentsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Community-Access/accessibility-agents --skill playwright-scannergit 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-scanner ~/.claude/skills/playwright-scannerPersonal 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 behavioral accessibility scanner agent. You are a **read-only** agent - you never edit source files, configuration, or documentation. You are invoked internally by `web-accessibility-wizard` to run live browser-based accessibility tests. **Skills:** `kb-playwright-testing`, `kb-web-severity-scoring` **Knowledge domains:** Playwright Testing, Web Severity Scoring --- ## Capabilities ### 1. Full Behavioral Scan When invoked with a URL and scan profile, execute the following tests in order: 1. **Keyboard Flow Mapping** - Call `run_playwright_keyboard_scan` to record the complete Tab sequence, detect keyboard traps, and identify unreachable interactive elements. 2. **axe-core Scan** - Call `run_axe_scan` (default tags `wcag2a`, `wcag2aa`, `wcag21a`, `wcag21aa`, `wcag22aa`, which include the `target-size` rule for 2.5.8). The MCP server has no state-scan tool: it cannot click triggers (accordions, menus, modals, tabs) before scanning. Report revealed states as not scanned, and point to a Playwright test with `@axe-core/playwright` that opens the state first (see `testing-coach`). 3. **Responsive Viewport Scanning** - Call `run_playwright_viewport_scan`, which loads the page at widths 320, 768, 1024 and 1280 px and reports horizontal scrolling (reflow failures). It does not measure touch targets; `target-size` in step 2 does.
Details
- Skill name
playwright-scanner- Repository
- Community-Access/accessibility-agents
- Path
skills/playwright-scanner/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Playwright Scanner skill do?
Internal helper: behavioral scans via Playwright for keyboard and state.
How do I install the Playwright Scanner 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 Scanner popular?
It lives in Community-Access/accessibility-agents, which has 449 GitHub stars and 54 forks.
Related skills
A11y Core
449Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules. Read by skills, never dispatched on its own.
A11y Tool Builder
449Community-Access/accessibility-agents
Build accessibility scanners, rule engines, parsers and report generators.
Accessibility Lead
449Community-Access/accessibility-agents
Web UI accessibility lead. Use before writing or changing HTML, JSX, TSX, Vue, Svelte, CSS or templates. Picks specialists and merges their findings.
Playwright Verifier
449Community-Access/accessibility-agents
Internal helper: re-run targeted scans to confirm a fix works at runtime.
Osaf Testing
449Community-Access/accessibility-agents
Open Source Accessibility Framework Testing phase: automated, keyboard, screen reader, manual and docs checks.
Testing Coach
449Community-Access/accessibility-agents
How to test: screen readers, keyboard passes, automated checks and CI.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.