How to Pick an Accessibility Ready WordPress Theme

An accessibility ready WordPress theme is a theme that has passed a manual review by the WordPress theme review team and earned the accessibility-ready tag in the WordPress theme directory. The tag means the theme met the minimum standards set for that review. It does not mean the theme meets WCAG AA level, and it does not cover the posts, plugins or color choices you add later. Use it as a shortlist filter, then run the test below.

Key takeaways

• The accessibility-ready tag comes from a manual review, not from a claim on a sales page.
• The tag covers the theme against minimum standards. It is not a verdict on your finished site.
• A tagged theme can still fail on your site if your content, plugins or colors introduce problems.
• Ten minutes on a demo can reveal problems a tag alone will not show.
• A scan is a starting point, and a quick manual keyboard and screen reader check is part of good practice.

What the accessibility ready WordPress theme tag means

Filter the WordPress theme directory for the accessibility-ready tag to find themes that went through this review. A theme author adds the tag before submitting a new theme, and a tagged theme goes through an accessibility review as part of approval. A tagged theme may not be made live in the repository until it has passed an accessibility audit.

The review checks 18 items, covering a skip link, landmarks, keyboard support, named controls, labelled forms, heading structure, underlined and clear link text, contrast, alt text, accessible media, reflow and text spacing, stable context, warnings for new windows, accessible hover and focus content, an accessibility statement, no inaccessible plugin requirements, and screen reader text.

Read that list as a floor. The team calls these minimum requirements, so two tagged themes can differ a lot in daily use. An author must not add the tag without prior approval, and adding it without passing an audit could result in suspension. Tagged themes may be re-reviewed at any time.

What the tag does not cover

Your posts are not part of the theme review. If a post uses a heading order that jumps levels for no reason, or an image with no useful alternative text, the theme cannot fix that choice for you. The same applies to a page builder layout that adds its own markup, a form plugin that labels its fields poorly, or a slider plugin that traps keyboard focus.

Your color choices are also outside the original review once you change them. The review checks contrast in the theme as submitted. If you pick a pale body text color in the customizer, you can undo that part of the theme work in a few clicks, so check contrast again with your own palette. Test with the settings you plan to use.

The 10 minute theme test

Use the theme demo, a keyboard, and a browser, with no mouse for the keyboard parts. Work through a demo page, a post page, and a form page if one is offered. Note each result as pass, fail or unclear, per page.

Minutes 0 to 2: keyboard and skip link. Press Tab. A skip link should appear as the first focusable item and point to the main content. Press Enter on it, then press Tab again. Focus should land inside the main content, not back in the header menu. Then Tab through the menu: every mouse item should work by keyboard. WCAG 2.4.1 Bypass Blocks asks for a way past blocks repeated on multiple pages.

Minutes 2 to 4: headings. Read the heading order from the page source or browser developer tools. There should be one main heading for the page, with subheadings that follow in order, without a jump that skips a level for no reason. Headings should describe the section that follows them.

Minutes 4 to 6: focus. Tab through a post page and watch the focus indicator. WCAG 2.4.7 Focus Visible asks for a mode of operation where the keyboard focus indicator is visible. You should see where focus is at every step, on links, buttons, form fields and menu items. A faint outline that disappears against a light background is a weak result, and no outline at all is a fail.

Minutes 6 to 8: contrast. Pick the main body text color and its background color, then check the ratio with a contrast checker. WCAG 1.4.3 Contrast (Minimum) asks for at least 4.5:1 for ordinary text, and at least 3:1 for large-scale text. Check links in text as well, and check whether links are underlined, since the tag list requires underlined links in text.

Minutes 8 to 10: forms and links. Open a search or comment form. Each field should have a visible label, not only placeholder text, which disappears when you start typing and is not a label. Link text should make sense on its own.

Red flags that should stop a shortlist

No visible focus indicator should end a theme trial on the spot, even if the rest of the demo looks good. A menu that only opens on hover, with no keyboard path to its submenu items, is another. Links that rely on color alone, with no underline or other cue, fail the tag list. A form with no labels, or a search box that only shows placeholder text, is a sign the theme author did not work through the form items in the review list.

Watch for demo gaps too. A demo that shows only a homepage gives you no way to run the full test. Ask for post, archive and form pages, or install the theme on a test site and run the same 10 minutes there.

How Axeazy helps with this exact issue

A scan of your live site shows what your finished pages do, with your content, plugins and settings in place. Axeazy lists skip navigation, heading structure, landmark structure and keyboard tab order among its 14 fix categories. Read the honest scope page for what is covered, and the methodology page for how issues are scored.

For WordPress, the free WordPress plugin page describes a free plugin that applies 3 fixes instantly at render time, with no account needed: a skip navigation link, a page language attribute, and an alt text fallback. Paid plans add more, including weekly scans. That plugin can supply a skip link at render time, but it does not rewrite a theme template that lacks a main element, and it does not repair a theme menu that cannot be used by keyboard.

Axeazy detects contrast problems and calculates a correct color, but a visible color change is never applied without owner approval. Approve the replacement shade, then retest. For headings, see the heading structure guide on the blog. For the skip link test, see the skip link guide. Want a quick read on your own site? Run the free 60 second scan on the Axeazy home page. It needs no signup.

Last checked: October 26, 2026.

FAQ

Does the tag mean my site meets WCAG AA level?

No. The WordPress theme team states that the tag means the theme reaches the minimum standards set for the theme review, not that the theme meets WCAG AA level.

Can I keep the tag benefit if I change the theme colors?

You keep the theme, but you do not keep the contrast result from the review once you change the palette. The review checked contrast in the theme as submitted. If you pick new colors, check the ratio again against 4.5:1 for ordinary text and 3:1 for large-scale text.

What if the demo passes but my site fails the same test?

Compare the two setups page by page. Check whether a plugin, a page builder layout, a custom style or a changed setting differs from the demo. Test on a test copy with plugins turned off if you need to narrow the cause, then turn them back on one at a time and retest.

Does the Axeazy plugin replace picking a sound theme?

No. The free plugin applies 3 fixes instantly at render time, including a skip navigation link, and paid plans add more. It does not rewrite a broken menu, add a missing main element to a template, or fix a form that has no labels. Pick a theme that passes the keyboard, heading, focus and contrast checks first.

Should I test with a screen reader as well as a keyboard?

Yes, when you have time for a longer check. The 10 minute test uses a keyboard, headings, focus and contrast, which catches a large share of theme problems. A screen reader check adds whether headings, landmarks and link text make sense when read in order.

Sources

• WordPress Accessibility, checked October 26, 2026
• WordPress Accessibility-Ready Requirements, checked October 26, 2026
• W3C 2.4.1 Bypass Blocks, checked October 26, 2026
• W3C 2.4.7 Focus Visible, checked October 26, 2026
• W3C 1.4.3 Contrast (Minimum), checked October 26, 2026
• Axeazy WordPress plugin, checked October 26, 2026
• Axeazy capabilities, checked October 26, 2026
• Axeazy home, checked October 26, 2026