A WordPress site can pass a quick visual review, score well on page speed and still stop a visitor cold. The mobile menu will not open from the keyboard. The contact form shows "This field is required" without saying which field. The "Read more" links all sound identical to a screen reader. None of these problems is rare, and most can be fixed.
WordPress powers a large share of the web, and its accessibility depends on far more than the core software. In this guide, SETN Consultants walks through ten common WordPress accessibility issues, how to test for each one and how to prioritize the fixes.
Why WordPress accessibility varies by theme, plugins and content
WordPress core is built with accessibility in mind, and its Make WordPress Accessible team reviews core features. But what visitors experience is the combined output of your theme, page builder (such as Divi or Elementor), plugins, custom code and the content your team publishes. An "accessibility-ready" theme can still be undone by an inaccessible slider plugin or by headings chosen for their size rather than their meaning. Effective review evaluates the whole stack.
Problems 1–3: missing labels, weak focus and inaccessible menus
1. Controls without accessible names. Icon-only buttons, such as search magnifiers, hamburger menus, social icons and slider arrows, often have no text that assistive technology can announce. Fix: add visually hidden text or an aria-label that describes the action, such as "Open menu."
2. Weak or missing focus indicators. Many themes remove the browser's focus outline because a designer found it unattractive. Keyboard users then cannot tell where they are. Fix: provide a clear, high-contrast :focus-visible style for every link, button and field.
3. Menus that only work with a mouse. Hover-only dropdowns and mobile menus built from non-button elements are among the most common keyboard navigation failures on WordPress. Fix: use real buttons for toggles, support Enter and Space, expose the expanded or collapsed state with aria-expanded, and return focus sensibly when the menu closes.
Test: unplug the mouse and Tab through the header, menu and footer. You should always see where focus is and be able to open, use and close every control.
Problems 4–6: low contrast, poor headings and links without context
4. Low color contrast. Light gray body text, pale buttons and text over photos often fall short of WCAG AA, which requires a contrast ratio of 4.5:1 for normal text and 3:1 for large text and essential interface elements. Fix: check your brand palette once in a contrast checker and set compliant colors in your theme settings, so every page inherits them.
5. Headings used for styling. Page builders make it easy to choose H4 because it "looks right," or to skip from H1 to H5. Screen reader users navigate by headings, so the structure needs to make sense. Fix: use one H1 per page, nest H2 and H3 headings logically, and control appearance with styles rather than heading levels.
6. Links without context. Blog grids full of "Read more" and "Click here" links are meaningless when a screen reader lists them out of context. Fix: use descriptive link text, or add hidden text so the link reads "Read more about WCAG 2.1 AA."
Problems 7–8: difficult forms and dynamic announcements
7. Forms that are hard to complete. Placeholder-only labels, required fields marked only by color, vague error messages and CAPTCHAs without accessible alternatives all cause real abandonment. WordPress form accessibility varies widely between form plugins and their settings. Fix: use visible labels tied to each field, identify required fields in text, and write errors that name the field and explain the fix.
8. Silent dynamic updates. AJAX form confirmations, filter results, cart updates and pop-ups often change the page without telling screen reader users anything happened. Fix: announce status messages with an ARIA live region, move focus into modals when they open, and return it when they close.
Problems 9–10: inaccessible media and documents
9. Media without alternatives. Meaningful images uploaded without alt text, videos without captions and auto-playing carousels without pause controls are frequent issues. Fix: fill in alt text in the Media Library as part of publishing, caption every video, and give any motion a visible pause control.
10. Inaccessible PDFs and downloads. Scanned or untagged PDFs, such as menus, brochures and application forms, are often unreadable to assistive technology. Fix: publish key content as HTML pages where possible, and make remaining PDFs tagged, with a logical reading order and real text.
A fix-first WordPress accessibility checklist
Tackle the problems that block tasks before the ones that cause friction:
- Keyboard-test your header, menu and primary forms (problems 2, 3 and 7).
- Add accessible names to every icon button (problem 1).
- Fix brand colors and focus styles globally in the theme (problems 2 and 4).
- Correct heading structure in your page builder templates (problem 5).
- Update blog and card templates for descriptive links (problem 6).
- Add live-region announcements to AJAX forms and modals (problem 8).
- Establish alt text, captions and document standards for your content team (problems 9 and 10).
Template-level fixes give the most return, because one change in the theme or page builder corrects every page that uses it. Automated tools help find candidates, but as W3C notes, tools cannot check every aspect automatically, and human judgment is required. If fixes involve custom code, our WordPress website development work and a semantic website structure go hand in hand.
Frequently Asked Questions
Is WordPress accessible by default?
WordPress core is designed with accessibility in mind, but your site's accessibility depends on the theme, page builder, plugins, custom code and content. Each layer needs to be evaluated.
Can an accessibility plugin fix every problem?
No. Plugins and overlay widgets can help with specific tasks, but they cannot reliably repair inaccessible menus, forms, headings, alt text or documents. Lasting fixes happen in the theme, templates and content.
How do I test a Divi or WordPress form with a keyboard?
Use Tab to move between fields, Shift+Tab to go back, Space to check boxes and Enter to submit. Confirm that every field shows visible focus and has a label, then submit with errors and check that the messages identify each field and are announced to screen readers.
Not sure which of these ten problems affect your site? Review Your WordPress Accessibility with SETN Consultants and get a prioritized, template-level fix list.
