WordPress is the most widely used CMS on the planet, but it does not ship as a fully accessible platform out of the box. Default themes, popular page builders, and third-party plugins routinely introduce WCAG violations that can expose site owners to ADA Title III lawsuits and shut out disabled users.
The good news: WordPress's plugin ecosystem makes accessibility improvements more achievable than on most other platforms. With the right theme, a few well-chosen plugins, and a systematic audit, most WordPress sites can reach WCAG 2.1 AA compliance.
See how 321 websites scored →
View the 2026 ReportThe DOJ's 2024 rule under ADA Title III confirmed that websites are places of public accommodation. Courts routinely hold that WordPress sites — whether run by small businesses, nonprofits, or enterprises — are covered. Inaccessible WordPress sites are a common target for demand letters and litigation precisely because the platform is so widely used and violations are often predictable and easy to scan for.
Accessibility is also good business. Screen reader users, keyboard-only users, and people with low vision represent a significant purchasing segment. An inaccessible WordPress site loses those customers before they even read your content.
WordPress accessibility is complex because your site's accessibility is the product of several independent systems working together: the WordPress core, your active theme, your active plugins, and your own content. A failure in any one layer creates violations.
WordPress core has improved substantially over recent releases. The Gutenberg block editor now outputs semantically correct HTML for most standard blocks, and the admin dashboard meets basic accessibility requirements. However, core alone is not enough — theme and plugin choices matter enormously.
Your theme controls the most critical accessibility properties: heading hierarchy, color contrast, keyboard navigation, focus indicators, and landmark regions. An inaccessible theme is the single most common source of WCAG failures on WordPress sites.
Every plugin you install can introduce new accessibility violations. Contact form plugins with unlabeled fields, slider plugins that autoplay without controls, and cookie consent banners that trap keyboard focus are among the most common plugin-introduced issues.
Even with a fully accessible theme and plugins, editors can introduce violations: images without alt text, manually set low-contrast colors, skipped heading levels, and tables without headers. Content governance is a critical part of WordPress accessibility.
The single highest-impact decision for WordPress accessibility is your theme choice. An accessible theme handles the structural requirements automatically — correct landmark regions, sufficient focus indicators, proper heading hierarchy, and sufficient color contrast defaults.
<header>, <main>, <nav>, <footer> landmark regions presentWordPress's official default theme is built to accessibility standards and serves as the baseline for what "accessible" means on the platform. It includes skip navigation, semantic HTML, visible focus indicators, and correct ARIA landmarks. If you need a starting point, this is the safest choice.
Astra is one of the most popular themes on WordPress.org and maintains an accessibility-ready tag. The free version covers core WCAG requirements; the Pro version adds accessibility-tested header and footer builder components. Pairs well with the SureCart and Elementor ecosystems.
GeneratePress is lightweight, fast, and explicitly accessibility-ready. It outputs clean semantic HTML with proper landmark regions and keyboard-operable navigation. A strong choice for content-heavy sites, blogs, and business sites where performance and compliance both matter.
Neve carries the WordPress accessibility-ready badge and is actively maintained with regular accessibility audits. It includes a built-in accessibility module that can improve focus styles, enable a "Skip to content" link, and add high-contrast mode support.
Plugins extend what your theme provides. The best accessibility plugins address issues that themes can't fix alone — particularly content-level alt text enforcement, form accessibility, and runtime ARIA injection.
The gold standard free accessibility plugin for WordPress. Adds skip navigation links, improves focus outlines, removes title attributes from images, adds language attributes to the HTML element, and provides a suite of fixes for common WordPress accessibility failures. Actively maintained by Joe Dolson, a leading voice in WordPress accessibility.
Focuses on content accessibility — helps editors write better alt text, structure headings correctly, and avoid common content-layer violations. Provides inline guidance in the block editor when accessibility issues are detected while writing.
Contact Form 7 is the most widely used form plugin but ships with known accessibility issues (particularly with error identification and form labels). The CF7 Accessibility add-on corrects the most critical failures and brings forms into closer alignment with WCAG 1.3.1, 1.3.3, and 3.3.1.
For sites with complex forms, Gravity Forms is the most accessible commercial option. It supports proper error identification, inline labels, required field marking, and logical tab order. Worth the cost if forms are a core part of your site's functionality.
Replaces Gravatars, which load external resources and can cause privacy and performance issues. These alternatives keep user data local and don't introduce third-party inaccessible image sourcing into your comment sections.
Based on accessibility audits of thousands of WordPress sites, these are the violations that appear most often:
| Violation | WCAG Criterion | Common Source |
|---|---|---|
| Missing or empty alt text on images | 1.1.1 Non-text Content | Media library uploads, featured images, WooCommerce product images |
| Insufficient color contrast | 1.4.3 Contrast Minimum | Theme defaults, customizer-set colors, Gutenberg color blocks |
| Missing form input labels | 1.3.1 Info and Relationships | Contact Form 7, WooCommerce checkout, custom widgets |
| Keyboard trap in modal/popup | 2.1.2 No Keyboard Trap | Popup plugins, cookie consent banners, lightbox plugins |
| Missing skip navigation link | 2.4.1 Bypass Blocks | Non-accessibility-ready themes |
| No focus indicator on interactive elements | 2.4.7 Focus Visible | Themes that set outline: none globally |
| Skipped heading levels | 1.3.1 Info and Relationships | Page builder content, widgets, manually composed blog posts |
| Autoplay media without controls | 1.4.2 Audio Control | Background video themes, slider plugins with audio |
Use this checklist to perform a systematic audit of your WordPress site before seeking compliance certification.
lang attribute is set to the correct language<header>, <main>, <nav>, <footer>outline: none or outline: 0 without replacementalt="") or are CSS backgroundsIf you run a WooCommerce store, accessibility requirements extend to the full shopping experience. WooCommerce's core templates have improved substantially in recent versions, but third-party themes and plugins often undo that progress.
The Gutenberg block editor is significantly more accessible than the classic editor, but content authors still need to follow best practices to avoid creating violations.
The most efficient approach combines automated scanning with targeted manual testing.
Run your homepage, key landing pages, contact form, and checkout (if applicable) through an automated scanner. Automated tools catch 30–40% of WCAG violations instantly — color contrast failures, missing alt text, unlabeled inputs, and structural issues.
Disconnect your mouse and navigate your site using only Tab, Shift+Tab, Enter, Escape, and arrow keys. You should be able to reach every interactive element, activate every control, and never get stuck in a focus trap.
Test your homepage and one key conversion flow (contact form, checkout, or sign-up) with a free screen reader: NVDA on Windows or VoiceOver on Mac (Cmd+F5). Listen for unlabeled controls, missing context, and confusing reading order.
Fix critical violations first — keyboard traps, missing form labels, and images with no alt text are both high-impact and typically fast to fix. Color contrast fixes often require theme or CSS changes and may need more planning.
Run a free WCAG 2.1 accessibility scan on your WordPress site. Get a full report of violations, severity ratings, and remediation guidance in under 60 seconds.
🔍 Scan My WordPress Site →Accessibility is not a one-time task. WordPress sites drift out of compliance through routine content updates, plugin upgrades, and theme changes. Sustainable compliance requires:
Publishing an accessibility statement demonstrates good faith and is required under some regulations (Section 508, EAA). Your statement should:
WordPress.org maintains an accessibility statement for the core software that you can reference as a model.
WordPress accessibility is achievable without rebuilding your site. The right combination of an accessible theme, the WP Accessibility plugin, accessible forms, and a content governance process gets most sites to WCAG 2.1 AA compliance.
Related guides: Shopify Accessibility Guide · Wix Accessibility Guide · WCAG for E-Commerce · ADA Website Compliance 2026
Try it yourself
Enter your website URL to get a free accessibility score.