WordPress accessibility, fixed in the code
WordPress powers a huge share of the web, which means a huge share of ADA web lawsuits land on WordPress sites. The good news: WordPress accessibility is fixable. Curbcut makes your WordPress site conform to WCAG 2.1 AA by remediating the actual code your theme, page builder, and plugins produce — not by bolting on a widget that hides the problem.
If you’ve received a demand letter, or you just want to remove legal exposure and serve every customer, this is the durable way to do it. Thousands of ADA website lawsuits are filed in the U.S. each year, and small businesses are the most common target. (This page is general information, not legal advice — for your specific risk, talk to an attorney.)
Why WordPress sites fail accessibility audits
WordPress core and the block editor are built to accessibility coding standards. The problems almost always come from what you add on top:
Themes
Many commercial themes ship with low color contrast, missing focus styles, decorative images without alt text, and broken heading structure. A theme demo can look polished and still be unusable with a screen reader (NVDA, JAWS, or VoiceOver) or by keyboard navigation alone.
Page builders
Elementor, Divi, WPBakery, and Beaver Builder give you visual control but frequently output inaccessible markup: <div> elements used as buttons, sliders and carousels with no keyboard support, popups that trap focus, accordions and tabs missing the right ARIA roles, and forms without labels. The builder isn’t inherently bad — it’s the default widgets and configuration that break the POUR principles (Perceivable, Operable, Understandable, Robust).
Plugins
Sliders, galleries, booking forms, cookie banners, and chat widgets each inject their own HTML. One inaccessible plugin can fail your whole page for assistive technology users — and you don’t control that third-party code through the WordPress editor.
| WordPress layer | Common accessibility issue | WCAG criterion |
|---|---|---|
| Theme | Low text/background contrast | 1.4.3 Contrast (Minimum) |
| Theme | No visible keyboard focus | 2.4.7 Focus Visible |
| Page builder | Carousels not keyboard-operable | 2.1.1 Keyboard |
| Page builder | Skipped or out-of-order headings | 1.3.1 Info & Relationships |
| Plugin (forms) | Inputs without labels | 3.3.2 Labels or Instructions |
| Media library | Images missing alt text | 1.1.1 Non-text Content |
Accessibility plugins vs. real remediation
This is the most important distinction for WordPress owners, because the plugin directory makes “one-click compliance” sound easy.
Overlay plugins — accessiBe, UserWay, AudioEye, and similar — inject JavaScript that claims to fix your site automatically. They don’t. They leave the underlying barriers in your theme, builder, and plugin code, they can interfere with the screen readers people already use, and courts have repeatedly declined to treat them as a defense. Here’s the evidence on overlays, and a look at accessiBe, UserWay, and AudioEye alternatives.
Helper plugins — like accessibility-checker tools that scan your content — are genuinely useful for catching issues as you publish. But scanning is not fixing. Automated tools catch only a fraction of WCAG failures; the rest require human judgment.
Manual remediation is the work that actually makes you compliant: rewriting markup, correcting ARIA, fixing contrast tokens, adding real labels and alt text, and making every interaction keyboard-operable. That’s what holds up against a demand letter or lawsuit, and it’s what Curbcut’s remediation service delivers.
How Curbcut fixes WordPress sites
We remediate inside your stack so updates don’t wipe out the work:
- Audit — A manual + automated accessibility audit against WCAG 2.1 AA, testing your live theme, builder output, and key plugins with NVDA, VoiceOver, and keyboard-only navigation.
- Remediate safely — Fixes go into a child theme, template overrides, block patterns, and hooks — never edits that an update will overwrite. We correct contrast, headings, landmarks, focus order, labels, alt text, and ARIA on your real pages.
- Tame the plugins — We configure, replace, or wrap inaccessible plugins (sliders, forms, popups, menus) so third-party widgets stop failing your audit.
- Document — You get an accessibility statement and, if you sell to government, education, or enterprise, a VPAT / Accessibility Conformance Report.
- Monitor — Optional ongoing monitoring catches regressions when you add a plugin, change a theme, or publish new content.
WordPress accessibility checklist (the essentials)
- Headings: one logical H1, no skipped levels — verify with our heading structure guide.
- Images: meaningful alt text on content images, empty alt on decorative ones.
- Contrast: text meets 4.5:1 (3:1 for large text) — check theme and builder color presets.
- Keyboard: every menu, slider, popup, and form works without a mouse, with a visible focus ring.
- Forms: every field has a programmatic label and clear error messages.
- ARIA: used only where native HTML can’t do the job, and used correctly.
Standards and where to go deeper
WordPress accessibility is measured against the same standards as any site: WCAG 2.1 AA (the W3C/WAI guidelines), ADA Title III as applied to the web, and Section 508 if you contract with the government. The U.S. Department of Justice has affirmed that the ADA applies to websites, and resources like WebAIM and Section508.gov explain the technical requirements in depth. For a business-owner-friendly breakdown, see WCAG 2.1 AA explained and how ADA, Section 508, and WCAG differ.
Conformance is reported at levels A, AA, and AAA; AA is the practical legal target for almost every business. None of this is legal advice — for a demand letter or active claim, consult a qualified attorney.
Get your WordPress site genuinely accessible
Whether you run a brochure site, a membership portal, or a WooCommerce store, Curbcut remediates your WordPress site by hand so it works for everyone and stands up to scrutiny. Start with a free accessibility scan to see exactly where your site stands.