The 11 Accessibility Pitfalls That Are Costing WordPress Agencies Clients (And How to Avoid Them)

If you run a WordPress agency, you’ve probably noticed the shift. Clients aren’t just asking about accessibility anymore—they’re requiring it. Government contracts demand WCAG 2.1 AA compliance. Nonprofits need to meet grant requirements. Mid-market companies are facing legal pressure they can’t ignore.

But here’s the challenge: most agencies learned WordPress development years before accessibility was on anyone’s radar. The result? Well-intentioned teams are unknowingly building inaccessible sites, and it’s becoming a serious business liability.

After 20 years building WordPress sites and the last decade focused specifically on accessibility, I’ve seen the same mistakes repeated across hundreds of projects. The good news? Most of these pitfalls are completely avoidable once you know what to look for.

Let’s break down the eleven most common accessibility mistakes WordPress agencies make—and more importantly, how to fix them.

Design Choices That Create Accessibility Barriers

1. Color Contrast That Looks Great But Fails Users

Your designer delivers a beautiful mockup with subtle gray text on a white background. It looks modern and clean. It also fails WCAG contrast requirements and makes content unreadable for users with low vision.

The fix: Use a contrast checker before finalizing any design. Text needs a 4.5:1 contrast ratio (3:1 for large text). This doesn’t mean sacrificing aesthetics—it means being intentional about color choices from the start.

2. Hover-Only Interactions That Lock Out Keyboard Users

Dropdown menus that only work on hover. Tooltips that appear on mouseover but never on focus. These design patterns are everywhere in WordPress themes, and they create a wall for anyone navigating by keyboard.

The fix: Every hover interaction needs a keyboard equivalent. If something happens on mouseover, it should also happen on focus. Test your navigation and interactive elements using only your Tab key—if you can’t access something, neither can your users.

3. Custom Icon Buttons Without Text Labels

Those sleek icon-only buttons (search icons, hamburger menus, social media links) often have no text alternative for screen readers. What’s visually obvious to sighted users is completely invisible to assistive technology.

The fix: Add visually hidden text labels using CSS, or use proper ARIA labels. Every interactive element needs a text alternative that describes its purpose, even if that text isn’t visible on screen.

Theme Selection and Customization Mistakes

4. Choosing Themes That Look Good But Test Poorly

The most popular WordPress themes in the repository can have significant accessibility issues. High sales numbers and five-star reviews don’t indicate accessible code—most reviewers simply aren’t testing for it.

The fix: Before purchasing or recommending a theme, test it thoroughly. Check the theme documentation for accessibility statements. Look for themes that explicitly mention WCAG compliance and provide accessibility documentation. Better yet, start with themes from developers known for accessibility, like GeneratePress or Kadence with proper configuration.

5. Overriding Theme Accessibility Features During Customization

Many modern themes ship with decent accessibility features—skip links, keyboard navigation support, proper heading hierarchy. Then agencies customize them and accidentally break everything.

The fix: When customizing themes, preserve the accessibility features. Don’t remove skip links. Maintain proper heading order. Keep focus indicators visible. If you’re using custom CSS to hide focus outlines, you’re creating barriers for keyboard users.

Plugin Selection Traps

6. Installing Accessibility Overlay Plugins (The Worst Mistake)

This one deserves bold text: Accessibility overlay plugins like AccessiBe, UserWay, and AudioEye do not make websites accessible and actually increase legal risk. These tools claim one-click compliance but deliver false security while creating new accessibility barriers.

The fix: Avoid overlay plugins entirely. There is no shortcut to accessibility. Real compliance requires proper HTML, thoughtful design, and manual testing. If a client asks about overlays, educate them on why these create legal liability rather than protection.

7. Choosing Page Builders That Generate Inaccessible Code

Popular page builders like Elementor and Divi give clients visual editing power, but they often generate bloated, inaccessible HTML. Improper heading hierarchies, missing ARIA labels, and keyboard navigation issues are common.

The fix: If you must use page builders, choose ones with better accessibility track records (Gutenberg with proper block patterns is generally better than third-party builders). Test everything after building. Configure the builder’s accessibility settings properly. Better still, consider whether your client actually needs a page builder—sometimes clean, accessible code is the better solution.

8. Form Plugins Without Proper Labels and Error Handling

Contact forms are often the most important conversion point on a site. They’re also frequently the most inaccessible element. Missing labels, unclear error messages, and reliance on visual-only indicators create massive barriers.

The fix: Choose form plugins that properly associate labels with inputs, provide clear error messaging, and announce validation feedback to screen readers. WPForms and Gravity Forms can be configured accessibly, but require attention to settings. Always test form submission with a screen reader.

Content and Media Management Issues

9. Images Without Meaningful Alt Text

This is the most well-known accessibility requirement, yet it’s constantly done wrong. Alt text that says “image123.jpg” or decorative images with lengthy, unnecessary descriptions both fail users.

The fix: Train your content team on writing meaningful alt text. Decorative images should have empty alt attributes (alt=””). Informative images need descriptions that convey the same information as the image. Complex images like charts might need longer descriptions elsewhere on the page.

10. Videos Without Captions and Transcripts

Video content without captions excludes deaf and hard-of-hearing users. Auto-generated YouTube captions are a start, but they’re often inaccurate and unprofessional.

The fix: Budget for professional captioning services or at minimum, carefully review and edit auto-generated captions. Provide transcripts for video content. Make sure video players have accessible controls that work with keyboards and screen readers.

The Testing Gap Nobody Talks About

11. Relying Solely on Automated Testing Tools

Here’s the uncomfortable truth: automated testing tools catch maybe 30-40% of accessibility issues. Chrome Lighthouse, WAVE, and other scanning tools are valuable, but they can’t test keyboard navigation, screen reader experience, or logical reading order.

The fix: Implement manual testing as part of your QA process. At minimum: test keyboard navigation through the entire site, verify heading structure makes sense, check color contrast, and test your most critical user flows with a screen reader. If you can’t do comprehensive manual testing in-house, partner with accessibility professionals who can.

Building Accessibility Into Your Agency Process

Fixing accessibility problems after launch is expensive and time-consuming. The agencies winning accessibility work are building it into their process from the start:

• Discovery: Ask about accessibility requirements and compliance mandates upfront
• Design: Use contrast checkers and test with keyboard navigation during design review
• Development: Choose accessible themes and plugins, follow semantic HTML practices
• Content: Train clients on alt text and accessible content creation
• QA: Add manual accessibility testing to your checklist, not just automated scans
• Launch: Provide clients with documentation on maintaining accessibility post-launch

The Bottom Line for Agencies

Accessibility isn’t a one-time checklist—it’s a fundamental shift in how you build websites. But here’s what makes it worth the investment: accessible sites are better sites. They’re more usable for everyone, they perform better in search, and they protect your clients from legal risk.

The 2026 federal accessibility mandates are coming. Government agencies, nonprofits, and regulated industries are all facing compliance deadlines. The agencies who master accessibility now will win those contracts. The ones who keep building inaccessible sites will lose clients and face growing liability.

The choice is pretty clear.

Ready to build more accessible WordPress sites? Start with the fundamentals: proper semantic HTML, keyboard navigation, color contrast, and meaningful alt text. Use automated testing tools to catch obvious issues, but don’t stop there—invest in manual testing. And most importantly, educate your entire team that accessibility isn’t an add-on feature; it’s a core requirement for professional web development.

The WordPress accessibility community is here to help. Connect with other agencies working on this challenge, share what you’re learning, and don’t be afraid to ask questions. We’re all working to make the web better together.