10 Accessibility Questions Every Client Asks Before an Audit

When clients reach out for accessibility audits, the same set of questions comes up again and again, around cost, scope, timelines, and compliance.

Here are the top 10 questions we get at DigitalA11Y, along with practical answers based on real-world experience. And if your question isn’t covered here, we’ve answered 80+ frequently asked questions (FAQs), organized by category on our dedicated FAQs page.

1. Why does a web accessibility audit cost more than expected?

Most clients initially assume accessibility is just running automated tools. In reality, a large part of the audit involves manual testing—keyboard navigation, screen reader testing, and validating issues against WCAG guidelines.
This requires time, expertise, and attention to detail, which is why accessibility audits may cost more than expected.

2. How much does a WCAG audit cost?

A typical WCAG audit can cost around $1,250 to $2,500 USD for a 10-page audit.
The actual cost depends on factors like the number of templates, components, platform type (website, web app, mobile app), and overall complexity. Most accessibility vendors estimate pricing based on scope.

3. What is the difference between manual and automated accessibility testing?

Automated testing uses tools like axe-core or WAVE to identify programmatic issues at scale.
Manual testing involves evaluating the application using keyboard navigation, screen readers, and other assistive technologies.
Both are essential—automated tools cannot catch all accessibility issues.

4. What is the process of conducting a WCAG audit?

A WCAG audit starts with defining the scope—key user journeys, templates, and platforms.
This is followed by automated testing and detailed manual testing. Issues are then documented with WCAG mappings, recommendations, and remediation guidance

5. What should be included in an accessibility audit scope?

Every audit is different. We typically identify key user journeys like login, signup, and checkout, along with unique templates, components, and high-traffic pages.
Since it is not practical to test every page manually, we focus on representative coverage.

6. Are all pages tested in an accessibility audit?

No. Instead of testing every page, we focus on key templates and critical user journeys.
Since many pages reuse the same components, fixing issues at the template level improves accessibility across the platform. Automated tools can still scan all pages.

7. How long does a typical accessibility audit take?

For a 10-page audit, it typically takes around 5–7 working days, depending on complexity.
Timelines may vary based on scope and vendor availability, so it’s always good to confirm upfront.

8. What deliverables are included in an accessibility audit report?

A good audit report includes an executive summary, issue descriptions, recommendations, screenshots, and code snippets.
Each issue is mapped to WCAG success criteria and assigned a unique identifier for tracking.

9. Can a VPAT be created before fixing accessibility issues?

Yes, a VPAT can be created after the audit is completed, even before fixes are implemented.
However, it may not reflect the most accurate state of compliance, especially during procurement processes. Updating it after major fixes is recommended.

10. How do teams maintain WCAG compliance after an audit?

Accessibility should be treated as an ongoing process.
Teams should integrate accessibility into design, development, and QA workflows, use automated monitoring, and validate new features before release. This helps prevent issues from reaching production.

Final Thoughts

Accessibility is not a one-time effort—it’s a continuous process.

Understanding the scope, cost, and methodology of a WCAG audit helps organizations make better decisions and build more inclusive digital products.

Related Reads

• Accessibility Questions
  Frequently asked accessibility questions answered.
• WCAG 2.2 AA Checklist
  A comprehensive WCAG 2.2 AA Checklist meant to be used as a guide for your accessibility initiatives.
• Shift Left Accessibility
  Shift Left Accessibility means that you think about accessibility from the start. Considering accessibility at every stage like user stories, design, development, QA testing, communication and more.