Agent skill

Wp Accessibility Review

by jorgerosal in jorgerosal/wordpress-skills

WordPress accessibility review for themes, blocks, plugins, and admin interfaces.

MITAuto-check passedFrontend & Design

Install Wp Accessibility Review

skills CLI
$ npx skills add jorgerosal/wordpress-skills --skill wp-accessibility-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jorgerosal/wordpress-skills wp-accessibility-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jorgerosal/wordpress-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-skills/wp-accessibility-review .claude/skills/wp-accessibility-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
wp-accessibility-review
GitHub stars
102
Token cost
~1.1k tokens
SKILL.md length
365 words
Files
3 (incl. references)
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

WordPress accessibility review for themes, blocks, plugins, and admin interfaces.

  • Works in 4 steps: Identify surface → Check structural semantics → Check interaction behavior → …
  • Reviewing keyboard navigation
  • SKILL.md covers Overview, When to Use, Code Review Workflow and File-Type Specific Checks, plus 3 more sections
  • Calls rg and modal

What it does

Wp Accessibility Review is an agent skill from jorgerosal/wordpress-skills. WordPress accessibility review for themes, blocks, plugins, and admin interfaces. Use when reviewing keyboard navigation, focus behavior, semantic HTML, ARIA usage, form labeling, screen-reader support, contrast-related implementation issues, or when user mentions "accessibility review", "a11y", "keyboard navigation", "focus management", "screen reader", "ARIA", "semantic HTML", "accessible form", or "accessible block". Detects implementation-level accessibility issues in frontend output, block markup, admin…

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/interactive-a11y-patterns.md` and `references/semantic-and-form-patterns.md`).

It sits in Frontend & Design, covering Accessibility. It works with WordPress. The repository describes itself as: ✅ 🎉 Claude skills and Codex skills for Wordpress development❗️. The licence is MIT.

When your agent uses it

  • Reviewing keyboard navigation
  • Screen-reader support
  • Contrast-related implementation issues
  • User mentions accessibility review

Example prompts

  • “accessibility review”
  • “keyboard navigation”
  • “focus management”
  • “/wp-accessibility-review”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Identify surface
  2. Check structural semantics
  3. Check interaction behavior
  4. Apply severity

What it can do on your machine

Read from SKILL.md and the folder at commit 8c96442. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • rg
    • modal

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Wp Accessibility Review loads about 1.1k tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 144 tokens; SKILL.md has 365 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~144
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jorgerosal/wordpress-skills at commit 8c96442, republished under its MIT licence (© jorgerosal). 365 words, ~1,111 tokens.

Download SKILL.mdSave it as .claude/skills/wp-accessibility-review/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
wp-accessibility-review
description
WordPress accessibility review for themes, blocks, plugins, and admin interfaces. Use when reviewing keyboard navigation, focus behavior, semantic HTML, ARIA usage, form labeling, screen-reader support, contrast-related implementation issues, or when user mentions "accessibility review", "a11y", "keyboard navigation", "focus management", "screen reader", "ARIA", "semantic HTML", "accessible form", or "accessible block". Detects implementation-level accessibility issues in frontend output, block markup, admin screens, and interactive UI behavior.

WordPress Accessibility Review Skill

Overview

Systematic accessibility review for WordPress themes, blocks, plugins, and admin interfaces. Core principle: Accessibility should be built into structure, interactions, and state changes, not patched in with scattered ARIA. Review covers semantic markup, keyboard behavior, focus management, labels, error messaging, admin interactions, block output, and JS-driven UI changes.

When to Use

Use when:

  • Reviewing theme templates or block markup
  • Auditing admin forms or custom plugin UI
  • Checking modal, tab, accordion, or menu interactions
  • Reviewing form labels, errors, and focus behavior
  • Validating accessible implementation before release

Don't use for:

  • Pure visual design critique without implementation context
  • Performance-only or security-only review
  • Color contrast measurement from screenshots alone

Code Review Workflow

  1. Identify surface

    • Frontend template
    • Block output
    • Admin interface
    • Interactive JS component
  2. Check structural semantics

    • Heading order
    • Buttons vs links
    • Form label association
    • Table/list semantics
  3. Check interaction behavior

    • Keyboard access
    • Focus visibility and focus return
    • Live region or status messaging when needed
    • Dialog/accordion/tab semantics where applicable
  4. Apply severity

    • CRITICAL: Core action inaccessible by keyboard, unlabeled required form controls, modal or menu traps focus incorrectly
    • WARNING: Weak semantics, poor error association, ARIA misuse, clickable non-buttons
    • INFO: Could improve heading structure, help text, or landmark usage

File-Type Specific Checks

Show full SKILL.md (162 more words)Show less
Templates and Markup
  • CRITICAL: Interactive elements implemented as div/span without keyboard support
  • WARNING: Missing heading structure or landmark usage
  • WARNING: Form inputs without labels
  • INFO: Could use native elements instead of ARIA-heavy replacements
JavaScript Interactions
  • CRITICAL: Focus not moved into modal or not returned on close
  • WARNING: Keyboard handlers incomplete
  • WARNING: State changes only visible visually
  • INFO: Could use live regions for async updates
Block and Admin UI Output
  • WARNING: Inspector controls or block UI labels unclear
  • WARNING: Admin notices not announced appropriately
  • INFO: Could improve empty-state clarity and assistive text

Search Patterns for Quick Detection (A11Y-21)

Use these rg commands for fast accessibility-oriented code scanning.

CRITICAL Patterns
bash
# Click handlers on non-semantic elements
rg -n "<(div|span)[^>]+on(click|key)" . -g '*.{php,html,js,jsx}'

# Form controls without obvious label references
rg -n "<input|<select|<textarea" . -g '*.{php,html}'

# Dialog or modal implementations
rg -n "dialog|modal|aria-modal|role=['\"]dialog" . -g '*.{php,html,js,jsx}'
WARNING Patterns
bash
# ARIA usage candidates to inspect manually
rg -n "aria-|role=" . -g '*.{php,html,js,jsx}'

# Button-like links or link-like buttons
rg -n "<a[^>]+href=['\"]#|<button[^>]+onclick" . -g '*.{php,html}'

# Focus management code
rg -n "focus\(|tabindex|keydown|keyup" . -g '*.{js,jsx,php}'
INFO Patterns
bash
# Headings and landmark structure
rg -n "<h[1-6]|<main|<nav|<aside|<header|<footer" . -g '*.{php,html}'

Reference Files

  • references/semantic-and-form-patterns.md - Native semantics, labels, error messaging, and form structure
  • references/interactive-a11y-patterns.md - Modals, menus, accordions, tabs, focus management, and keyboard behavior

Output Format (A11Y-23)

For each finding include severity, file reference, affected user interaction, why the implementation is inaccessible, and the practical fix. Prefer implementation guidance over broad compliance language.

© jorgerosal, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in claude-skills/wp-accessibility-review of jorgerosal/wordpress-skills.

  • SKILL.md
  • references/interactive-a11y-patterns.md
  • references/semantic-and-form-patterns.md

Open the folder on GitHubat commit 8c96442

Compare with similar skills

Wp Accessibility Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Wp Accessibility Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wp Accessibility Review this skilljorgerosal/wordpress-skills102—~1.1kAutomated safety check: PassMIT
Web Interface Guidelines Reviewervercel-labs/openreview1.7k97 repos~308Automated safety check: PassNone
Accessibility Reviewmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence
Accessibility Fixeribelick/ui-skills9.5k4 repos~1.2kAutomated safety check: PassMIT
Wcag Audit PatternsvmDeshpande/ai-agent-automation17811 repos~610Automated safety check: PassApache-2.0

Similar skills

  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 97 repos~308 tokens
    Frontend & DesignAuto-check passed
  • Accessibility Review

    markmead/hyperui

    Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

    12k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • Web Animation Design

    baptisteArno/typebot.io

    Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.

    11k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed
  • Accessibility Fixer

    ibelick/ui-skills

    Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.

    9.5k GitHub starsUsed in 4 repos~1.2k tokens
    Frontend & DesignAuto-check passed
  • Wcag Audit Patterns

    vmDeshpande/ai-agent-automation

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.

    178 GitHub starsUsed in 11 repos~610 tokens
    Frontend & DesignAuto-check passed
  • Baseline UI

    ibelick/ui-skills

    Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.

    9.5k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed

More from jorgerosal/wordpress-skills

All 35 skills in this repo
  • Wp Acf And Content Modeling

    jorgerosal/wordpress-skills

    WordPress ACF and content modeling review. An agent skill from jorgerosal/wordpress-skills.

    102 GitHub stars~3.2k tokensUpdated 4 mo ago
    Auto-check passed
  • Wp Admin UI Development

    jorgerosal/wordpress-skills

    WordPress admin UI review and development guidance. An agent skill from jorgerosal/wordpress-skills.

    102 GitHub stars~1.2k tokensUpdated 4 mo ago
    Auto-check passed
  • Wp CI CD And Release Engineering

    jorgerosal/wordpress-skills

    WordPress CI/CD and release engineering review guidance. An agent skill from jorgerosal/wordpress-skills.

    102 GitHub stars~1.7k tokensUpdated 4 mo ago
    Auto-check passed
  • Wp Headless And Wpgraphql

    jorgerosal/wordpress-skills

    Headless WordPress and WPGraphQL review guidance. An agent skill from jorgerosal/wordpress-skills.

    102 GitHub stars~1.7k tokensUpdated 4 mo ago
    Auto-check passed
  • Wp Migration Upgrade Review

    jorgerosal/wordpress-skills

    WordPress migration and upgrade review. An agent skill from jorgerosal/wordpress-skills.

    102 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Wp Phpstan Review

    jorgerosal/wordpress-skills

    WordPress PHPStan review and setup guidance. An agent skill from jorgerosal/wordpress-skills.

    102 GitHub stars~1.2k tokensUpdated 4 mo ago
    Auto-check passed

Works with

Questions about Wp Accessibility Review

What does Wp Accessibility Review do?

WordPress accessibility review for themes, blocks, plugins, and admin interfaces. Wp Accessibility Review is an agent skill from jorgerosal/wordpress-skills. WordPress accessibility review for themes, blocks, plugins, and admin interfaces.

When should I use Wp Accessibility Review?

Wp Accessibility Review fits situations like: reviewing keyboard navigation; screen-reader support; contrast-related implementation issues; user mentions accessibility review.

How do I install Wp Accessibility Review in Claude Code?

Run `npx skills add jorgerosal/wordpress-skills --skill wp-accessibility-review -a claude-code`. Or copy the skill folder (claude-skills/wp-accessibility-review in jorgerosal/wordpress-skills) into .claude/skills/wp-accessibility-review in your project. Claude Code loads it when a task matches its description.

How do I install Wp Accessibility Review in Codex?

Run `npx skills add jorgerosal/wordpress-skills --skill wp-accessibility-review -a codex`. Or copy the skill folder (claude-skills/wp-accessibility-review in jorgerosal/wordpress-skills) into .agents/skills/wp-accessibility-review in your project. Codex loads it when a task matches its description.

Can I use Wp Accessibility Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jorgerosal/wordpress-skills --skill wp-accessibility-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wp-accessibility-review, .gemini/skills/wp-accessibility-review, .github/skills/wp-accessibility-review and .opencode/skills/wp-accessibility-review in your project.

What does Wp Accessibility Review need to run?

Going by SKILL.md and its folder, Wp Accessibility Review needs the command-line tools its instructions call (rg and modal).

Does Wp Accessibility Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Wp Accessibility Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Wp Accessibility Review use?

Wp Accessibility Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Wp Accessibility Review use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 224 tokens, read only when the agent opens those files.

What are the alternatives to Wp Accessibility Review?

Skills that share tags, products or a category with Wp Accessibility Review: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wp Accessibility Review?

jorgerosal (a GitHub user) maintains it in jorgerosal/wordpress-skills, which has 102 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on June 7, 2026.

Source: jorgerosal/wordpress-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.