Playwright Verifier logo

Playwright Verifier

Organization
Community-Access
playwright-verifier

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

Overview

PublisherCommunity-Access
Repositoryaccessibility-agents
Skill nameplaywright-verifier
Stars
429
Forks
51
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Community-Access on GitHub. Read the source before you install it.

Installation

Install the Playwright Verifier AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Community-Access/accessibility-agents/tree/main/skills/playwright-verifier
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
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
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Playwright Verifier in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Playwright Verifier on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Playwright Verifier is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

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:

Fix TypeVerification ToolWhat to Check
contrastrun_playwright_contrast_scanScan the specific element's computed colors, verify ratio meets threshold
keyboardrun_playwright_keyboard_scanVerify the element appears in tab order, no traps introduced
ariarun_playwright_a11y_treeVerify the element's role, name, and state in the accessibility tree
structurerun_playwright_a11y_treeVerify heading hierarchy, landmark structure
staterun_playwright_state_scanVerify dynamic content is accessible after interaction
viewportrun_playwright_viewport_scanVerify reflow and touch targets at all widths

Step 3: Determine Verdict

Compare pre-fix and post-fix results:

  • PASS — Original violation is absent and no new violations were introduced
  • FAIL — Original violation is still present (fix didn't work)
  • REGRESSION — Original violation is absent but new violations were introduced

Step 4: Report Results

text
FIX VERIFICATION #{fix_number}
Rule: {rule_id}
Selector: {selector}
Verdict: {PASS|FAIL|REGRESSION}

{If FAIL}
  Original violation still present.
  Current state: {element's current accessibility state}

{If REGRESSION}
  Original violation fixed, but new issues found:
  - {new_violation_1}
  - {new_violation_2}

{If PASS}
  Fix verified successfully.

Test Code Generation

After a verified PASS, generate a Playwright test that encodes the assertion for regression prevention:

javascript
// Generated by playwright-verifier for fix #{fix_number}
import { test, expect } from '@playwright/test';
import AxeBuilder from '@axe-core/playwright';

test('{rule_id} — {selector} should pass', async ({ page }) => {
  await page.goto('{url}');
  const results = await new AxeBuilder({ page })
    .include('{selector}')
    .withRules(['{rule_id}'])
    .analyze();
  expect(results.violations).toEqual([]);
});

For keyboard fixes, generate keyboard navigation tests:

javascript
test('keyboard: {selector} is reachable via Tab', async ({ page }) => {
  await page.goto('{url}');
  let found = false;
  for (let i = 0; i < 100; i++) {
    await page.keyboard.press('Tab');
    const focused = await page.evaluate(() => {
      const el = document.activeElement;
      return el?.matches('{selector}') || false;
    });
    if (focused) { found = true; break; }
  }
  expect(found).toBe(true);
});

Graceful Degradation

If Playwright is not installed:

  • Report that live verification is unavailable
  • Suggest the fix is "unverified" and should be manually tested
  • Provide the install command for future use

Batch Verification

When verifying multiple fixes, maintain a running tally:

text
VERIFICATION SUMMARY
====================
Total Fixes: {n}
Verified PASS: {n}
FAIL: {n}
REGRESSION: {n}
Skipped (no Playwright): {n}

Output contract

Return only JSON matching skills/a11y-core/schemas/findings.schema.json. No prose, no summary, no restated instructions. One object, one array of findings.

Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md. Authoritative specifications for this skill: skills/a11y-core/references/sources.md.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Playwright Verifier AI skill do?

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

Why use Playwright Verifier on TypingMind?

Because you install it once and use it with any model. Playwright Verifier is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Playwright Verifier in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Community-Access/accessibility-agents/tree/main/skills/playwright-verifier. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Playwright Verifier?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Playwright Verifier?

As many as you like. As long as a model supports skills, you can use Playwright Verifier with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Playwright Verifier AI skill free?

Yes. It is published on GitHub by Community-Access under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇