WordPress powers a huge share of the web, which means WordPress sites are also among the most common targets of accessibility complaints. The good news: most barriers on WordPress sites come from a short list of repeat problems in themes, page builders and content. Fix those and you are a long way towards WCAG 2.2 Level AA.
Use this checklist to audit your site. Each item explains what to check, why it matters and how to fix it in WordPress.
Theme and structure
1. Start with an accessibility-ready theme
Themes tagged accessibility-ready in the WordPress.org directory have passed a basic review for keyboard navigation, skip links, headings and contrast. If you use a premium or custom theme, test it yourself: it is the foundation every page inherits.
2. Keep a logical heading order
Each page should have one H1, usually the page or post title, followed by H2s for sections and H3s inside them. Don’t pick heading levels for their size. In the block editor or Elementor, choose the level for structure and adjust the look with styles.
3. Make sure there is a skip link
A “Skip to content” link lets keyboard users jump past the menu. Press Tab once on your home page: the first thing that appears should be a visible skip link that moves focus to the main content.
4. Set the page language
Screen readers use the language attribute to pronounce text correctly. Check Settings → General → Site Language, and if you run a multilingual site with Polylang or WPML, confirm each language version sets its own lang attribute.
Navigation and keyboard
5. Test the whole site with a keyboard
Put your mouse aside and use Tab, Shift+Tab, Enter and Space. You should be able to open menus, use sliders, submit forms and close pop-ups. Mega menus and off-canvas mobile menus are frequent failures.
6. Keep focus visible
Many themes remove the browser’s focus outline for looks. WCAG 2.2 requires a visible focus indicator, and focused elements must not be hidden behind sticky headers or cookie banners. Add a clear outline in your theme’s CSS, for example :focus-visible { outline: 3px solid #1f2beb; outline-offset: 3px; }.
7. Size touch targets properly
WCAG 2.2 introduced a minimum target size of 24 by 24 CSS pixels for most interactive elements. Check icon-only buttons such as social links, carousel arrows and close buttons on mobile.
Content
8. Write meaningful alt text
Add alt text in the Media Library or the image block for every image that carries information, and leave it empty for purely decorative images. See our guide on how to write alt text that works for examples.
9. Use descriptive link text
“Click here” and “Read more” make no sense out of context, and many screen reader users browse by a list of links. Write links that describe the destination, such as “Read our accessibility statement”.
10. Check colour contrast
Normal text needs a contrast ratio of at least 4.5:1 against its background, and large text 3:1. Light grey body text, text over images and coloured buttons are the usual offenders. Fix colours in your theme or page builder’s global settings so the change applies everywhere.
Forms, media and plugins
11. Label every form field
Every input needs a visible label, not just a placeholder that disappears when you type. Error messages should say what went wrong and how to fix it. Test your contact form, newsletter sign-up and WooCommerce checkout, and avoid image-based CAPTCHAs, which lock out many users.
12. Caption videos and check PDFs
Add captions to videos and transcripts to audio. PDFs uploaded to WordPress are part of your site too: they need tags, a title and a logical reading order, or an accessible HTML alternative.
13. Audit your plugins
Sliders that auto-play, pop-ups that trap focus, chat widgets without labels and cookie banners that can’t be closed with a keyboard are common plugin problems. Make sure anything that moves can be paused, and replace plugins that can’t be fixed.
Keep it accessible over time
Accessibility on WordPress isn’t a one-off project. Every new post, plugin update and page builder change can introduce problems. A sustainable process looks like this:
- Scan the whole site regularly and after major updates
- Give editors simple guidance on headings, links and alt text
- Test new templates with a keyboard before launch
- Publish an accessibility statement and keep it current
Frequently asked questions
Is WordPress accessible out of the box?
WordPress core and its default themes are built with accessibility in mind, but your theme, plugins, page builder and content decide whether your actual site is accessible.
Are page builders like Elementor accessible?
They can be. Choose heading levels carefully, add labels to icon-only buttons, check contrast in global colours, and avoid animations that can’t be paused.
Do I need a developer to make my WordPress site accessible?
Many fixes, like alt text, headings, link text and contrast, can be done in the editor. Theme and plugin issues sometimes need a developer, or a managed remediation service.
Check your WordPress site in minutes
The Reguweb WordPress plugin connects your site in one click. It scans every page against WCAG 2.2, suggests AI-written alt text, alerts you to vulnerable plugins and adds an accessibility widget for visitors. Run a free scan now, or start a 14-day free trial with no credit card.
On this page
Is your website compliant?
Get your WCAG 2.2 and SEO scores in about 60 seconds. No sign-up needed.
