orbit-accessibility

Audit WordPress plugin interfaces for WCAG 2.2 AA compliance using axe-core and code review.

2|1|Updated Apr 20, 2026

Search Tags:#accessibility #a11y #WCAG #audit #WordPress

Ready to run

npx skills add https://github.com/adityaarsharma/orbit --skill orbit-accessibility

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orbit-accessibility
Source: https://github.com/adityaarsharma/orbit/tree/main/skills/orbit-accessibility
Command: npx skills add https://github.com/adityaarsharma/orbit --skill orbit-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of WCAG 2.2 AA accessibility audits for WordPress plugin admin UI, block editor output, and frontend markup, ensuring compliance with accessibility standards.

Core Features & Use Cases

Automated WCAG Audit: Combines axe-core (30% automated coverage) with code review to catch 70% of accessibility issues that automated tools miss.
Use Case: After any UI change to the plugin's admin pages or block output, use this Skill to audit for accessibility compliance.
Integration: Runs automatically as part of /orbit-gauntlet --mode full.

Quick Start

Run the orbit-accessibility skill with Claude to audit a plugin's admin UI and frontend markup for WCAG 2.2 AA compliance: "Audit admin UI for WCAG 2.2 AA using orbit-accessibility."

Frequently Asked Questions about orbit-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit a WordPress plugin for WCAG 2.2 AA compliance?▼

You audit WordPress plugin accessibility against WCAG 2.2 AA standards by combining automated axe-core scanning with manual code review to assess admin UI, block editor output, and frontend markup for compliance issues.

What percentage of WCAG 2.2 AA issues can automated accessibility tools catch?▼

Automated accessibility tools like axe-core catch approximately 30% of WCAG 2.2 AA issues, requiring manual code review to identify the remaining 70% of accessibility problems in WordPress plugin interfaces.

Can I use axe-core to audit WordPress block editor output for accessibility?▼

Yes, you can use axe-core to audit WordPress block editor output for accessibility, combining it with manual code review to evaluate frontend markup and admin UI against WCAG 2.2 AA standards.

When should I run a WCAG 2.2 AA accessibility audit on my WordPress plugin?▼

You should run a WCAG 2.2 AA accessibility audit on your WordPress plugin after any UI change to admin pages or block output to ensure ongoing compliance with accessibility standards.

Does automated axe-core scanning find all WCAG 2.2 AA violations in WordPress plugins?▼

No, automated axe-core scanning does not find all WCAG 2.2 AA violations in WordPress plugins, covering only 30% of issues while manual code review is required to detect the remaining 70%.