← Accessibility Insights & Resources

WordPress Accessibility: Themes, Plugins and Common Failures

Whether WordPress is accessible, what an "accessibility-ready" theme really promises, which plugins help, and the failures we find most often on WordPress sites.

Run a free scan of your WordPress site

WordPress itself is built with accessibility in mind, but that doesn't make a WordPress website accessible. The WordPress project commits its own code to WCAG 2.2 Level AA. Your site is that core software plus a theme, a set of plugins, possibly a page builder, and everything your team has published. Each of those layers can add barriers, and most of the problems we find on WordPress sites come from them, not from WordPress core.

So the honest answer to "is WordPress WCAG compliant?" is that the question is about the wrong thing. WCAG conformance is measured on the pages your visitors use. Two sites running the same version of WordPress can be at opposite ends of the scale.

This guide covers what WordPress does and doesn't promise, how to read the "accessibility-ready" theme tag, where page builders and plugins fit, the failures to look for, and who on your team can fix what.

Is WordPress accessible?

The core software aims to be. The WordPress accessibility coding standards say that code integrated into WordPress "is expected to conform to the Web Content Accessibility Guidelines (WCAG), version 2.2, at level AA." The project has an Accessibility Team that provides expertise across the project and reviews this work.

WordPress is also open about the limits. Its own accessibility page describes the goal as making the admin screens and the bundled themes meet WCAG 2.2 AA "where possible", says some features may not fully comply yet, and says the project cannot guarantee that all themes are compliant.

That leaves four things WordPress core has no control over on your site:

  • The theme. It produces most of the HTML your visitors get: the header, navigation, page layout, colours and focus styles.
  • Plugins. Forms, sliders, pop-ups, cookie banners, booking tools and shops each add their own markup and scripts.
  • A page builder, if you use one in place of the built-in block editor.
  • Your content. Headings, alt text, link text, documents and video are written by your team, and no software can get those right for you.

What the "accessibility-ready" theme tag means

The WordPress.org theme directory has an accessibility-ready tag. A theme can only use it after passing a manual review against a published list of requirements. It is the most useful filter available when you're choosing a free theme.

The required items in the theme review handbook include:

  • a skip to content link
  • meaningful landmark roles and names
  • keyboard navigation support
  • controls with accessible names, roles and states
  • labelled form fields
  • headings with a meaningful structure
  • underlined links in text, and no ambiguous link text
  • sufficient colour contrast for text and controls
  • support for reflow, text resizing and text spacing changes
  • no links that open a new window or tab without warning
  • the theme must not recommend or require inaccessible plugins

What the tag does not mean

It does not mean the theme, or your site, meets WCAG. The theme review handbook says so directly: "ready" does not mean that the theme meets the WCAG guidelines at Level AA. It means the theme reaches the minimum standards the theme review team has set. The handbook also points out that WCAG measures content, and a theme has no content until you add yours.

Keep three practical limits in mind:

  • The review covers the theme as submitted. If you change the colour palette, swap fonts or add custom CSS, you can undo what was reviewed. A brand colour that fails contrast fails whatever the theme's tag says.
  • It covers the theme, not your plugins. A form or slider plugin brings its own code.
  • The tag belongs to the WordPress.org directory. Themes sold elsewhere may describe themselves as accessible, but that is the seller's own claim and hasn't been through this review. Ask what was tested and how.

Page builders and accessibility

Many WordPress sites are built with a visual page builder, not the block editor that ships with WordPress. Page builders differ a lot from one another and change with every release, so we won't rank them here. What they have in common is that the builder, not WordPress core, generates your markup, and the WordPress coding standards don't apply to it.

These are the patterns to check on a builder-made page:

  • Headings chosen by look. When the heading level and the text size sit in the same panel, people pick the level that looks right.
  • Reading order that doesn't match the screen. Columns and absolutely positioned elements can be arranged visually in an order that differs from the order in the code, which is the order a screen reader and the Tab key follow.
  • Clickable things that aren't links or buttons. An icon box or image made clickable with a script may not be reachable by keyboard or announced as a control.
  • Interactive widgets. Tabs, accordions, carousels, pop-ups and mobile menus each need correct keyboard behaviour and correct states for screen readers.
  • Animation. Entrance effects and auto-playing backgrounds need a way to be paused or switched off.

None of this means you have to abandon your page builder. It means the builder's output has to be tested like any other code, and that settings your editors can reach (heading level, alt text, link text, colours) need a house rule.

WordPress accessibility plugins: what helps and what doesn't

Search the plugin directory for "accessibility" and you get two very different kinds of tool. It matters which one you install.

Checkers that flag issues while you edit

These plugins scan a post or page and list problems in or beside the editor: skipped heading levels, images with no alt text, vague link text, low contrast. They are useful because they catch mistakes at the moment the person who made them can fix them. WordPress's own training site has a lesson on testing your content for accessibility that walks through several.

The block editor also has two checks built in, described in that same lesson. The Outline tab in the Document Overview shows your heading structure and flags incorrect heading levels, and the colour settings warn you when a text and background combination may be hard to read.

A checker tells you about a problem. It doesn't fix it, and it can only find what can be detected in code. It can tell you an image has no alt text, not whether the alt text you wrote makes sense.

Overlay and toolbar plugins

The other kind adds a floating button to your site that opens a panel of options, such as larger text or higher contrast, often with a claim that it makes the site compliant. It doesn't. An overlay doesn't change your theme, your templates, your forms or your PDFs, and WCAG conformance is judged on what your site actually delivers. We cover the detail, including the US Federal Trade Commission's 2025 order against one overlay vendor, in accessibility overlays and compliance.

A quick test for any plugin: does it help you find and fix problems in your own content and code, or does it promise to make them go away without anyone fixing anything? The first kind is worth having.

See what an automated scan finds on your site

Our free scan checks your WordPress site for common barriers such as missing alt text, low contrast and unlabelled form fields. It's a starting point, not an audit.

Run a free scan

Common WordPress accessibility failures

These are the issues we look for first when we audit a WordPress site. The success criterion numbers refer to WCAG 2.2; all of the ones named here are also in WCAG 2.0.

Heading levels chosen for size

An H4 picked because H2 "looked too big", or bold paragraphs standing in for headings. Screen reader users navigate by heading level, so the levels have to describe the structure of the page (1.3.1 Info and Relationships). In the block editor, set the level for structure and change the size separately under Typography. See accessible headings and page structure.

Missing alt text in the media library

Images uploaded with an empty Alt Text field, or with the file name left in it (1.1.1 Non-text Content). One WordPress detail catches people out. According to the Image block documentation, alt text in the Media Library sets the default used when you insert the image, while alt text edited on the block applies only to that page. So check the images already placed in your pages, not only the library. Our image accessibility guide covers what to write.

"Read more" links

Blog listings and card grids that repeat "Read more", "Learn more" or "Click here" for every item. Out of context, a screen reader user hears the same link ten times and can't tell them apart (2.4.4 Link Purpose). Sometimes this is the excerpt setting in your theme and sometimes it's a block or pattern an editor added by hand.

Sliders and carousels

Hero sliders that rotate on their own with no pause button fail 2.2.2 Pause, Stop, Hide, which applies to content that moves automatically for more than five seconds alongside other content. The W3C carousel tutorial also asks for full keyboard operation and for slide changes to be communicated to screen reader users. Many slider plugins miss at least one of these. The simplest fix is often a single static image.

Form plugins: labels and error handling

Contact, quote and sign-up forms where placeholder text is used in place of a label, where required fields are marked only by colour, or where an error appears as a red border with no message a screen reader will announce (3.3.1 Error Identification, 3.3.2 Labels or Instructions). Some of this is the plugin's markup and some is how the form was set up, so check both. Details are in our form field accessibility guide.

Menus that don't work with a keyboard

Dropdown menus that only open on mouse hover, mobile menu buttons that can't be reached or operated with the keyboard, and menus that open but trap focus or let it wander behind the panel (2.1.1 Keyboard). Test this yourself in two minutes: put the mouse aside and use Tab, Shift+Tab, Enter and Escape to reach every page in your navigation.

Embedded PDFs

Price lists, menus, application forms and reports uploaded as PDFs and linked or embedded in a page. The PDF is part of your web content, and a scanned or untagged PDF is unreadable to a screen reader no matter how good the page around it is. Where you can, publish the information as a normal page. Where you can't, fix the document: see common PDF accessibility errors and solutions.

Low contrast theme palettes

Light grey body text, white text on a pale brand colour, and links that differ from the surrounding text only by a slightly different shade. WCAG asks for a contrast ratio of at least 4.5:1 for normal-size text (1.4.3 Contrast (Minimum)). The cause is usually the theme's default palette or colours picked in the site editor, which means one change can fix it site-wide.

What an editor can fix and what needs a developer

A good share of WordPress accessibility work needs no code at all. The table shows where each common failure is usually fixed. Your set-up may differ: on some sites an editor can reach theme colours, and on others they're locked down.

Common WordPress accessibility failures and who can usually fix them
IssueA content editor canNeeds a developer or a theme or plugin change
HeadingsSet the right level on each Heading block and check the OutlineHeading levels hard-coded in the theme's templates, widgets or footer
ImagesWrite alt text, or mark an image as decorative, in the block settingsImages output by the theme or a plugin with no alt text field
Link textRewrite "click here" links and button labels in page content"Read more" links generated by the theme or a listing block
Colour contrastChoose passing colours on individual blocks and act on the editor's warningThe theme's palette, link styles and focus indicators
Forms Give every field a visible label and clear instructions in the form plugin's settings How the plugin marks up labels, required fields and error messages
MenusKeep menu labels clear and the structure simpleKeyboard operation, focus handling and the mobile menu button
SlidersTurn off autoplay if there's a setting, or replace the slider with an imageKeyboard support, a pause control and screen reader announcements
PDFs and videoPublish content as a page where possible; add captions and transcriptsAn accessible media player, if the current one can't be used by keyboard
Page structureNot usually editableSkip link, landmarks, page language and page titles from the theme

Two things follow from this. Train the people who publish, because content mistakes come back every week if nobody knows the rules. And fix theme and plugin problems once at the source, where a single change repairs every page that shares the template.

How the AODA applies to a WordPress site

Ontario's accessibility law doesn't care what your site is built with. Under the Integrated Accessibility Standards Regulation, public sector organizations and private or non-profit organizations with 50 or more employees in Ontario must make their public websites and web content conform to WCAG 2.0 Level AA, other than live captions and pre-recorded audio description. Our AODA requirements guide sets out who is covered.

The obligation sits with your organization, not with WordPress, your theme's author or a plugin vendor. An accessibility-ready theme or an installed plugin is not evidence that your site conforms. What counts is how your pages behave when someone uses them with a keyboard or a screen reader.

Organizations with 20 or more employees also file an accessibility compliance report every three years, and for those with 50 or more that report asks about the website. If you're not sure where you stand, an AODA website audit tests your site by hand against WCAG 2.2 AA, which covers the WCAG 2.0 AA criteria the regulation requires. Our fixed packages are on the pricing page. This is general information, not legal advice.

Frequently asked questions

Is WordPress WCAG compliant?

WordPress core is written to a WCAG 2.2 Level AA coding standard, and the project says it can't guarantee every part complies. Your website's conformance depends on your theme, plugins, any page builder and your content, so it has to be tested as a whole.

Does an accessibility-ready theme make my site compliant?

No. The tag means the theme passed the WordPress theme review team's minimum accessibility requirements. The theme review handbook says it does not mean the theme meets WCAG Level AA, and it says nothing about your plugins, your colour changes or your content.

Which WordPress accessibility plugin should I install?

Choose one that checks your content in the editor and tells you what to fix. Avoid relying on a toolbar or overlay plugin that claims to make the site compliant by itself. No plugin replaces fixing the theme, the forms and the content.

Is the block editor better for accessibility than a page builder?

The block editor is part of WordPress core, so it falls under the project's accessibility coding standards, and it has built-in heading and contrast checks. Page builders vary. Either can produce accessible or inaccessible pages, so test the output instead of trusting the tool.

Do I need to rebuild my WordPress site to make it accessible?

Usually not. Many barriers are fixed in content, in theme styles or by replacing one plugin. A rebuild is worth considering when the theme or page builder itself produces barriers you can't fix, and an audit will tell you whether that's the case.

Does the AODA apply to my WordPress website?

The AODA website requirement applies by type and size of organization, not by platform. If you're an Ontario public sector organization, or a business or non-profit with 50 or more employees, your public website must meet WCAG 2.0 Level AA whatever it is built with.