Web Accessibility Audit: Key Questions Before Hiring

Web Accessibility Audit: Key Questions Before Hiring

Web Accessibility Audit: Key Questions Before Hiring

Web Accessibility Audit: Key Questions Before Hiring

Quick Answer: What questions should I ask a web accessibility auditing company before hiring?

Ask a web accessibility auditing company which standard the audit targets (WCAG 2.1 AA, WCAG 2.2 AA, or both), how much of the work is manual expert testing versus automated scanning, and whether real assistive technology users are involved. You should also confirm how findings are documented, what happens after delivery, and who actually performs the testing. Get these answers in writing and compare them across at least two vendors.

Auditors differ in scope, methodology, and the legal frameworks they map to. Some test only to a client’s stated standard; others include EN 301 549 or Section 508 mapping for procurement. A few provide remediation support, while others hand over a report and stop there.

Before signing, check the standard and version covered, the manual-to-automated split, assistive technology testing, the report format and severity ratings, retesting terms, accessibility statement support, and the credentials of the people doing the work.

Why the Right Questions Matter More Than the Right Logo

Why the Right Questions Matter More Than the Right Logo

Plenty of agencies sell “accessibility audits.” Far fewer deliver something a developer can actually act on or a legal team can defend. That gap is where budgets quietly die.

The core problem is that accessibility is not a single checklist. It is a moving standard, a legal patchwork, and a deeply human experience all at once. An audit that ignores any of those three legs tends to wobble. And unlike a broken checkout button, accessibility failures often go unnoticed by the very people commissioning the work, because they are not the ones hitting the barriers.

So the interview matters. The questions below are the ones that separate a genuine audit from a glorified automated scan with a PDF wrapper. Ask them early, ask them plainly, and listen for specifics rather than reassuring adjectives.

Questions About Standards and Scope

Which WCAG version does the audit cover?

WCAG 2.2 became a formal W3C Recommendation on 5 October 2023, adding nine success criteria such as Focus Not Obscured, Redundant Entry, and Accessible Authentication. WCAG 2.1 has been a Recommendation since 5 June 2018 and still dominates law and procurement. An auditor should say clearly whether they test to 2.1 AA, 2.2 AA, or both, and why that choice fits your situation.

Watch for vagueness here. “We follow WCAG” is not an answer.

Which conformance level, and on which pages?

Level A, AA, or AAA? Which templates, user journeys, and content types are in scope? A homepage-only audit tells you almost nothing about a checkout flow or an account dashboard. Ask for a written scope list and confirm what is excluded.

Does the report map to the legal framework you actually face?

Standards and laws are not the same thing. In the United States, the Revised Section 508 Standards, effective 18 January 2018, incorporate WCAG 2.0 Level AA by reference for federal agencies’ technology. The ADA itself sets no technical standard for websites, though courts and the DOJ have generally looked to WCAG 2.0 or 2.1 AA. The DOJ’s 2024 rule for state and local government entities adopted WCAG 2.1 AA with compliance dates in 2026 and 2027.

In Europe, EN 301 549 is the harmonised standard for ICT accessibility, updated to reference WCAG 2.1. The European Accessibility Act, Directive (EU) 2019/882, applies from 28 June 2025 to a range of products and services including e-commerce, banking, e-books, and transport. If any of that touches your organisation, ask whether findings are mapped to those specific clauses. If your work involves AI-driven interfaces, the same discipline applies to reviewing a vendor’s AI chatbot security questions before buying, where scoping questions matter just as much.

Questions About Methodology

What is the split between automated and manual testing?

This is the single most revealing question in the whole conversation. Automated tools catch only a minority of WCAG failures. One widely cited vendor analysis of a million pages put automated detection at roughly 57% of issues, and other industry estimates run lower, around 30%. No peer-reviewed consensus exists, so treat any figure as an estimate. The principle holds regardless: automation cannot judge whether alt text is meaningful, whether a focus order makes sense, or whether an error message is understandable.

Push for a rough percentage. An auditor who claims full automation is selling you a scanner.

Do you test with real assistive technology users?

The W3C’s guidance on involving people with disabilities in evaluation exists for a reason: lived experience surfaces barriers that no rule set fully captures. Ask whether the audit includes sessions with screen reader, switch, or voice control users. If not, ask why, and expect a thoughtful answer rather than a shrug.

Does your methodology align with ACT rules?

The W3C’s Accessibility Conformance Testing Rules Format became a Recommendation on 12 December 2019. It gives test rules a common structure, which improves reproducibility. An auditor whose methods align with ACT rules is more likely to produce findings another expert could replicate. That consistency is worth real money when a finding gets disputed.

Who actually does the testing?

Senior specialists or a junior with a checklist? Ask for names, roles, and relevant certifications. Ask how much of the work is outsourced. This is the same due-diligence instinct that applies when reviewing a managed detection and response checklist of questions to ask before committing: the people behind the service matter as much as the service description.

Questions About the Deliverable

What does the report actually look like?

Ask for a sample. A useful report typically includes the success criterion, the affected page or component, a severity rating, a reproduction path, a screenshot or recording, the relevant code snippet, and a remediation recommendation. Vague findings like “improve contrast” waste everyone’s time.

How are severity ratings defined?

Does “critical” mean a total blocker for screen reader users, or merely “we think this matters”? Ask for the rubric in writing.

Can you produce a VPAT or accessibility conformance report?

The VPAT is maintained by the Information Technology Industry Council, with version 2.5 as the current edition. If you sell to government or enterprise buyers, an ACR built on a VPAT is often a procurement requirement. Confirm the auditor can produce one and which edition they use.

Will you help write our accessibility statement?

A public statement is a commitment, and a sloppy one creates risk. Ask whether drafting support is included.

Questions About Process, Retesting, and Cost

What happens after the report lands?

Does the engagement include a walkthrough with your developers? A question-and-answer window? A retest after fixes? Retesting is where audits prove their worth, and it is frequently the line item vendors quietly omit.

How is pricing structured?

Pricing model What it usually means Watch for
Per page or template Fixed scope, predictable cost Unclear treatment of dynamic components
Per hour Flexible but open-ended No cost ceiling in the contract
Flat project fee Simple to budget Scope creep exclusions buried in fine print
Retainer Ongoing support and monitoring Minimum terms and rollover rules

Ask whether retesting is bundled or billed separately, and get the answer in the contract.

What is the timeline, and what do you need from us?

Realistic audits need access, staging environments, and a decision-maker who can answer questions. Ask what happens if your team is slow to respond.

Can you show relevant experience?

Case studies in your sector help, but methodology matters more than logos. A strong auditor in healthcare can learn your industry; a weak one with a familiar brand cannot fake rigor. When weighing any vendor claim, the same skeptical reading applies as in a Rillabox review buyers should weigh before ordering: marketing language rarely survives contact with specifics.

Mistakes People Make When Hiring an Auditor

The most common error is buying an audit as a box-ticking exercise. Teams commission a scan, receive a 300-page automated report, fix the easy contrast issues, and declare victory while keyboard traps remain untouched.

A second mistake is failing to involve developers during scoping. Auditors who never speak to the people writing the code produce findings that get filed away rather than fixed.

A third is ignoring procurement standards until a contract demands them. If your buyers require a VPAT, discovering that after the audit means paying twice. The same trap shows up in consumer purchases, where buyers who skip the fine print on a Fidelity money market funds review of terms savers should check often learn about conditions the hard way.

Finally, many teams treat accessibility as a one-time project. It is a maintenance discipline. Sites change weekly; audits age fast.

What Actually Works in Practice

Practical experience across the industry points to a few patterns that consistently hold up.

First, scope by user journey rather than by page count. A login-to-purchase flow reveals more than fifty static pages.

Second, insist on a findings workshop. Developers who hear a screen reader demonstration firsthand fix issues faster and more permanently than those reading a spreadsheet.

Third, build a remediation backlog with owners and dates before the audit ends. Findings without owners evaporate.

Fourth, retest. A short verification pass three to six months later catches regressions and confirms the fixes actually worked.

Fifth, keep the standard visible in your design system and component library. Fixing a button once beats fixing it four hundred times. Teams that plan for the long haul, much like pilgrims preparing for World Youth Day 2027 in Seoul with a proper planning guide, do better when they prepare deliberately rather than scramble at the last minute.

And keep perspective on cost. A thorough audit is an investment, but it is usually cheaper than retrofitting accessibility after a complaint, a procurement rejection, or a rebuild. Buyers weighing any significant purchase learn the same lesson, whether they are comparing audit vendors or checking an Air Jordan 3 Pure Money buyer’s guide before chasing a pair: the details you skip upfront tend to cost more later.

Conclusion

Hiring a web accessibility auditing company is less about finding the cheapest quote and more about finding a partner who can explain their standard, their method, and their evidence. Ask about WCAG versions, manual versus automated testing, assistive technology users, report quality, retesting, and legal mapping. Then compare answers side by side.

The vendors worth hiring will welcome those questions. The ones who dodge them have just told you something useful too. Whether you are auditing a website, evaluating a pair of Ray-Ban Meta Skyler smart glasses before committing, or comparing Air Jordan 4 Pure Money listings before chasing a deal, the discipline is identical: ask precise questions, demand specifics, and let the answers do the sorting.

FAQ

How long does a typical web accessibility audit take?

Most audits of a mid-sized website run two to six weeks, depending on page count, complexity, and how quickly your team supplies access and answers. Manual testing and assistive technology sessions add time but rarely waste it. Ask for a timeline broken into phases so you can see where delays might appear.

Is an automated scan enough on its own?

No. Automated tools reliably catch some categories of failure, such as missing alternative text or insufficient contrast, but they miss judgment-based issues like confusing focus order or unclear error messages. Industry estimates of automated coverage vary widely, so treat any single percentage with caution. A credible audit combines scanning with expert manual review.

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2, a Recommendation since October 2023, builds on 2.1 by adding nine success criteria covering areas like focus visibility, redundant data entry, and accessible authentication. WCAG 2.1 remains widely referenced in law and procurement. Many organisations now ask for 2.2 AA while confirming 2.1 AA coverage for older contracts.

Should the audit include people with disabilities?

It should, wherever feasible. Testing with assistive technology users surfaces barriers that rule-based testing can miss entirely, and the W3C publishes guidance on involving users in evaluation. If a vendor excludes this, ask how they compensate for the gap and whether they at least test with the same assistive technologies those users rely on.

What is a VPAT, and do I need one?

A VPAT is a template maintained by the Information Technology Industry Council that vendors use to document how a product meets accessibility standards. The resulting document is often called an accessibility conformance report. You need one if you sell to government agencies or large enterprise buyers that request it during procurement.

How often should a website be re-audited?

Most organisations benefit from a full audit annually, with lighter checks after major releases or redesigns. Accessibility degrades quietly as content and components change. Pair periodic audits with automated monitoring and a design system that bakes accessibility in, so regressions get caught between formal reviews.

on this page