a11y-specialist-skills plugin

A six-skill accessibility plugin: page review, WCAG 2.2 audit with Playwright, audit planning and an improvement roadmap.

  • 61 ★ on the repository
  • Last commit
  • MIT
Plugin

Extended access

Why this level

  • The audit scripts open pages in a Playwright browser and run check code on your machine.
All reasons and checks

masup9/a11y-specialist-skills

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add plugins/a11y-specialist-skills

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The audit scripts open pages in a Playwright browser and run check code on your machine.

This is third-party code. Review the repository files before installing.

What it does

The plugin for Claude Code and Codex gives an agent a method for accessibility checks against WCAG 2.2 and WAI-ARIA APG. The `reviewing-a11y` skill examines pages, components, mockups and specifications and returns findings at three levels, critical, major and minor, with the WCAG criterion and a suggested fix. `auditing-wcag` runs an AA conformance audit in four phases: automated axe-core and Playwright script checks, interactive checks, manual checks and content review. The scripts rely on the `@a11y-skills/audit` npm package from the same repository. The other skills build an audit plan by the WAIC method, an improvement roadmap with a maturity assessment and KPIs, and look up the right criteria in the knowledge base while building UI.

Who it is for. Front-end developers and accessibility specialists who need a repeatable WCAG 2.2 AA audit rather than a one-off eyeball check.

Good fit when

  • Before a release a page must be checked for focus, 320 pixel reflow and target size.
  • A dropdown menu is built to APG and the agent must know the required roles and keys.
  • An organization needs an audit plan: representative page selection and an automated versus manual split.
  • An accessibility roadmap with a maturity assessment and KPIs is needed.

Not a fit when

  • A legal verdict on conformance is needed: automated checks cover only part of the criteria and people verify the rest.
  • A project targets another standard, for example EN 301 549 without WCAG mapping.
  • An audit is needed without installing a browser: the Playwright scripts require one.

Example request

Run a WCAG 2.2 AA audit for https://example.com and list separately the items that need manual checking.

Limitations

The axe-core and Playwright automated checks cover only part of the WCAG criteria, so reports keep items for manual verification. The audit scripts need Node.js and a browser installed by Playwright. The Codex plugin is marked as the recommended path, while a standalone skill install needs a repository clone and a symlink into `~/.claude/skills` or `~/.agents/skills`. The `a11y-knowledge` base is used by the other skills and is not meant to be run on its own. A Japanese README is available.

How to disable. Remove the plugin through `/plugin` in Claude Code or the Codex plugin list. For a symlink install, delete the links from the skills directory.

FAQ

How do I install the plugin in Claude Code?

Run `/plugin marketplace add masuP9/a11y-specialist-skills`, then `/plugin install a11y-specialist-skills@a11y-specialist-skills`.

How do I install it in Codex?

Add the catalog with `codex plugin marketplace add masuP9/a11y-specialist-skills`, start `codex` and install the plugin from the `/plugins` list.

How do I call a skill manually?

In Claude Code with `/reviewing-a11y`, in Codex with `$reviewing-a11y`. Agents also activate the skill on phrases such as "check accessibility".

What do the automated scripts check?

Focus indicators, reflow at 320 pixels, line and letter spacing, target size and other WCAG 2.2 criteria.

Can I take the checks into my own project?

Yes, they are published as the npm package `@a11y-skills/audit`: `npm install -D @a11y-skills/audit` plugs them into your Playwright project.

Discussion

No questions or reviews yet.

Plugins

Over 30 accessibility skills, one per topic: forms, keyboard, contrast, ARIA, CI, manual testing and axe rules.

SkillMinimal access60Repository stars

A Claude Code plugin for UX regression testing that walks user journeys in a live app and returns a ranked fix plan.

PluginExtended access59Repository stars

MCP Accessibility Scanner runs axe checks, exercises keyboard focus and saves accessibility reports for web pages

MCP serverExtended access59Repository stars

Seven QA agents and ten skills for test automation: Playwright in TypeScript, Selenium in Java, API, accessibility and ISTQB.

PluginExtended access263Repository stars

A Playwright and TypeScript project template with rules and 17 skills so Claude Code, Codex and Cursor write tests to a standard

CLIExtended access283Repository stars

show-your-work

claude-show-your-work

A plugin that shows images and video in the Claude Code terminal, records Playwright checks and compares before and after

PluginExtended access308Repository stars

README in short

Installation goes through the Claude Code or Codex marketplace, with a manual symlink variant. Requests are plain phrases and the report structure is fixed.

README badge

Report a problem