ThisCalculator

Everyday

How to Choose an Accessibility Consultant for WordPress

Updated · Standard formula, shown below

Choosing the right accessibility consultant for your WordPress site can mean the difference between a quick audit that sits in a drawer and a lasting improvement in usability for people with disabilities. This guide walks you through the process of vetting, selecting, and working with a consultant who understands both WordPress’s specific technical landscape and the WCAG (Web Content Accessibility Guidelines) standards. Before you start, have a clear idea of your site’s size, your budget range, and whether you want a one-time audit or ongoing support.

What You’ll Need

  • A list of your site’s main page types (home, product, blog, forms, etc.)
  • Your WordPress admin login (for the consultant, if you choose to grant access)
  • Your current theme and plugin names (at least the major ones)
  • A rough budget and timeline for the project
  • Any existing accessibility reports or user feedback

Step-by-Step

  1. Define your goals and scope. Decide whether you need a full WCAG 2.1 AA audit, a targeted review of a specific template, or ongoing remediation support. Write down what “accessible” means for your project—this will guide every conversation.
  2. Search for consultants with WordPress-specific experience. Use search terms like “WordPress accessibility consultant” or “a11y WordPress auditor.” Look for people who have worked with WordPress themes, page builders, and plugins, not just generic web accessibility experts. Check their portfolios for case studies that mention WordPress specifically.
  3. Review their credentials and knowledge. Look for certifications like IAAP (International Association of Accessibility Professionals) CPACC or WAS. But don’t stop there—ask how they stay current with WCAG updates and WordPress core changes. A good consultant will mention testing with screen readers like NVDA, JAWS, or VoiceOver.
  4. Ask about their testing methodology. A reliable consultant should combine automated tools (like WAVE, axe, or Lighthouse) with manual testing and assistive technology testing. Ask how many pages they typically test and how they choose which ones. They should also test keyboard navigation and focus management.
  5. Request a sample audit or a small paid pilot. Before committing to a full engagement, ask if they can review one page (e.g., your homepage or a product page) for a flat fee. This shows you their reporting style, depth of analysis, and how they communicate findings.
  6. Check references and reviews. Ask for contact details of past clients, especially those with WordPress sites. Reach out and ask about the consultant’s responsiveness, clarity of reports, and whether they actually fixed issues or just pointed them out.
  7. Clarify deliverables and reporting format. Will you get a spreadsheet of issues, a detailed PDF, or a live document? Make sure issues are prioritized by severity (critical, serious, minor) and include clear steps to fix, with code examples where relevant. Ask if they will re-test after fixes.
  8. Discuss the remediation process. Will the consultant fix issues themselves, or just advise your developers? If they fix, do they have WordPress development experience? If they advise, will they be available for questions during the fix phase? Make sure you understand the handoff.
  9. Evaluate their communication style. During initial calls, note how they explain technical concepts. They should be able to talk to both non-technical stakeholders and developers. Avoid consultants who are condescending or overly vague.
  10. Get a written proposal and contract. The proposal should include the scope, timeline, cost, deliverables, and any assumptions (e.g., access to staging site). Ensure it states which WCAG version and conformance level you’re targeting (usually 2.1 AA).
  11. Consider long-term support. Accessibility is not a one-time fix. Ask if they offer retainer packages for ongoing audits after theme or plugin updates. This can be more cost-effective than hiring a new consultant later.
  12. Trust your instincts. After all the checks, choose someone who seems genuinely passionate about accessibility, not just checking boxes. The right consultant will ask thoughtful questions about your users and your content workflow.

Common Mistakes

  • Choosing a consultant who only uses automated tools. Automated testing catches maybe 30-40% of issues. Real accessibility requires manual testing with screen readers and keyboard-only navigation.
  • Ignoring WordPress-specific issues. A consultant who doesn’t know WordPress might recommend fixes that break your theme or conflict with plugins. Always ask about WordPress experience.
  • Going for the cheapest option. Accessibility consulting is specialized. Extremely low bids often mean a superficial audit that misses critical issues.
  • Not involving your developers early. If your developers aren’t in the loop, they may resist the consultant’s recommendations. Include them in the selection process or at least in the kickoff meeting.
  • Expecting a quick fix. Accessibility remediation takes time, especially on a large site. Set realistic timelines.

Tips

  • Look for consultants who contribute to WordPress or attend WordCamps. They are likely more familiar with the platform’s accessibility team and best practices.
  • Ask for a sample report before hiring. Many consultants will share a redacted version. This shows you how they prioritize and explain issues.
  • Check if they test with real users with disabilities. Usability testing with people who use assistive technology is incredibly valuable, though it may cost extra.
  • Make sure they understand your page builder. If you use Elementor, Beaver Builder, or Gutenberg, they should know how those tools output HTML and where accessibility pitfalls lie.
  • Have a clear handoff plan. Decide who will fix the issues—your in-house team or the consultant—and set a timeline for re-testing.

Troubleshooting

If the engagement doesn’t go as planned, here’s what to do:

  • If the report is too vague: Ask for clarification. A good consultant should be able to provide specific code snippets or point to the exact element in the DOM.
  • If they don’t respond to questions: Check your contract for response times. If they are unresponsive, escalate to a manager or consider terminating the contract if it’s a breach.
  • If they recommend fixes that break your site: Immediately stop and get a second opinion. A competent consultant should provide tested code or at least clear guidance that your developers can implement safely.
  • If the cost overruns: Review the original scope. If they are doing extra work, ask for a change order. If they are inefficient, discuss the issue directly.
  • If you’re not satisfied with the quality: Many contracts include a revision clause. Ask for a re-test of the areas you’re unhappy with.

Frequently Asked Questions

How much does an accessibility consultant cost?

Costs vary widely: a small site audit might be $1,000–$5,000, while a large e-commerce site could cost $10,000 or more. It depends on the number of pages, complexity, and whether they provide fixes.

Should I choose a consultant who is also a developer?

Not necessarily, but it helps. If the consultant can fix issues themselves, it streamlines the process. However, a good auditor who can clearly communicate with your developers is also fine.

How long does an audit take?

For a typical WordPress site (10-20 page templates), expect 1-3 weeks for the audit and report. Remediation can take longer depending on the number of issues.

Will the consultant need access to my WordPress admin?

It depends. They might need access to inspect themes and plugins, but they can also work from a staging site or even the public site. Always provide a staging site if possible.

What if my site uses a page builder like Elementor?

Make sure the consultant has experience with that specific builder. Page builders often generate complex HTML that can create accessibility issues, so specialized knowledge is key.

What is WCAG 2.1 AA?

It’s the most common accessibility standard for websites. AA level means the site is accessible to most people with disabilities. The consultant should be familiar with its success criteria.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.