Skill · WordPress & Dev

WordPress Accessibility Auditor

A structured WCAG 2.1 AA audit and fix agent for WordPress themes — organised by block theme, Gutenberg, forms, and navigation context, not a generic axe dump.

Category: WordPress & Dev
Deliverable: 1 .skill bundle
Outputs: 6
Last updated: 15 Jun 2026

$13.99 One-time · lifetime updates

Get it on Agensi

Works in Claude Pro, Team, and Enterprise
Lifetime access to updates
Refundable for 30 days via the marketplace

Or get a free skill every month. Subscribers get one curated skill, free, every 1st. Pick yours →

StrategistKit Affiliate. Purchase happens on the marketplace, which handles payment, delivery and refunds.

Overview

What WordPress Accessibility Auditor does.

WordPress Accessibility Auditor runs in two modes against real WordPress code. In AUDIT mode, supply theme files, template part HTML, theme.json, plugin PHP or JS, or a live URL — the agent returns a scored finding table organized by WP context (block theme landmarks, skip links, keyboard operability, form labels, Gutenberg semantics, AJAX aria-live), an executive summary framed around EAA regulatory exposure, and a 13-item acceptance checklist where every item has its own axe or grep command for independent verification. In FIX mode, it delivers production-ready before-and-after patches for each finding.

A typical input looks like: paste your header.html, functions.php, theme.json, and a Contact Form 7 shortcode, state your regulatory context (EU EAA compliance, block FSE theme, no prior axe run), and run AUDIT. The agent identifies the missing skip link in header.html, the 2.4:1 contrast pair in theme.json, the CF7 field relying on placeholder text instead of a visible label, and the flyout nav where Tab never escapes — issues axe-core would not flag.

Sample output excerpt from AUDIT mode: a finding table row reads — ID: 2A-2, Criterion: 2.4.1 Bypass Blocks, Context: parts/header.html, Finding: No skip link present as first focusable element, Impact: 5, Effort: 1, Score: 25.0, Tier: P0 — block before launch. Below the table, the executive summary notes EAA legal exposure. FIX mode then returns the complete skip link template-part patch with before and after code blocks and the axe command to verify the fix.

Who it's for

WordPress developers and agencies shipping sites to EU or Norwegian clients who carry EAA or public-sector accessibility compliance obligations — particularly those maintaining block or FSE themes where automated scanners miss the majority of real violations. Also useful for freelancers preparing a client-facing audit report that must withstand independent legal or technical review.

What you get

One skill. 6 outputs.

One .skill bundle. Run it on your material and it returns:

A structured WCAG 2.1 AA audit organized by WordPress context: block themes, navigation, forms, Gutenberg, dynamic content.

Scored audit table (Impact²/Effort) with P0–P3 severity tiers — fix legal blockers first.

6 complete before→after code fixes: skip link, modal focus management, aria-live for AJAX, theme.json contrast checker, CF7 form labels, keyboard-trap-free navigation.

A Node.js palette contrast checker that reads theme.json and exits non-zero in CI if any color pair fails WCAG AA.

A 13-item verifiable acceptance checklist — every item has its own axe or grep command so a second reviewer can score objectively.

EAA / Norway accessibility law framing so you can present the business case to a client.

How it works

Three steps. About two minutes.

Install

Add the .skill file to your Claude app. ~10 seconds.

Run it on your work

Invoke the skill and paste in your material.

Apply the output

Review, keep what works, and use it.

In depth

Why a Claude skill beats a prompt template.

A copy-paste prompt runs one static pass and stops. A skill is a bundled program — instructions, examples, and a workflow Claude runs as a unit: it asks for the right input, applies the same pattern every time, and returns the structured outputs above.

FAQ

Common questions.

What input does the skill actually need to start an audit?

At minimum: your theme files or a live URL, confirmation of theme type (block/FSE, classic, or hybrid), any form plugins in use, and whether dynamic content like modals or AJAX search is present. If you cannot supply everything, the agent states sensible defaults and proceeds rather than blocking.

How is this different from just running axe-core myself?

Axe-core catches roughly 35% of WCAG 2.1 AA violations. This agent audits the other 65% by checking WordPress-specific failure points — the block theme skip link that never gets written, the theme.json palette pair with insufficient contrast, the Contact Form 7 field missing a visible label, the flyout menu that traps keyboard focus — none of which axe flags.

What code does FIX mode actually produce?

Six complete before-and-after patches covering: skip link template part, modal focus-trap handler, aria-live region for AJAX content, a Node.js theme.json contrast checker that exits non-zero in CI, labeled CF7 fields, and a keyboard-trap-free navigation handler. Each patch is ready to apply without further editing.

Can I use the audit report with a client or in a legal context?

The report includes EAA and Norwegian accessibility law framing and a 13-item acceptance checklist where every item has its own axe or grep verification command, so a second reviewer can score the site independently. The skill does not constitute legal advice, but the structured output is designed to support a defensible compliance conversation.

Does this work with classic themes, or only block and FSE themes?

Both. Gate 0 of the audit asks you to confirm theme type by checking the style.css header and presence of theme.json. The checklist items then apply the relevant context — classic themes skip block-editor-specific checks and focus on template file semantics, navigation PHP, and enqueued script behavior instead.

Skills used with this one.

WordPress & DevAgensi