The right accessibility auditor produces a clear, actionable report grounded in WCAG conformance, not a scan output with a logo on top. Look for someone who conducts fully manual evaluations, documents issues with code-level detail, references specific success criteria, and explains remediation in language your developers can act on. Credentials help, but the audit report itself is the truest signal of quality. Ask for a sample before you sign anything.
Pricing transparency, turnaround time, and the auditor’s willingness to answer technical questions during the sales process all matter. A good auditor will not oversell, will not promise certification, and will not blend audits with automated scans.
| Factor | What to Look For |
|---|---|
| Methodology | Fully manual evaluation against WCAG 2.1 AA or 2.2 AA |
| Sample report | Code-level detail, specific criteria, plain-language fixes |
| Credentials | DHS Trusted Tester, CPACC, or documented audit experience |
| Pricing | Transparent per-page or per-screen pricing |
| Scope clarity | Defined pages, templates, user flows, and environments |
| Turnaround | Realistic timeline based on scope, not rushed |
| Red flags | Conformance guarantees, certification promises, scan-only audits |
What does a real accessibility auditor actually do?
An accessibility auditor evaluates a website, web app, or mobile app against the Web Content Accessibility Guidelines, typically WCAG 2.1 AA or WCAG 2.2 AA. The work is manual. The auditor navigates the product with a keyboard, runs it through screen readers like NVDA, JAWS, and VoiceOver, inspects the code, and documents each issue against the specific success criterion it violates.
What you receive is an audit report. It identifies issues, maps them to WCAG criteria, includes the offending code or element, and explains how to remediate. A good report reads like a working document, not a marketing deliverable.
Why fully manual evaluation matters
Automated scans flag approximately 25% of accessibility issues. They cannot evaluate context, meaning, keyboard logic, screen reader output, or whether an interactive component actually works for someone with a disability. They are useful for catching surface-level code issues. They are not an audit.
When you are hiring an accessibility auditor, confirm the evaluation is fully manual. Some providers run a scan, format the output, and call it an audit. That is not what you are paying for, and it will not hold up if conformance ever needs to be defended.
The sample report is the single best signal
Before you hire anyone, ask for a sample audit report. Read it carefully. A strong sample will show each issue mapped to a specific WCAG success criterion, the exact element, selector, or code snippet causing the issue, a clear description of why it fails, a remediation recommendation a developer can act on without further research, and severity or priority indicators.
If the sample is vague, generic, or reads like a scan export, move on. The audit report is the product. If the product is weak, the service is weak.
Credentials worth weighing
Credentials matter less than the report, but they signal training and rigor. The DHS Trusted Tester certification is a strong indicator that the auditor has been trained in a structured evaluation method. CPACC from IAAP demonstrates broad accessibility knowledge. WAS certification leans more technical.
None of these guarantee a good audit. A practitioner with five years of hands-on audit experience and no certification can outperform a freshly certified auditor. Ask how many audits they have conducted and request references when possible.
What about pricing?
Accessibility audit pricing varies widely. Enterprise providers often quote $15,000 to $50,000 or more for a single audit. Independent practitioners and smaller firms can deliver the same quality for a fraction of that, often priced per page or per screen.
What you want is transparency. A reasonable auditor will explain what is included, how scope was determined, and what a page or screen means in their model. If pricing requires three sales calls and a custom proposal for a small website audit, you are likely paying for overhead, not audit quality.
How do you scope the project correctly?
Scope is where audits go wrong. The auditor needs a defined list of pages, templates, user flows, and environments (desktop, mobile, both). For a SaaS product, that means identifying the most important screens and authenticated states. For ecommerce, it means category, product, cart, checkout, and account pages.
A capable auditor will help you scope. They will ask which user flows matter most, which templates repeat across pages, and what your conformance goal is. If they accept your scope without question, that is a warning sign.
Red flags during the sales process
Watch for these during conversations with potential auditors. Guarantees of WCAG conformance or ADA compliance are a concern. So are promises of accessibility certification, since no such formal certification exists. Be wary of providers bundling an audit with an automated scan and calling the combination an audit, refusing to share a sample report, giving vague answers about methodology or screen reader use, or pricing that depends on aggressive upsells for remediation work.
The strongest auditors are direct about what they do and what they do not do. They will tell you an audit identifies issues, that conformance depends on remediation, and that they can validate fixes but cannot promise legal outcomes.
Frequently Asked Questions
How do I know if an auditor is right for my project?
Review their sample report, confirm methodology is fully manual, verify they evaluate against WCAG 2.1 AA or 2.2 AA, and ask how they map your specific platform or framework. If they answer technical questions clearly and price transparently, they are likely a good fit.
Should I hire an individual auditor or a firm?
Both can produce excellent work. Individuals often cost less and communicate directly. Firms can scale across larger products and offer validation, remediation guidance, and VPAT or ACR services. Match the provider to the size and complexity of your product.
How long does an accessibility audit take?
Most audits take two to four weeks depending on scope. A small marketing site might wrap in a week. A large SaaS product with dozens of authenticated screens can take six weeks or more. Anyone promising same-week turnaround on a meaningful scope is cutting corners.
Does an audit make my website compliant?
No. An audit identifies issues. Remediation, where developers fix those issues, is what moves a product toward WCAG conformance. After remediation, the auditor validates the fixes. Only then can a conformance claim be supported.
What’s the difference between an audit and a VPAT?
An audit is the evaluation that identifies accessibility issues. A VPAT is a template used to produce an Accessibility Conformance Report (ACR), which documents how a product conforms to WCAG. The audit informs the ACR. You typically need the audit first.
Hiring an accessibility auditor is mostly about reading the sample report and listening for honesty during the sales process. The auditors who do the work well make that clear quickly.
Looking for an accessibility auditor? Contact the Accessibility Base directory to find practitioners.