WordPress Accessibility Compliance Guide

What this prompt does

This prompt makes the model a WordPress accessibility specialist driving a [site_type] site to [compliance_level]. It runs six stages: an automated audit with [audit_tool], a theme structure review of [theme_name], form fixes, media fixes, keyboard and focus management, and an ongoing maintenance plan.

The audit scans [page_count] representative pages including the [critical_page], categorizing each issue by WCAG criterion, severity, and affected element into a prioritized backlog. The theme review checks heading hierarchy, landmark roles, skip links, and contrast against [contrast_ratio]. Form work enforces label/id pairs and aria-describedby error wiring; media work covers alt text, captions, and transcripts; and the keyboard pass tests [interactive_count] components for operability and visible [focus_style] focus.

The prompt is honest about the limits of tooling, which is what makes it credible. Automated scans catch only a fraction of real barriers, so it pairs [audit_tool] with manual [screen_reader] testing using [screen_reader] to catch what tools miss. Each issue carries a WCAG criterion, a severity, and an affected element, producing a backlog sorted by impact and effort rather than a flat dump of warnings. The final stage turns compliance into a habit with [monitoring_tool] regression scans, editor training, an accessibility statement, and a feedback channel, so the site does not quietly regress after the next content update.

When to use it

• You must bring a site to [compliance_level], often for legal or procurement reasons.
• An automated scan flagged issues and you need them triaged and fixed.
• Your theme [theme_name] has structural problems like bad heading order or low contrast.
• Forms lack proper labels and screen-reader error handling.
• Interactive components fail keyboard navigation or focus trapping.
• You want ongoing monitoring and editor training, not a one-time pass.

Example output

Expect an audit-plus-remediation package: a prioritized backlog from [audit_tool] across [page_count] pages tagged by WCAG criterion and severity, theme fixes for [theme_name] with file and line references (or a child theme for overrides), form corrections with label/id and aria-describedby wiring, media guidance with [example_count] good-vs-bad alt-text examples, a keyboard pass over [interactive_count] components using [focus_style] indicators, and a maintenance plan with [monitoring_tool] scans plus [screen_reader] manual audits.

Pro tips

• Treat the automated scan as a starting point; pair it with [screen_reader] testing, since tools miss roughly the issues that matter most to real users.
• Fix contrast at the theme level against [contrast_ratio] rather than patching colors page by page.
• Wire form errors with aria-describedby and aria-live so they are announced, not just shown.
• Use empty alt="" for decorative images; alt text on every image is not the goal, accurate alt text is.
• Test focus trapping and restoration on every modal among the [interactive_count] components, not just the obvious ones.
• Schedule recurring [monitoring_tool] scans so fixes do not regress after the next content update.