Platform guide
WordPress Accessibility: A Practical Guide
WordPress core is solid — but your theme, page builder, plugins, and content decide the outcome. Here’s where to focus.
WordPress powers a huge share of the web, which means a huge share of accessibility problems live there too. WordPress core has improved a lot, but your site’s accessibility is ultimately decided by your theme, page builder, plugins, and content. This guide breaks down where the issues actually come from and how to fix them.
Where accessibility is won or lost
WordPress core follows accessibility coding standards, but most real-world issues come from the theme, a page builder (Elementor, Divi, WPBakery), plugins, and the content editors add. That’s where to focus.
WordPress and accessibility
A clean, well-coded theme with good content can be highly accessible. A heavy page-builder theme stuffed with plugins and unlabeled widgets often isn’t. The platform gives you the tools; the outcome depends on your stack and habits.
The four layers that affect accessibility
| Layer | What to do |
|---|---|
| Core | Keep it updated; it follows accessibility-ready standards. |
| Theme | Choose an “accessibility-ready” theme (a tag in the theme directory). |
| Page builder / plugins | Each injects markup — test what they output. |
| Content | Alt text, heading order, link text, contrast — your editors’ daily choices. |
Common WordPress accessibility issues
- Missing image alt text — the media library has an alt field; it’s often skipped. (How to write alt text.)
- Broken heading structure — builders that drop multiple H1s or skip levels for visual styling.
- Low contrast from theme palettes and button styles.
- Unlabeled form fields in contact and comment forms.
- Vague link text — “Read more” auto-appended to every excerpt (see the link auditor).
- Inaccessible sliders, popups, and menus from plugins that ignore keyboard and ARIA.
- PDFs uploaded to the media library that aren’t themselves accessible.
How to fix them
- Pick an accessibility-ready theme (filter by that tag) or audit your current one.
- Set alt text on every meaningful image in the media library and when inserting blocks.
- Use real heading blocks in order — H1 for the title, H2/H3 for sections — not just big bold text.
- Check contrast on your palette and button styles; adjust in the customizer or theme settings.
- Test plugin output with a keyboard and a screen reader before relying on a slider or popup.
- Re-test after updates. Core, theme, and plugin updates can reintroduce issues — continuous monitoring catches regressions.
Accessibility plugins: helpful vs. harmful
Two very different things share the “accessibility plugin” label:
- Helpful: testing/authoring aids that flag issues in the editor or help you add proper markup. Use these.
- Harmful (overlays): one-click widgets that promise instant compliance. They don’t fix your code, can disrupt assistive tech, and are lawsuit magnets. Avoid these.
Rule of thumb
If a plugin claims it makes your site “compliant” by adding one script, it’s an overlay. Real accessibility comes from accessible themes, content, and plugin output — not a widget.