Accessibility guide

WordPress Accessibility: How to Make a WordPress Site Accessible

WordPress powers a large share of the web, so "how do I make my WordPress site accessible?" is a common question. The honest answer is that themes and plugins help, but no plugin makes a site accessible on its own. This guide covers accessibility-ready themes, where plugins do and do not help, and the manual testing you still need.

Reviewed by the EAA Navigator team

TL;DR

  • Accessibility starts with the theme: choose an accessibility-ready theme and keep your content structured (headings, alt text, link text).
  • Plugins can help with specific tasks, but no plugin makes a site compliant, and accessibility overlay plugins do not equal compliance.
  • Most WCAG issues — contrast, alt text, keyboard operation, focus order — are decided by your content and design choices, not by a plugin.
  • You still need manual testing: keyboard-only navigation and a screen-reader pass on your key templates.
Get the WCAG ChecklistBrowse all guides

In this guide

What this covers

  • Choosing an accessibility-ready theme and what that label does and does not guarantee.
  • Where plugins genuinely help, and the honest limits of accessibility plugins.
  • Why overlay plugins are not a compliance solution.
  • The manual testing that no WordPress plugin can replace.

What matters

Key points

  • Themes matter most: an accessibility-ready theme gives you sensible heading structure, keyboard support and focus styles to build on, but your content and customisations can still break it.
  • Plugins help with tasks, not compliance: a plugin can help you add captions or check contrast, but installing a plugin does not make the whole site conformant.
  • Overlay plugins are not compliance: widgets that promise instant accessibility cannot fix most WCAG issues, and overlay-equipped sites are still sued. Automated tooling alone catches only about 30 to 40 per cent of issues.
  • Content is where most failures live: missing alt text, vague link text ("click here"), poor contrast and skipped heading levels are authoring choices, not plugin settings.

Across web accessibility, Level AA of WCAG 2.2 is the working target, and for the EU it is incorporated into the harmonised standard EN 301 549.

What to do

What to do next

  1. Start with an accessibility-ready theme and check it with the keyboard before you build on it.
  2. Set WCAG 2.1 AA (or 2.2 AA) as your target and structure content properly: one H1, logical headings, meaningful link text and alt text on images.
  3. Use plugins for specific jobs (captions, contrast checking, form labels), not as a compliance guarantee — and avoid overlay widgets that claim instant compliance.
  4. Test manually: navigate every key template with the keyboard only, then run a screen-reader pass on your home page, a post and any forms.
  5. Publish an accessibility statement and arrange a manual audit for anything you cannot confidently test yourself.

For the standard itself, see the WCAG explainer; to put it into practice, work through the WCAG 2.2 AA checklist.

FAQ

Common questions

Is there a plugin that makes WordPress accessible?
No. Plugins can help with specific tasks such as captions or contrast checking, but no plugin makes a site compliant on its own. Most WCAG issues depend on your theme, content and design choices, which a plugin cannot fix automatically.
Do accessibility overlay plugins work for WordPress?
Overlay plugins do not make a site compliant. Automated tooling detects only about 30 to 40 per cent of WCAG issues, and overlay-equipped sites are still subject to complaints and lawsuits. Treat overlays as, at best, a minor convenience and not a compliance solution.
What is an accessibility-ready theme?
It is a theme reviewed against a set of accessibility requirements — such as keyboard navigation, sufficient contrast and proper heading structure. It gives you a sound starting point, but your content and customisations can still introduce barriers, so testing is still needed.
How do I test my WordPress site for accessibility?
Combine automated checks with manual testing: navigate your key templates using only the keyboard, run a screen-reader pass on your home page, a post and any forms, and check colour contrast. For anything you cannot confidently assess, commission a manual audit.

Make your site accessible

Start with the WCAG 2.2 AA checklist, then work through the guides to fix what you find.

Get the WCAG ChecklistTry the contrast checker

This is guidance, not legal advice

This guide is here to help you understand web accessibility and how WCAG, the EAA and the ADA apply in practice. It is not legal advice. For decisions specific to your business, confirm with the official sources we link or a qualified adviser.

Sources

  1. [1]Web Content Accessibility Guidelines (WCAG) 2.2 (W3C Recommendation)retrieved 9 Jun 2026
  2. [2]WCAG overview (W3C Web Accessibility Initiative)retrieved 9 Jun 2026
  3. [3]Directive (EU) 2019/882 — European Accessibility Act (EUR-Lex)retrieved 9 Jun 2026
  4. [4]EN 301 549 v3.2.1 — harmonised ICT accessibility standard (ETSI)retrieved 9 Jun 2026
  5. [5]US DOJ ADA Title II web accessibility rule fact sheetretrieved 9 Jun 2026
  6. [6]WebAIM Million 2025 — accessibility of the top 1,000,000 home pagesretrieved 9 Jun 2026
  7. [7]Overlay Fact Sheet — why overlays do not deliver complianceretrieved 9 Jun 2026

The Accessibility Brief

Subscribe to The Accessibility Brief

We watch the standards so you don't. Plain-English WCAG, EAA and ADA updates, free.

No spam. Unsubscribe anytime.

WordPress Accessibility: Themes, Plugins & Testing | EAA Navigator · EAA Navigator