WordPress Accessibility

Audit WordPress themes, plugins, and blocks for WCAG 2.1/2.2 Level AA compliance.

6|2|Updated Dec 1, 2025

Search Tags:#accessibility #a11y #screen reader #keyboard navigation #WCAG #compliance #WordPress

Ready to run

npx skills add https://github.com/courtneyr-dev/wp-dev-prompts --skill wordpress-accessibility

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: WordPress Accessibility
Source: https://github.com/courtneyr-dev/wp-dev-prompts/tree/main/skills/wordpress-accessibility
Command: npx skills add https://github.com/courtneyr-dev/wp-dev-prompts --skill wordpress-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make WordPress websites, themes, and plugins accessible to all users, including those with disabilities, by adhering to WCAG standards.

Core Features & Use Cases

Automated Audits: Identifies common accessibility violations through automated checks.
Manual Testing Guidance: Provides clear steps for keyboard and screen reader testing.
ARIA Pattern Implementation: Offers examples of correct ARIA usage for interactive elements.
Color Contrast Checks: Details contrast ratio requirements for text and UI elements.
WordPress Specifics: Covers accessibility considerations for blocks, admin areas, and theme templates.
Use Case: A developer can use this Skill to audit a new custom block for WCAG 2.2 Level AA compliance, ensuring it's usable by keyboard-only users and screen reader software.

Quick Start

Review the provided WCAG 2.2 Level AA checklist for WordPress development.

Frequently Asked Questions about WordPress Accessibility

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

FAQPage Schema

How do I make a WordPress theme WCAG 2.2 Level AA compliant?▼

WordPress WCAG 2.2 Level AA compliance requires verifying keyboard navigation, screen reader compatibility, correct ARIA patterns, and color contrast requirements across themes, plugins, and block editor output through automated scanning and manual testing.

What WordPress accessibility checks are needed for custom blocks?▼

WordPress custom block accessibility checks require verifying keyboard-only navigation, screen reader compatibility, correct ARIA pattern implementation for interactive elements, and adequate color contrast ratios to meet WCAG 2.1/2.2 Level AA standards.

How do I test keyboard navigation and screen reader compatibility in WordPress?▼

Test WordPress keyboard navigation and screen reader compatibility by following manual testing guidance steps that verify interactive elements are fully reachable and properly announced without relying on a mouse pointer device.

When do I need ARIA patterns for WordPress plugin development?▼

You need ARIA patterns for WordPress plugin development when building interactive elements that require screen reader compatibility and keyboard navigation, ensuring custom UI components meet WCAG 2.1/2.2 Level AA accessibility standards.

Can I use automated scanning to find all WCAG violations in WordPress?▼

Automated scanning identifies common accessibility violations in WordPress, but manual testing guidance is also required to fully verify keyboard navigation flows and screen reader compatibility for WCAG 2.2 Level AA compliance.