Evaluating accessibility consultant proposals comes down to five areas: scope clarity, evaluation methodology, deliverables, pricing transparency, and consultant qualifications. A strong proposal spells out exactly what will be evaluated, how the work will be conducted, what you receive at the end, what it costs, and who is doing the work. If any of those areas are vague or missing, the proposal needs follow-up questions before you sign anything.
Most weak proposals fail in the same places. They quote a flat price without defining scope. They mention automated scans without committing to a manual evaluation. They promise WCAG conformance without explaining how it will be verified. Reading proposals carefully saves money and prevents disappointment later.
| Area | What to Look For |
|---|---|
| Scope | Exact pages, screens, or templates covered. Desktop and mobile environments specified. |
| Methodology | Fully manual evaluation against WCAG 2.1 AA or 2.2 AA. Not scan-only. |
| Deliverables | Audit report with issue location, severity, and remediation guidance. |
| Pricing | Itemized cost per page or screen. No hidden fees for revisions or validation. |
| Qualifications | Who is conducting the audit. Credentials, experience, and sample reports. |
Does the Scope Match What You Asked For?
Scope is where most misalignment starts. A proposal should name the specific pages, screens, or templates being evaluated. If you asked for a 20-page website audit, the proposal should list 20 pages or explain how a representative sample was chosen.
Watch for vague language like “the website” or “key pages.” That phrasing creates flexibility for the consultant and uncertainty for you. Ask for the exact URL list before signing.
For mobile apps and web apps, scope is measured in screens or states, not pages. A proposal that quotes a SaaS audit by “pages” likely misunderstands the asset. That’s a red flag.
Is the Methodology Fully Manual?
Automated scans flag approximately 25% of accessibility issues. A proposal that relies primarily on a scan or tool output cannot determine WCAG conformance. That work is not an audit.
Look for explicit language about manual evaluation conducted by a trained auditor against WCAG 2.1 AA or WCAG 2.2 AA success criteria. The proposal should reference assistive technology evaluation, including screen readers and keyboard-only navigation.
If the methodology section is short or leans on tool names, ask the consultant to describe a single success criterion and how they evaluate it. Their answer will tell you everything.
What’s in the Deliverables?
A complete audit report includes the issue, where it occurs, the WCAG criterion it relates to, a severity rating, and remediation guidance specific enough for a developer to act on. Generic remediation notes mean rework later.
Ask to see a sample report before signing. The format, depth, and clarity of the sample reflect what you will actually receive. If a consultant cannot share a redacted sample, that’s a signal.
Validation is often quoted separately. Confirm whether the proposal includes a re-evaluation after remediation or if that is a follow-up engagement with separate pricing.
Is the Pricing Transparent?
Strong proposals itemize pricing. You should see a per-page or per-screen rate, the total project cost, and any add-ons like user evaluation, VPAT/ACR preparation, or validation broken out separately.
Be cautious of flat enterprise quotes with no breakdown. A $25,000 quote with no line items is harder to negotiate and harder to compare. A proposal showing $300 per page across 30 pages gives you a clear unit cost.
Cost benchmarks vary by asset type. Informational websites are typically cheaper per page than web apps or platforms because the page complexity differs. A consultant quoting the same rate across all asset types likely hasn’t accounted for that.
Who Is Actually Doing the Work?
Ask who will conduct the audit. Some consulting companies sell the project but route the work to contractors with varying experience. That’s not inherently wrong, but you should know.
Credentials worth asking about include DHS Trusted Tester certification, CPACC, or WAS. Years of audit experience matters as much as letters after a name. Sample reports authored by the assigned auditor tell you the most.
If you are buying an ACR or VPAT, confirm the consultant has produced them before. Filling in a VPAT correctly requires understanding both the audit findings and the template structure.
Comparing Proposals Side by Side
When you have two or three proposals in hand, build a quick comparison: scope (pages/screens), methodology (manual vs. scan-assisted), deliverable format, total cost, unit cost, and turnaround time. Differences become obvious.
The cheapest proposal is rarely the best value, and the most expensive isn’t either. The right consultant is the one whose proposal is specific, whose methodology is fully manual, and whose deliverable will actually help your team fix issues.
Frequently Asked Questions
How long should I expect a consultant proposal to take?
Most consultants return a proposal within 2 to 5 business days after a scoping call. Faster turnaround can be a positive sign of operational maturity. Anything past two weeks without communication is worth a follow-up.
What’s a reasonable price range for a website accessibility audit?
Per-page rates for informational websites typically range from $150 to $500, depending on page complexity and the consultant’s positioning. Web apps, platforms, and mobile apps cost more per screen because evaluation depth increases.
Should the proposal mention WCAG 2.1 AA or WCAG 2.2 AA?
It should reference one specifically. WCAG 2.1 AA remains the most common standard, with 2.2 AA increasingly requested for newer projects. The proposal should name the version, not say “latest WCAG.”
Can I negotiate a consultant proposal?
Yes. Scope adjustments, payment terms, and bundled services are all negotiable. Hourly rates and unit costs are typically firmer. Ask the consultant what flexibility exists rather than guessing.
What if a proposal doesn’t include a sample report?
Request one. Reviewing a sample report before signing is reasonable and standard. A consultant who declines or delays without good reason is showing you something about how they operate.
A strong proposal reads like a plan. A weak proposal reads like a brochure. Once you’ve reviewed a few side by side, the difference becomes clear quickly.
Looking for accessibility consultants to request proposals from? Contact Accessibility Base to browse the directory.