skills.rest
jorgerosal
jorgerosalCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

wp-accessibility-review

Identify accessibility issues in WordPress UI implementations with severity and file references.

69|9|Updated Apr 17, 2026
Search Tags:#accessibility#a11y#audit#semantic-markup#wordpress#aria#keyboard-access
One-click install
npx skills add https://github.com/jorgerosal/wordpress-skills --skill wp-accessibility-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wp-accessibility-review
Source: https://github.com/jorgerosal/wordpress-skills/tree/main/codex-skills/wp-accessibility-review
Command: npx skills add https://github.com/jorgerosal/wordpress-skills --skill wp-accessibility-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WordPress accessibility review for Codex. Use when reviewing semantic HTML, keyboard access, focus behavior, form labels, ARIA usage, and accessible interaction patterns in themes, blocks, plugins, and admin screens.

Core Features & Use Cases

  • Semantic markup checks ensure proper element roles and landmark usage across frontend and admin views.
  • Keyboard and focus checks verify logical tab order, visible focus rings, and accessible modal/dialog interactions.
  • Labels and ARIA checks validate form labels, relationships, and appropriate ARIA attributes for dynamic UI.
  • Use Case: Audit WordPress UI implementation in new themes or plugins to ensure accessibility best practices are met.

Quick Start

Instruct Codex to audit the target WordPress surface (frontend, block output, or admin UI) for accessibility issues and report actionable fixes.

Frequently Asked Questions about wp-accessibility-review

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

FAQPage Schema
How do I audit a WordPress theme for accessibility and ARIA issues?▼

WordPress accessibility audits review semantic markup, keyboard navigation, focus behavior, form labels, and ARIA usage across frontend templates, blocks, and admin screens. They validate landmark roles, logical tab order, visible focus rings, and accessible modal interactions.

How do I fix keyboard access and focus issues in WordPress blocks?▼

Fixing keyboard access in WordPress blocks requires verifying logical tab order, visible focus rings, and accessible modal or dialog interactions. Accessibility reviews detect focus behavior barriers and provide concrete file references and practical fixes to restore keyboard navigation.

Does my WordPress plugin need semantic markup checks for admin screens?▼

WordPress plugin admin screens need semantic markup checks to ensure proper element roles and landmark usage. Accessibility reviews validate admin interfaces alongside frontend views, identifying ARIA and structural issues with specific file references and severity ratings.

Can I check form labels and ARIA relationships in WordPress admin interfaces?▼

You can check form labels and ARIA relationships in WordPress admin interfaces. Accessibility reviews validate form labels, relationships, and appropriate ARIA attributes across admin screens and frontend views, flagging missing or incorrect dynamic UI associations.

What is the best way to review ARIA usage in dynamic WordPress UI components?▼

Review ARIA usage in dynamic WordPress UI components by auditing accessible interaction patterns and validating that ARIA attributes correctly communicate state changes. Reviews provide severity-ranked findings and practical fixes for frontend templates and admin screens.

What limitations exist when auditing WordPress accessibility for custom block patterns?▼

Auditing WordPress accessibility for custom block patterns is limited to analyzing semantic structure, keyboard navigation, and ARIA usage within the provided UI implementation. It requires specifying the target surface and cannot detect runtime issues absent from the static markup.

Related Skills

Explore More Design & Creative Skills→
pelcherspelchers

ensuring-accessibility

Implement WCAG 2.1 AA-compliant accessibility patterns for web interfaces.

Community
Advanced
89jobrien89jobrien
4

web-accessibility

Audit web content for WCAG 2.1/2.2 conformance and accessibility issues.

Community
Advanced
SAPSAP
294

a11y-audit

Audit UI components for WCAG AA accessibility compliance.

Official
Advanced
MaggieAppletonMaggieAppleton
160

fixing-accessibility

Identify and fix HTML accessibility issues to meet WCAG requirements.

Community
Intermediate