Setting expectations with an accessibility consultant starts with a written scope, a defined standard, a deliverables list, and an agreed timeline. Both sides need clarity on what is being evaluated, which WCAG version applies, what the final report looks like, and how follow-up work is priced. A short kickoff conversation answers most of these questions. A written statement of work confirms them. When expectations are documented before the audit begins, the project runs cleanly and the report lands with no surprises.
| Expectation Area | What to Confirm |
|---|---|
| Scope | Exact pages, screens, or user flows included. Desktop, mobile, or both. |
| Standard | WCAG 2.1 AA or WCAG 2.2 AA. Add Section 508 or EN 301 549 if procurement requires it. |
| Method | Fully manual evaluation by a qualified auditor, not a scan-based report. |
| Deliverables | Audit report with issues, severity, locations, and remediation guidance. |
| Timeline | Start date, draft delivery date, and final report date. |
| Pricing | Fixed fee or per-page pricing. Validation and re-audit costs disclosed upfront. |
| Communication | Single point of contact, response windows, and meeting cadence. |
Start With a Clearly Defined Scope
Scope is where most consultant relationships go sideways. If you bring a 200-page site to the conversation but expect a 12-page audit price, the project will stall before it begins.
Identify the exact URLs, templates, or app screens you want evaluated. Distinguish between unique templates and repeated instances. A product detail page is one template even if the catalog has 5,000 items.
Confirm whether desktop, mobile web, or native mobile environments are included. Each environment is a separate evaluation effort.
Agree on the Standard and Version
The default for most projects is WCAG 2.1 AA. Some buyers, especially in procurement-driven sectors, ask for WCAG 2.2 AA. Government and federal work often requires Section 508 or EN 301 549 alignment.
Lock the standard in writing before the audit starts. A consultant cannot retroactively map issues to a different version without redoing work.
What Should the Deliverable Look Like?
Ask to see a sample audit report before signing. The format tells you everything about how the consultant works.
A strong report includes the issue, the WCAG criterion it maps to, the page or screen location, a severity rating, and a clear recommendation for remediation. Screenshots or code snippets help your developers act faster.
Reports that only export a scan dashboard are not audits. Scans flag approximately 25% of issues and cannot determine conformance.
Clarify Method: Evaluation, Not Scans
A qualified consultant evaluates the asset using assistive technology, keyboard navigation, and code inspection. The work is performed by a person. Automated checks may support the process but never replace it.
Ask directly: is the audit fully manual, or does it rely on scan output? The answer separates real consultants from resellers.
Set Timeline and Communication Norms
A standard audit on a mid-size website takes one to three weeks depending on scope. Mobile apps and complex web apps take longer. Get a draft delivery date and a final report date in writing.
Decide who the point of contact is on both sides. Agree on response time for questions during the audit. A 24 to 48 hour window is reasonable.
Confirm What Happens After the Report
The audit is the start, not the end. Ask the consultant what their remediation support looks like.
Some consultants advise your developers. Some pair with a development team. Some only deliver the report and step back. Any approach can work, but you need to know which one applies before the report lands.
Confirm validation pricing now. A validation pass after fixes confirms whether issues were resolved correctly. If validation is priced as a surprise add-on, the project budget is incomplete.
Pricing Should Be Transparent
A consultant who cannot give you a clear quote based on scope is a risk. Pricing is usually per page, per screen, or fixed for a defined asset.
Ask what triggers additional cost. New pages added mid-audit, scope expansion, and rush turnaround are common surcharge areas. None of these should appear as a surprise on the invoice.
Frequently Asked Questions
How do I know if a consultant is qualified?
Ask about credentials such as CPACC, WAS, or DHS Trusted Tester. Ask how long they have been auditing and how many audits they have completed. Request a sample report. A qualified consultant answers all three without hesitation.
Should I expect a fixed price or hourly billing?
Most accessibility audits are priced as fixed fees based on scope. Hourly billing is more common for consulting, remediation guidance, and training engagements. Confirm the model in writing.
What if the scope changes mid-project?
Scope changes are normal. A good consultant will pause, document the new scope, and provide a revised estimate before continuing. Avoid consultants who absorb scope changes silently and then surprise you later.
Do consultants guarantee WCAG conformance?
No reputable consultant guarantees conformance on assets they did not build. They evaluate the current state and identify what needs to change. Conformance is achieved through remediation, validation, and ongoing maintenance.
How often should I re-engage a consultant?
Most teams re-engage annually or after significant product changes. High-frequency release teams may benefit from a quarterly check or ongoing monitoring arrangement.
The Right Conversation Before the Contract
A 30 minute scoping call answers most of the questions above. If a consultant cannot give direct answers to scope, standard, method, deliverables, timeline, and pricing in that call, that is the signal to keep looking.
Browse vetted accessibility consultants in the Accessibility Base directory.