Most clients who go through an accessibility project say the same thing afterward: they wish they had known a few key things before they started. The biggest regret is not understanding the scope of what WCAG conformance actually requires. A (manual) accessibility audit identifies issues across your digital asset, but what happens next, including remediation, validation, and ongoing conformance, catches many teams off guard.
Accessibility project preparation for clients comes down to setting realistic expectations around cost, timeline, internal resources, and the difference between a scan and an actual audit. The organizations that move fastest are the ones who walk in with a clear picture of what they own, what needs to be evaluated, and who on their team will coordinate fixes.
| Area | Key Takeaway |
|---|---|
| Scans vs. Audits | Scans only flag approximately 25% of issues. A (manual) audit is the only way to determine WCAG conformance. |
| Remediation Effort | Fixing accessibility issues takes longer than the audit itself. Budget developer time accordingly. |
| Scope Definition | Knowing exactly which pages, screens, or components need evaluation prevents cost surprises. |
| Internal Coordination | A designated point person on the client side keeps the project moving and prevents delays. |
| Ongoing Conformance | Conformance is not a one-time event. New content and updates can introduce new issues. |
Why Scope Definition Changes Everything
The single most common source of confusion at the start of an accessibility project is scope. Clients frequently underestimate how many distinct pages, templates, or application screens their digital asset contains. A marketing website with 30 pages is a different project than a web app with 200 unique views and complex interactive components.
Before requesting an audit quote, take inventory. List every unique page template, every form, every interactive workflow. This is the foundation of accurate pricing and realistic timelines. An auditor evaluates representative pages, so understanding what makes each page type distinct helps define what gets included.
Do Clients Need Developers Ready Before the Audit?
Not before, but immediately after. The audit identifies accessibility issues and delivers them in a report. From there, your development team or an outside remediation partner works through the fixes. The gap between receiving an audit report and starting remediation is where many projects lose momentum.
Having developer resources lined up before the audit is complete is recommended. Even a two-week delay in starting fixes can stretch a project timeline by a month or more once competing priorities take over.
If your organization does not have in-house developers with accessibility experience, factor in the cost of a remediation partner. This is a separate line item from the audit itself, and it often represents the larger portion of total project cost.
Understanding the Difference Between Scans and Audits
Clients who have previously relied on automated scans often assume their digital asset is close to conformance. Then an audit reveals a significantly different picture. Scans only flag approximately 25% of issues. The remaining issues require human evaluation by a qualified auditor who can assess things like keyboard navigation, screen reader compatibility, and content structure.
Scans and audits are completely separate activities. A scan is a quick, automated check. An audit is a thorough, page-by-page evaluation against the WCAG standard, typically WCAG 2.1 AA or WCAG 2.2 AA. They serve different purposes and produce different outcomes.
Budget for More Than the Audit
The audit is one phase. A complete accessibility project typically includes the audit, remediation, validation (a follow-up evaluation confirming fixes were implemented correctly), and potentially an ACR if your product needs procurement documentation.
Clients who budget only for the audit often stall after receiving their report because remediation funds were never allocated. A good rule: plan for the audit to represent roughly one-third of total project cost, with remediation and validation covering the rest.
For organizations pursuing ADA compliance or responding to procurement requirements, the cost of an ACR (completed using the VPAT template) should be factored in as well.
Timeline Expectations That Match Reality
A typical website audit takes one to three weeks depending on scope. Remediation takes longer, often four to twelve weeks depending on the volume of issues identified and developer availability. Validation adds another one to two weeks.
End to end, a complete accessibility project for a mid-size website or web app runs approximately two to four months. For larger digital assets or organizations coordinating across multiple teams, six months or more is common.
Clients who set internal deadlines without factoring in remediation time often create pressure that leads to incomplete fixes or skipped validation.
What Standard Should You Evaluate Against?
Most organizations evaluate against WCAG 2.1 AA. It remains the most widely referenced standard for ADA compliance, Section 508 conformance, and EN 301 549 requirements. WCAG 2.2 AA is gaining traction, particularly for organizations that want to stay ahead of regulatory changes or meet European Accessibility Act (EAA) expectations.
Your auditor can advise on which version fits your situation. For most clients starting their first project, WCAG 2.1 AA is the right choice.
One Person Needs to Own the Project
Accessibility projects that move smoothly have a single internal point person. This person coordinates between the auditor, the development team, and organizational leadership. They do not need to be a technical expert. They need to be responsive, organized, and authorized to make decisions about priorities.
When responsibility is spread across multiple people with no clear owner, communication gaps emerge. Audit reports sit unread. Remediation questions go unanswered. And the project loses freshness.
Can a scan replace an audit for WCAG conformance?
No. Scans only flag approximately 25% of accessibility issues. A (manual) audit conducted by a qualified auditor is the only way to determine WCAG conformance. Scans are useful as a supplementary check, but they cannot evaluate the full range of criteria that conformance requires.
How much does a full accessibility project cost?
Total cost varies based on the size and complexity of your digital asset. A website audit might cost a few thousand dollars, while remediation and validation can double or triple that figure. Larger web apps and software products cost more. Requesting a detailed quote with scope clearly defined upfront prevents surprises.
What if our team has no accessibility experience?
That is common. The audit report provides specific, actionable guidance on what needs to change and where. Developers with general web development skills can address most issues using the report as a reference. For more complex fixes, an outside remediation partner with accessibility expertise can step in.
Preparation is the difference between an accessibility project that wraps up on schedule and one that drags on for months. Know your scope, line up your developers, budget beyond the audit, and assign a project owner. The organizations that do this work upfront consistently report smoother, faster outcomes.
Contact Kris Rivenburgh to discuss your accessibility project.