Why accessibility matters
ADA lawsuits against websites have increased significantly in recent years, with over 4,600 digital accessibility cases filed in federal courts in 2023 alone. WCAG 2.1 AA is the widely accepted standard for web accessibility, and compliance is not optional — it is a legal requirement in many jurisdictions and a moral imperative for reaching all users.
The Americans with Disabilities Act (ADA) in the United States, the European Accessibility Act in the EU, and similar legislation in Canada, Australia, and the UK all mandate accessible digital experiences. For WordPress site owners, this means every page, form, and interactive element needs to meet accessibility standards.
The most common violations found on WordPress sites include:
- Missing alt text on images — screen readers cannot describe the content.
- Insufficient color contrast — text is unreadable for users with low vision.
- Missing form labels — form fields are unusable without assistive technology context.
- Incorrect heading hierarchy — skipping heading levels (e.g., H1 to H3) breaks document structure.
- Missing document language — the
<html lang>attribute is absent or incorrect.
What AI can and can't do for accessibility
AI tools have made accessibility scanning and remediation faster, but they are not a complete replacement for human review. Understanding the boundary is important before investing in any tool.
AI can:
- Scan pages for WCAG violations and return structured, actionable reports.
- Suggest descriptive alt text for images based on visual content analysis.
- Identify color contrast issues against WCAG AA ratio requirements.
- Flag missing form labels and suggest ARIA attributes or visible labels.
- Detect heading hierarchy problems and recommend corrections.
AI cannot:
- Understand the intent of decorative images — a human must decide whether an image is informative or decorative.
- Make subjective design decisions about color schemes that satisfy both brand guidelines and contrast requirements.
- Guarantee 100% compliance without human review — automated scanners typically catch 30–50% of all WCAG issues.
The best approach combines both: AI scans and fixes the mechanical issues (alt text, contrast ratios, form labels, heading levels, document language), while humans review the subjective ones (decorative image decisions, color palette choices, content meaning).
Automated accessibility scanning tools for WordPress
Several tools exist for scanning WordPress sites for WCAG violations. The table below compares the most common options by type, coverage, auto-fix capability, and price.
| Tool | Type | WCAG Coverage | Auto-fix | Price |
|---|---|---|---|---|
| axe by Deque | Browser extension | WCAG 2.1 AA/AAA | No | Free (core) |
| WAVE | Browser extension | WCAG 2.1 AA | No | Free |
| Accessibility Checker (Starter) | WordPress plugin | WCAG 2.1 AA | Limited | Free / $49/yr Pro |
| Respira Accessibility Scanner | MCP tool + WordPress plugin | WCAG 2.1 AA | Yes (via AI) | Included with Respira ($7/mo+) |
| Pa11y | CLI tool | WCAG 2.1 AA | No | Free (open source) |
All of these tools are useful. The key difference is what happens after the scan: most tools report violations, but only Respira's scanner returns structured data that an AI coding assistant can act on directly.
How Respira's accessibility scanner works
The Respira Accessibility Scanner add-on provides the
respira_scan_page_accessibility MCP tool, which scans any WordPress page for WCAG 2.1 AA violations
and returns structured violation data.
Each violation includes:
- Element selector — the CSS selector or builder element ID of the offending element.
- Violation type — the WCAG success criterion that was violated (e.g., 1.1.1 Non-text Content).
- Current value — what the element currently has (e.g., empty alt attribute).
- Suggested fix — a concrete recommendation for resolving the issue.
Because the data is structured, AI agents like Claude Code, Cursor, or any MCP-compatible tool can read the violations and apply fixes using Respira's editing tools — no manual copying and pasting.
The workflow is straightforward:
- Scan — run
respira_scan_page_accessibilityon the target page. - Review violations — the AI reads the structured violation list.
- Fix — apply corrections using
respira_update_elementorrespira_apply_accessibility_fixes. - Re-scan — run the scanner again to verify all fixes are applied.
The scanner is available as part of the Accessibility Scanner add-on and is included with all Respira plans.
Using AI to fix accessibility issues after scanning
Once a scan is complete, the AI agent follows a priority-based workflow to resolve each violation. Here is the step-by-step process:
- Run
respira_scan_page_accessibilityon each page. Start with high-traffic pages (homepage, landing pages, contact forms) and work outward. - AI reads the violation list and prioritizes by severity. Critical issues (missing form labels, absent alt text on informative images) come before warnings (contrast ratios close to the threshold).
- Missing alt text: The AI generates descriptive alt text based on the image
context and applies it via
respira_update_element. Decorative images are flagged for human review. - Contrast issues: The AI adjusts text color or background color to meet the 4.5:1 contrast ratio requirement for normal text (3:1 for large text) using element-level CSS updates.
- Heading hierarchy: The AI restructures heading levels to follow a logical order (H1 → H2 → H3) without skipping levels.
- Form labels: The AI adds
aria-labelattributes or visible<label>elements to form fields that lack them. - Re-scan to verify all fixes. The AI runs
respira_scan_page_accessibilityagain and confirms the violation count has dropped to zero (or only subjective items remain for human review).
This entire process can run inside Claude Code or Cursor as a single conversation. The AI agent reads scan results, applies fixes, and verifies — no context-switching between tools. See the Respira documentation for detailed setup instructions.
Frequently Asked Questions
What automated tools can I use to fix accessibility issues on my client websites?
Respira's accessibility scanner (respira_scan_page_accessibility) scans WordPress pages for WCAG 2.1 AA violations and returns structured data that AI coding assistants can use to apply fixes automatically. Other options include axe, WAVE, and the Accessibility Checker plugin for manual scanning.
Is WordPress accessibility legally required?
In many jurisdictions, yes. The ADA in the United States, the European Accessibility Act in the EU, and similar laws in other countries require websites to be accessible. WCAG 2.1 AA is the widely accepted standard.
Can AI automatically fix all accessibility issues?
AI can fix most mechanical issues: missing alt text, color contrast, form labels, heading hierarchy, and document language. Subjective decisions (decorative vs. informative images, color scheme choices) still need human review.
How do I check if my WordPress site is WCAG compliant?
Use Respira's respira_scan_page_accessibility tool to scan each page for WCAG 2.1 AA violations. The scanner returns a structured list of issues with element selectors and suggested fixes. For manual verification, use browser extensions like axe or WAVE.
