The Real Audit Scope
The first cost driver is not the number of URLs in a sitemap. It is the number of unique experiences that need review: homepage, navigation, product or service pages, forms, checkout or booking, account access, search, filters, modals, error states, media, and documents.
W3C WCAG-EM frames evaluation as a scoped process: define the target, understand the product, select a representative sample, test the sample, and report findings. That is why a credible audit scope should name the pages, workflows, roles, browsers, and assistive technologies included.
Complete processes matter. A form, checkout, application flow, or purchase path should not be audited as one isolated screen if the user must move through multiple steps to complete the task.
What A Quote Should Separate
Discovery and sampling should be separate from manual testing. Automated tools can save time, but W3C notes that some accessibility checks cannot be automated and require manual intervention.
A useful quote should separate testing, issue documentation, severity rating, code-level guidance, design guidance, developer office hours, retesting, accessibility statement support, and optional monitoring.
If the audit is for procurement, a VPAT or ACR, a lawsuit response, or an enterprise buyer, evidence quality matters more. That usually means clearer scope notes, reproducible findings, screenshots or code references, and a retest plan.
How To Compare Audit Vendors
Ask vendors whether they test keyboard navigation, focus order, form errors, screen reader behavior, dynamic states, mobile breakpoints, and representative user tasks. A crawler-only report is not the same as a manual audit.
Ask whether findings are grouped by reusable component and template. A report that lists every repeated product-card issue as separate noise can feel large while still failing to help developers fix the root cause.
Ask what happens after delivery. The best audit path includes prioritization, remediation support, retesting, and an operating plan so new content, campaigns, apps, and releases do not recreate the same issues.
Where Partner Providers May Fit
Some teams need a one-time expert audit. Others need a hybrid path with software, monitoring, developer support, manual services, file accessibility, or procurement evidence.
When appropriate and with your consent, we may refer you to accessiBe. Use the quote drivers first, then compare which parts of the work should be handled by software, expert services, internal developers, or an ongoing accessibility program.
Decision path
Use these links to move from research to evidence, then from evidence to a responsible remediation option.
Frequently asked questions
Is an automated scan the same as an accessibility audit?
No. Automated tools help find common issues quickly, but many checks need human judgment, keyboard testing, assistive-technology review, and task-based evaluation.
What should I prepare before asking for audit pricing?
Prepare your platform, critical user paths, representative templates, known documents, traffic or revenue-critical pages, urgency, and whether you need remediation guidance or retesting.
Should an audit include every page?
Usually it should include a representative sample plus complete user processes. Testing every URL is less useful than testing unique templates, components, documents, and critical workflows.