WordPress ADA Compliance: Complete Guide for Site Owners

WordPress powers 43% of all websites on the internet. That means hundreds of millions of websites news sites, business pages, non-profits, medical practices, e-commerce stores are built on WordPress. And the vast majority of them fail basic WordPress accessibility plugin WCAG.

According to WebAIM’s 2025 Million report, 95.9% of homepages tested had detectable WCAG failures. For WordPress sites, the most common culprits are theme-level colour contrast failures, unlabelled form inputs, and missing alt text issues that put site owners at legal risk and lock disabled users out of your content.

This guide gives WordPress site owners a complete, developer-optional path to WCAG 2.2 AA compliance from theme selection through ARIA implementation, keyboard navigation, and the fastest way to deploy an ADA-compliant widget.

1. Does WordPress Need to Be ADA Compliant?

Yes and “I’m using WordPress” is not a defence. The ADA applies to the website and its owner, not the platform it is built on.

Title III of the Americans with Disabilities Act requires that businesses open to the public make their services accessible to people with disabilities. Federal courts have ruled consistently that this includes websites. The DOJ’s 2022 guidance named WCAG 2.1 AA as the applicable standard, and WCAG 2.2 (released October 2023) is increasingly cited in updated legal opinions.

Who is most at risk?

WordPress-powered businesses in high-litigation categories are frequent ADA lawsuit targets:

• Healthcare providers and medical practices
• Legal services and law firm websites
• Real estate agencies
• E-commerce stores (especially WooCommerce)
• Hospitality, restaurants, and tourism
• Educational institutions

ADA demand letters typically arrive without warning and demand settlement within 30 days. The average settlement cost is $25,000–$75,000, not including legal fees. For a business running on WordPress without accessibility measures, the question is not if it is when.

2. Choosing an Accessible WordPress Theme

The single most impactful decision for WordPress accessibility is your theme. A poorly coded theme creates hundreds of accessibility failures that no plugin can fully remediate.

What Makes a WordPress Theme Accessible?

Look for these characteristics:

• Semantic HTML structure: Correct use of <header>, <main>, <nav>, <article>, <aside>, <footer> elements
• Skip navigation link: A “Skip to main content” link as the first focusable element on every page
• Visible focus indicators: Custom :focus styles that meet WCAG 2.4.11 contrast requirements (new in WCAG 2.2)
• Keyboard-navigable menus: All dropdowns and mega-menus accessible without a mouse
• ARIA landmark roles: role=”banner”, role=”navigation”, role=”main”, role=”contentinfo” present
• Adequate colour contrast: Text/background combinations that meet 4.5:1 (normal text) and 3:1 (large text) ratios

Accessible WordPress Themes Recommended for 2026

Free themes with strong accessibility:

• Twenty Twenty-Four (WordPress default) WordPress maintains these for core accessibility compliance
• Twenty Twenty-Three consistently updated
• Astra (Accessibility Ready version) popular, well-supported, excellent keyboard navigation

Premium themes with accessibility documentation:

• GeneratePress lightweight, semantic HTML, documented accessibility features
• Kadence WP actively maintained with accessibility improvements
• Blocksy strong WCAG support with documented compliance features

Warning: Page builder caution. Themes built primarily for Elementor, Divi, or WPBakery Visual Composer can introduce significant accessibility issues depending on how components are configured. Use these tools with accessibility in mind not as an afterthought.

3. WordPress Accessibility Settings You Should Enable Today

WordPress core has built-in accessibility features that many site owners never activate:

In the Dashboard

Settings → Discussion:

• Enable comment form accessibility ensure comment labels are properly associated

Users → Profile:

• Enable the “Reduce motion” admin option if you manage admin users with vestibular disorders (not front-end, but good practice)

Gutenberg Block Editor: Gutenberg (the WordPress block editor) has improved significantly for accessibility. Ensure you are running the latest WordPress version to benefit from the most recent ARIA and keyboard navigation improvements.

Accessibility-Related Plugin Settings to Review

If your site uses Contact Form 7, WPForms, Gravity Forms, or any form plugin visit their settings and enable:

• Visible field labels (not just placeholders)
• Error identification that does not rely on colour alone
• Success/error announcements compatible with screen readers

4. ARIA in WordPress: What You Need to Know

ARIA (Accessible Rich Internet Applications) is a set of HTML attributes that communicate the purpose and state of interactive elements to assistive technologies. For WordPress sites, ARIA matters most in:

Navigation Menus

WordPress’s built-in navigation menus should include:

<nav aria-label=”Primary Navigation”>

  <ul>

    <li><a href=”/about”>About</a></li>

    <li>

      <button aria-expanded=”false” aria-haspopup=”true”>Services</button>

      <ul>…</ul>

    </li>

  </ul>

</nav>

The aria-expanded attribute must toggle between true and false as dropdowns open and close. Many WordPress themes implement the dropdown HTML structure but fail to update ARIA states via JavaScript.

Sliders and Carousels

Sliders are among the most inaccessible components on the web. If your WordPress theme or homepage uses a slider:

• The slider must be pause able (SC 2.2.2)
• Individual slides must have role=”group” and aria-label attributes
• Navigation arrows must have accessible names (aria-label=”Next slide”)

If you cannot implement these changes, consider replacing the slider with static content or a well-built alternative.

Modals and Popups

If your site uses popups (newsletter sign-ups, cookie notices, promotions):

• The modal must receive focus when it opens
• Tab focus must be trapped within the modal while it is open
• The modal must close on Escape key press
• Focus must return to the trigger element when the modal closes

Many WordPress popup plugins fail these requirements. Test any popup plugin before deployment.

Custom Post Types and Dynamic Content

If your WordPress site uses custom post types, Ajax-loaded content, or single-page application-style navigation:

• Content updates must be announced to screen readers via aria-live regions
• Dynamic loading indicators must have accessible labels
• History-based navigation (back/forward) must work correctly

5. Keyboard Navigation: Testing and Fixing

How to test keyboard navigation on your WordPress site:

1. Open your site in Chrome or Firefox
2. Disconnect your mouse
3. Press Tab to move forward through interactive elements; Shift+Tab to move backward
4. Press Enter to activate links and buttons; Space to activate buttons and checkboxes
5. Press Escape to close any modals or dropdowns

What you should see:

• A clearly visible focus indicator on every focusable element
• Logical focus order that follows visual page flow
• All menus, modals, and interactive components operable by keyboard
• No “keyboard traps” you should always be able to Tab away from any component

Common keyboard navigation failures in WordPress:

• Mega menus that open on hover but have no keyboard equivalent
• Slider “next/prev” arrows that receive no keyboard focus
• Embedded maps (Google Maps iframes) that trap keyboard focus
• Video players without keyboard-accessible controls
• Cookie consent bars that block Tab navigation to the main content

Fixing focus indicators in WordPress:

If your theme removes the default browser focus ring (many do, citing design reasons), add this to your theme’s style.css or the Additional CSS section in Customizer: focus-visible {outline: 3px solid #0073e6;outline-offset: 2px;}

WCAG 2.2 SC 2.4.11 requires that focus indicators have a contrast ratio of at least 3:1 against adjacent colors ensure your chosen color meets this.

6. Form Accessibility in WordPress

Forms are the most failure-prone element on most WordPress sites. Contact forms, quote forms, checkout forms, and newsletter sign-ups regularly fail WCAG criteria.

The Critical Rules for Accessible WordPress Forms

1. Every input must have a <label> Placeholder text is not a label. The label must be visible at all times not just when the field is empty.
2. Required fields must be identified in text Do not use color alone (red asterisks without text explanation violate SC 1.4.1). Include a legend such as “Fields marked with * are required.”
3. Error messages must be specific “Please correct the errors above” is insufficient. Each error message must identify which field has the error and explain how to fix it.
4. Success messages must be announced to screen readers After form submission, use aria-live=”polite” to announce the success message so screen reader users know the form submitted successfully.

Best Accessible Form Plugins for WordPress (2026)

• WPForms (with accessibility mode enabled in settings) generally good WCAG compliance
• Fluent Forms lightweight, well-structured labels
• Gravity Forms powerful, accessible when configured correctly

Avoid form plugins that rely on unlabeled icon buttons, floating labels that disappear on focus, or reCAPTCHA without an audio alternative.

7. Image Alt Text: The WordPress Workflow

WordPress makes alt text management straightforward if you use it consistently.

For New Images

Every time you upload an image to the WordPress Media Library:

1. Click the image in the Media Library
2. Find the “Alt Text” field in the right sidebar
3. Write a description of the image’s content and purpose
4. For decorative images (purely visual, no information), leave alt text blank (an empty alt=”” attribute tells screen readers to skip the image)

For Existing Images

Run the free Image SEO plugin or audit your Media Library manually. Sort by images with missing alt text and work through them in batches.

Alt Text Best Practices

• Describe the content and purpose: “Dog trainer demonstrating sit command with golden retriever at park” not “dog image”
• For product images: Include color, material, and key feature: “Navy blue wool men’s blazer with two-button front”
• For charts and graphs: Describe the data: “Bar chart showing 40% increase in mobile accessibility failures from 2023 to 2025”
• For logos: “[Company name] logo” is sufficient
• For purely decorative images: Leave alt text empty do not write “decorative image” as that gets read aloud by screen readers

8. Color Contrast in WordPress Themes

Color contrast is the most common WCAG failure on WordPress sites. WebAIM’s 2025 Million report found low contrast text on 81% of tested homepages.

WCAG Contrast Requirements

Text Size	Minimum Ratio (AA)	Enhanced Ratio (AAA)
Normal text (< 18pt or < 14pt bold)	4.5:1	7:1
Large text (≥ 18pt or ≥ 14pt bold)	3:1	4.5:1
UI components and graphical objects	3:1	—
Focus indicators (WCAG 2.2)	3:1	—

Fixing Contrast in WordPress

1. Identify failures: Use the WebAIM Contrast Checker or the WAVE browser extension
2. Adjust theme colors: In WordPress Customizer → Colors, adjust text and background colors
3. Page builder color panels: In Elementor or Gutenberg, check global color settings under Site Editor → Styles → Colors
4. Hard-coded theme colors: If your theme CSS has hard-coded colors that are not adjustable via Customizer, you may need a CSS override or to switch themes

9. The Best WordPress Accessibility Plugin: Accessify

After addressing manual issues (alt text, labels, contrast, keyboard nav), a WordPress accessibility plugin handles the automated layer providing users with real-time adjustments to how they experience your site.

Accessify is the leading WordPress accessibility widget for 2026, offering:

• Accessibility toolbar with profiles for visually impaired, motor-impaired, colour-blind, and cognitive accessibility needs
• Keyboard navigation enhancement improves focus management across standard and custom components
• WCAG 2.2 AA compliance dashboard shows your site’s accessibility score and flags issues for manual remediation
• Screen reader optimisations ARIA labels and landmarks injected where missing in standard theme components
• Text and spacing controls users can adjust font size, line height, letter spacing, and word spacing
• Contrast and color profile switching high contrast, monochrome, low saturation
• Link and button highlighting critical for users with cognitive disabilities

Accessify does not conflict with popular WordPress page builders (Elementor, Divi, Beaver Builder, Gutenberg) and has been tested on over 100 active WordPress themes.

10. How to Install Accessify on WordPress

Method 1: WordPress Plugin Directory (Recommended)

1. Log in to your WordPress admin dashboard
2. Go to Plugins → Add New
3. Search for “Accessify”
4. Click Install Now, then Activate
5. Go to Settings → Accessify and connect your Accessify account
6. Configure widget position (bottom-left or bottom-right) and initial profile
7. Save settings the widget is now live

Total time: approximately 3 minutes.

Method 2: Manual Script Installation

1. Go to accessify.app and log in to your dashboard
2. Copy your unique script snippet
3. In WordPress admin, go to Appearance → Theme File Editor → header.php (or use a plugin like “Insert Headers and Footers”)
4. Paste the script just before the closing </head> tag
5. Save the widget is live immediately

Post-Installation Steps

After installing Accessify:

1. Test the widget on desktop and mobile
2. Verify keyboard navigation still functions correctly
3. Check your Accessify dashboard for any immediate compliance flags
4. Set up monthly compliance report emails

11. Manual vs Automated Accessibility: What Each Covers

Understanding the boundary between what Accessify (and any widget) can fix automatically versus what requires manual intervention saves time and prevents false confidence.

Issue Type	Accessify Handles	Requires Manual Fix
Colour contrast for text	✅ (user-facing adjustments)	✅ Fix at theme level for default view
Missing alt text	❌ (flags the issue)	✅ Must be written manually
Form label association	⚠️ Partial ARIA injection	✅ Full fix requires label HTML
Keyboard focus indicators	✅ Enhanced focus styles	✅ Underlying CSS fix recommended
Skip navigation	✅ Injected if missing	—
Video captions	❌ (flags missing captions)	✅ Captions must be added to video
PDF document accessibility	❌	✅ PDFs need separate remediation
ARIA on custom components	⚠️ Standard components only	✅ Custom components need code fix
Screen reader text alternatives	⚠️ Landmark roles	✅ Complex components need dev work

 

The combination of manual fixes + Accessify covers 85–95% of WCAG 2.2 AA requirements for typical WordPress sites.

12. WordPress Multisite and WooCommerce Accessibility

WordPress Multisite

For WordPress Multisite networks, Accessify can be deployed network-wide via a network-activated plugin or by inserting the script into the shared header.php. Each site in the network can use the same Accessify account with separate per-site tracking in the dashboard.

WooCommerce Accessibility

WooCommerce stores require specific accessibility attention:

• Product pages: Ensure “Add to Cart” buttons have descriptive ARIA labels (not just “Add to Cart” screen reader users browsing multiple products need context: “Add Blue Wool Blazer to Cart”)
• Cart and checkout: Test the full checkout flow with a screen reader (NVDA + Firefox is the recommended test combination)
• Account pages: Login and registration forms must meet form labelling requirements
• Order confirmation emails: While not subject to WCAG directly, consider accessible email design as a UX best practice

Accessify’s WooCommerce compatibility is maintained and tested with WooCommerce 8.x+.

Conclusion

WordPress ADA compliance in 2026 is achievable for any site owner no developer required for the fundamentals. The combination of a well-chosen accessible theme, good content practices (alt text, form labels, headings), and Accessify’s automated compliance layer puts WCAG 2.2 AA compliance within reach for any WordPress-powered business.

The most common mistake is waiting. ADA demand letters arrive without warning, and the remediation cost under pressure is always higher than proactive compliance.

Start your free Accessify trial and get your WordPress site compliant today →

FAQ

What is the best accessibility plugin for WordPress?