How Much Does a WCAG Audit Cost?

The Detailed Answer

WCAG audit pricing varies widely because "an accessibility audit" can mean very different things depending on what is included. At the low end, an automated scan using tools like axe-core or Siteimprove produces a machine-generated report of detectable violations with no human evaluation. At the high end, a full manual audit combines automated scanning with expert human review of every unique page template, screen reader testing across multiple browser and assistive technology combinations, keyboard testing of all interactive components, a prioritized remediation plan with code-level fix recommendations, and follow-up verification testing after remediation.

The number of unique page templates is the primary cost driver, not the total number of pages. A 500-page blog with one content template, one homepage template, and one category page template has three unique templates to audit. A 50-page web application with login flows, dashboards, settings panels, forms, reports, and modal dialogs might have 30 unique templates. The web application costs significantly more to audit despite having fewer pages because each unique template requires separate evaluation of its layout, interactive elements, color scheme, ARIA implementation, and keyboard behavior.

Auditor credentials and reputation also affect pricing. Independent consultants with IAAP (International Association of Accessibility Professionals) certifications like CPAC or WAS typically charge $150 to $300 per hour. Established accessibility consultancies like Level Access, Deque, and TPGi charge enterprise rates that reflect their brand, team depth, and ability to provide legally defensible audit reports. Smaller specialized firms and solo practitioners offer the same technical expertise at lower rates, sometimes 40-60% less than the large consultancies.

Pricing Breakdown by Audit Type

Automated-only audits run scanning tools against your site and produce a report of machine-detected violations. These cost $500 to $2,000 depending on the number of pages scanned and the reporting depth. Automated audits are useful as a starting point to understand your current violation count and most common issues, but they only catch 30-40% of WCAG violations and should not be treated as evidence of compliance. Some providers offer automated scanning as a subscription service, typically $100 to $500 per month, with continuous monitoring and alerts when new issues appear.

Manual audits with automated scanning combine tool-based detection with expert human evaluation. A small site with 10 to 20 unique templates typically costs $5,000 to $15,000. The auditor tests each template against all applicable WCAG success criteria, documents every finding, and provides remediation guidance. This is the audit type that most organizations need, and it produces a report that demonstrates due diligence for legal purposes.

Full compliance programs include the initial audit, detailed remediation support (code reviews, developer training, office hours with accessibility experts), follow-up testing to verify fixes, VPAT creation for government procurement, accessibility statement drafting, and ongoing monitoring. These programs cost $20,000 to $100,000 or more annually, depending on the organization's size and the complexity of its digital properties. Enterprise organizations with multiple websites, mobile apps, and internal tools typically need this level of engagement.

Accessibility consulting on an hourly basis is an alternative to fixed-scope audits. Expert consultants charge $150 to $300 per hour, and you engage them as needed for specific questions, code reviews, or focused evaluations of particular components. This model works well for organizations with in-house accessibility knowledge that need occasional expert input rather than a full audit. A 20-hour consulting engagement at $200 per hour ($4,000 total) can address specific concerns, train developers on common patterns, and review the accessibility of critical workflows.

Factors That Increase Audit Cost

Single-page applications (SPAs) and complex web applications cost more to audit than content-driven websites because they have more interactive states, dynamic content, and custom widgets that require individual evaluation. A SPA with a complex dashboard, dozens of modal dialogs, drag-and-drop interfaces, real-time data updates, and custom chart components requires significantly more testing time than a marketing site with static pages.

Authentication and multi-role access add cost because the auditor must test different user experiences. An application with separate customer, administrator, and support agent interfaces effectively multiplies the audit scope by the number of distinct roles. Each role may see different pages, different navigation, and different functionality, all of which need independent accessibility evaluation.

Third-party integrations like payment processors, chat widgets, embedded maps, social media feeds, and analytics dashboards add complexity because their accessibility varies and may not be under your control. The auditor needs to evaluate these components and determine which accessibility issues are within your control to fix and which require engagement with the third-party vendor.

Tight timelines increase cost because the auditor must dedicate concentrated resources to meet the deadline, potentially displacing other client work. A standard audit with a four-to-six week timeline costs less than the same audit needed within two weeks. Rush fees of 25-50% are common in the accessibility consulting industry.

VPAT (Voluntary Product Accessibility Template) creation adds $2,000 to $5,000 to the audit cost. VPATs document the accessibility conformance of a product against WCAG and Section 508 criteria, and they are required for selling software or services to U.S. government agencies. Creating a VPAT requires evaluating every relevant WCAG criterion and documenting the conformance status of each, which is essentially a comprehensive audit with a specific documentation format.

How to Reduce Audit Costs

Fix automated violations before the manual audit. Run axe-core against your site, resolve every machine-detectable issue, and re-scan to confirm zero automated violations. This reduces the manual auditor's work because they spend less time documenting issues you could have found yourself. Some auditors will quote a lower price if you can demonstrate that automated scanning has already been addressed.

Reduce the number of unique templates to audit by standardizing your design system. If every form uses the same form component, every modal uses the same modal component, and every page uses one of three layout templates, the auditor evaluates each component once rather than re-evaluating similar-but-slightly-different implementations across dozens of pages.

Build in-house accessibility expertise. Train one or two team members in WCAG evaluation methodology, screen reader testing, and keyboard testing. Use their skills for routine evaluations and reserve external audits for annual formal assessments or complex edge cases that require specialist judgment. The cost of training (IAAP certification costs approximately $500 for the exam, plus study materials and time) pays back quickly by reducing reliance on external consultants for everyday accessibility questions.

Scope the audit to your actual risk profile. If your site is a content-heavy blog with minimal interactive elements, a focused audit on page structure, images, links, and color contrast covers your primary risk areas without paying for comprehensive form and widget testing you do not need. If your site is an e-commerce platform, prioritize the checkout and account management flows where accessibility failures directly cause revenue loss and legal exposure, and audit secondary content pages at a lower frequency.

What to Look for in an Audit Provider

The quality of accessibility audit providers varies significantly. Look for auditors with credentials from the International Association of Accessibility Professionals (IAAP), specifically the Certified Professional in Accessibility Core Competencies (CPAC) or the Web Accessibility Specialist (WAS) certification. These certifications require passing a rigorous exam that tests WCAG knowledge, assistive technology proficiency, and practical evaluation skills.

Ask about the testing methodology before signing a contract. A thorough audit should include automated scanning (using axe-core or equivalent), keyboard-only navigation testing, screen reader testing with at least two screen reader and browser combinations, manual evaluation of every applicable WCAG success criterion against each unique page template, and a review of dynamic content and interactive components. Audits that rely solely on automated scanning are not comprehensive and should not be marketed as WCAG conformance audits.

Review sample audit reports from prospective providers. A useful audit report identifies each issue with the specific page URL, the failing element, the WCAG success criterion violated, the impact severity, and a concrete remediation recommendation with code examples where applicable. Reports that list violations without actionable fix guidance leave your development team guessing about how to resolve each issue, effectively doubling the cost because you need additional consulting to interpret the findings.

Ask about remediation support. Some audit providers deliver a report and consider the engagement complete. Others include a period of remediation support where the auditing team reviews your fixes, answers technical questions, and performs re-testing to verify that issues are resolved. The second model costs more upfront but typically results in faster, more accurate remediation because developers can ask questions as they work rather than interpreting the report independently.

Check references and look for experience with your technology stack. An auditor who has evaluated hundreds of React single-page applications will identify issues faster and provide more relevant remediation guidance for a React project than an auditor whose experience is primarily with static HTML sites. Similarly, auditors with experience in your industry (e-commerce, healthcare, financial services, education) understand the specific user flows and compliance requirements that apply to your context.