WordPress · ADA Title III · WCAG 2.1 AA
Make your WordPress site ADA compliant
US courts use WCAG 2.1 Level AA as the de-facto ADA standard for websites, and WordPress sites open to the public are among the most sued. The path is straightforward: scan for the violations that matter, fix the source, and document what you did — no overlay widget required.
Got a demand letter?
Act, but don't panic-buy an overlay. Scan first to see the real issues, fix the serious ones, and document the dates. The first-48-hours playbook walks through the exact response.
The 3-step compliance path
- 1. Scan for WCAG 2.1 AA violations. Install the free plugin and run it on your key templates — home, a product/service page, contact, and any form. It uses axe-core, the same engine plaintiff experts use.
- 2. Fix the source.Resolve serious and critical issues in your theme and content. The axle Site plan ($19/mo) generates the code-level fix for each one if you don't have a developer.
- 3. Document conformance. Keep dated scan reports and publish an accessibility statement. A documented remediation history is what defends you.
Check your site now
Enter your WordPress URL for a free WCAG 2.2 AA report — the fastest way to see where you stand.
WordPress ADA compliance FAQ
Does my WordPress site have to be ADA compliant?
US courts apply ADA Title III to websites as 'places of public accommodation' and use WCAG 2.1 Level AA as the practical standard. There is no official government checklist, but WCAG 2.1 AA is what settlements, consent decrees, and expert witnesses reference. Businesses open to the public — retail, services, hospitality, healthcare — are the most frequent targets.
What is the standard for ADA website compliance?
WCAG 2.1 Level AA. It is the conformance level cited in the vast majority of ADA web settlements and the one the DOJ has pointed to. Meeting WCAG 2.1 AA (and ideally 2.2 AA) is the defensible target. An automated scan catches roughly 57% of issues; a human audit covers the rest.
I received an ADA demand letter for my WordPress site — what do I do?
Don't ignore it, and don't panic-buy an overlay widget (they don't resolve claims and can make you a repeat target). Scan your site to establish the actual issues, fix the serious violations, and document the remediation with dates. See the first-48-hours playbook for the full response, then keep a record of your conformance work.
Is an accessibility overlay or plugin enough for ADA compliance?
An overlay is not — the FTC fined the largest vendor $1M in 2025 and overlay sites are still sued. A scanning plugin that shows you real source-level fixes is the right tool: it finds the WCAG 2.1 AA violations courts care about so you can fix your theme and content, then document it.