What Digital Accessibility Actually Costs (And How Long It Really Takes)

If you’re planning a digital accessibility project, you’ve probably done some searching. Maybe you’ve looked at automated tools that promise compliance for $49 a month. Maybe you’ve gotten a quote from a remediation firm and felt sticker shock. Maybe you’re trying to build a budget and can’t find actual numbers anywhere.

That’s not an accident. The accessibility industry is notoriously opaque about pricing. Most service providers hide behind “Request a Quote” forms. Vendor pages promise the moon but never mention cost. And almost nobody talks about timelines.

After working with organizations across healthcare, education, government, parks & recreation, and nonprofits, we see the same two misconceptions again and again. Organizations underestimate what digital accessibility actually costs to do correctly, including legally defensible documentation. And they underestimate how long the initial remediation takes.

Both of those miscalculations lead to the same outcome: organizations either don’t start, or they start with the wrong partner and run out of budget before the work is done.

This article gives you real numbers and real timelines so you can plan correctly.

The True Cost of Digital Accessibility

Let’s start with what accessibility actually costs. Not the marketing promises, not the “request a quote” vagueness. Actual ranges based on organization size, scope, and what the work needs to include.

Accessibility Audits

An accessibility audit is the assessment phase. Accessibility assessments should identify the governing standard for the organization. Many organizations now test against WCAG 2.2 Level AA as the current W3C standard, while specific regulations or contracts may reference an earlier version. For example, the DOJ’s ADA Title II web accessibility rule for state and local governments incorporates WCAG 2.1 Level AA. This is not the same as running an automated scanner. A real audit combines automated testing, manual review by certified experts across every page template and user flow, and testing with assistive technologies like NVDA, JAWS, and VoiceOver.

Understanding Pages, Templates, Components, and User Flows

One of the biggest mistakes organizations make when estimating accessibility work is counting URLs instead of evaluating the actual complexity of the digital experience.

A website with 5,000 URLs may rely on only 20 to 30 unique page templates. On the other hand, an application with only 50 URLs may contain hundreds of interactive states, custom components, forms, dialogs, dashboards, and user workflows that each require separate accessibility testing.

For accessibility purposes, scope should be based on a combination of:

• Unique page templates
• Reusable components
• Interactive states
• Forms and form validation
• Critical user flows
• Third-party integrations
• Documents and PDFs
• Video and audio content
• Mobile application screens
• Authentication and account functionality

A user flow is an end-to-end task a person needs to successfully complete. Examples include creating an account, logging in, resetting a password, searching for information, filtering results, completing an application, uploading a document, scheduling an appointment, checking out, submitting payment, or updating account information.

This distinction matters because accessibility testing is not simply a page-counting exercise. A complex checkout flow with five screens may require substantially more testing than 50 static informational pages.

Here’s what audits actually cost:

• Small organizations (under 25 web pages and templates, 1-20 documents): $2,500 to $10,000
• Mid-size organizations (30 to 100 web pages and templates, 20-50 documents, and core user flows): $10,000 to $50,000
• Large organizations (multi-domain, 100+ pages and templates, 50+ documents, and native apps): $50,000 to $200,000+

On a per-page basis, expect to pay $100 to $350 per complex page or screen, and $25 to $100 per simpler template-repeat page. The audit should produce a detailed report mapping every barrier to the specific WCAG success criterion it violates, with screenshots, code references, and prioritized remediation recommendations. This report is the roadmap for the remediation phase, and it’s also your first piece of legal documentation.

Remediation

Remediation is the actual fix work. This is where barriers are corrected in your source code, content, and design. Costs depend on the number of barriers, the complexity of your site architecture, and whether you’re doing the work internally or outsourcing it.

Per-page remediation rates:

• Simple static content pages (alt text, basic ARIA, contrast adjustments): $150 to $300 per page
• Interactive pages (forms, modals, advanced ARIA, tables, custom controls): $300 to $800 per page
• Complex application views (dashboards, checkout flows, portals): $800 to $2,500+ per view

Total site remediation investment:

• Small sites (10 to 25 pages): $3,000 to $10,000
• Mid-size sites (50 to 150 pages, templates, and flows): $15,000 to $50,000
• Large/complex sites (enterprise apps, e-commerce, portals): $50,000 to $200,000+

If you’re budgeting for internal developer time, expect accessibility work to take 3 to 6 hours per complex template screen. At typical engineering rates of $100 to $250 per hour, that’s $300 to $1,500 per screen in labor alone.

The Piece Most Organizations Forget: Legally Defensible Documentation

Here’s where most budgets fall short. An audit and remediation project that doesn’t produce defensible documentation is like doing the work but not being able to prove it.

If you’re ever sued, audited by a federal agency, or asked to demonstrate compliance in an RFP, you need documentation that holds up. This includes:

• A WCAG conformance report mapping every success criterion (1.1.1 through 4.1.2) to your site’s compliance status, using standard conformance terms: Supports, Partially Supports, Does Not Support, Not Applicable. The report must include testing methodology, the exact assistive technology combinations tested (the operating system, browser, screen reader or assistive technology, and version used for each test configuration.), and auditor qualifications (IAAP CPACC, WAS, or equivalent certifications).
• A VPAT (Voluntary Product Accessibility Template) if you sell software or services to government or enterprise buyers. Self-authored VPATs based on an existing audit cost $350 to $950. Full third-party audit plus VPAT packages run $5,000 to $10,000 for standard products, and $15,000 to $50,000+ for complex enterprise software.
• Remediation evidence logs showing who was the tester, who was the developer, who was the validator, what was found, what was fixed, when it was fixed, and how it was verified.
• Assistive technology testing records documenting which tools were used, which pages were tested, and what the user experience was.

This documentation can add approximately 15 to 25% to the overall project effort, but it serves an important purpose. It creates a record of what was evaluated, what barriers were identified, how they were prioritized, what was remediated, and how the organization verified the results.

An automated scanning report alone should not be treated as proof of WCAG conformance. Automated tools are extremely useful for identifying certain categories of accessibility defects, but many WCAG requirements require human judgment, keyboard interaction, visual review, content evaluation, or assistive technology testing.

The strongest accessibility programs therefore combine automated testing with manual expert review and documented validation.

Documents, Video, and Audio (The Hidden Scope)

Most organizations budget for website pages and forget everything else. This is where projects blow through their budgets.

PDF and document remediation

• Standard text PDFs: $4 to $9 per page
• Medium complexity (multi-column, graphics, tables): $9 to $20 per page
• Complex fillable forms: $25 to $60+ per page

A university or government agency with 10,000 PDFs averaging 5 pages each faces a document remediation bill of $250,000 to $500,000+. This is not a rounding error in your budget.

Video Captioning & Transcripts

• Professional human closed captioning (99%+ accuracy): $1.25 to $3.00 per minute
• Live real-time captioning (CART): $100 to $150 per hour

Audio Description (required under WCAG 2.1 AA for synchronized video):

Professional human audio description: $15 to $35 per minute
Complex or technical content: $35 to $60+ per minute

Ongoing Monitoring and Maintenance

Accessibility is not a one-time project. Every time you publish new content, update a page, or add a new feature, you introduce the risk of new barriers. Budget 15 to 30% of your initial remediation cost annually for ongoing maintenance.

• Automated monitoring tools (Siteimprove, axe Monitor, Pope Tech)
  • $1,200 to $3,600 per year for small sites
  • $5,000 to $15,000 for mid-size
  • $20,000 to $60,000+ for enterprise
• Continuous compliance retainers (quarterly re-audits, expert support, regression testing)
  • $3,000 to $6,000 per year for small organizations
  • $10,000 to $25,000 for mid-size
  • $30,000 to $100,000+ for enterprise
• Staff training
  • $500 to $2,000 per developer
  • $200 to $600 per content creator
  • Budget for annual refreshers and onboarding new staff

Organizations that invest in ongoing maintenance spend significantly less over three years than those that do a one-time remediation and let the site drift back into non-compliance. It’s the difference between routine maintenance and emergency repairs.

Total First-Year Investment

Putting it all together, here’s what a realistic first-year budget looks like:

• Small organizations: $6,700 to $16,000 (audit + remediation + documentation + first year of monitoring)
• Mid-size organizations: $30,000 to $80,000
• Large organizations: $180,000 to $530,000+

For context, organizations typically spend 3 to 10% of annual revenue on compliance activities across all regulatory domains (HIPAA, data privacy, billing, quality reporting). Allocating 5 to 10% of your existing compliance budget to digital accessibility is a reasonable starting point.

The Tax Credit Most Organizations Miss

If you’re a small business, the IRS Section 44 Disabled Access Credit can offset a significant portion of your accessibility investment. The credit covers 50% of eligible expenditures between $250 and $10,250, up to a maximum credit of $5,000 per year. Eligible expenses include accessibility audits, remediation services, and staff training.

That means a small organization spending $15,000 on accessibility could recover $5,000 through the tax credit, reducing the net cost to $10,000.

How Long Accessibility Remediation Actually Takes

Cost is only half the equation. The other half is time.This is where organizations are often caught off guard because accessibility project timelines are not determined simply by the number of pages on a website.

The biggest factors include:

• Number of unique templates and components
• Number and complexity of critical user flows
• Number of accessibility barriers discovered
• Severity and technical complexity of those barriers
• Availability of internal developers
• Existing development sprint schedules
• CMS and platform limitations
• Number of PDFs and other documents requiring remediation
• Number of videos requiring captions or audio description
• Third-party platforms and embedded tools
• Availability of staging and test environments
• Procurement or vendor dependencies
• Number of remediation and validation cycles required
• Speed of internal approvals
• Release and deployment schedules
• A project may contain 100 hours of actual accessibility work but still span several months because testing, remediation, deployment, and validation do not always happen consecutively.

Phase 1: Discovery and Automated Scanning (1 to 2 weeks)

Initial site, document, and media inventory, automated scanning, and scoping. This identifies the size of the problem.

Phase 2: Manual Audit and Assistive Technology Testing (2 to 8 weeks)

Manual expert review of every page template, keyboard navigation testing, screen reader testing across multiple browser/AT combinations, and documentation of every barrier. For small sites, this can take as little as one to two weeks. For large or complex sites, expect three to five weeks or more.

Phase 3: Report and Developer Triage (1 to 2 weeks)

The audit findings are compiled into a structured report, prioritized by severity and user impact, and handed off to the development team with specific remediation instructions for each barrier.

Phase 4: Engineering Sprints (4 to 24 weeks)

This is where the actual fixes happen. For a small site with straightforward issues, remediation can take two to four weeks. For a mid-size site with moderate complexity, plan on six to eight weeks. For large sites with custom applications, complex forms, and significant document libraries, remediation can take three to six months or more.

What extends this phase: legacy CMS limitations, third-party widgets and plugins that need vendor cooperation, custom JavaScript applications, large document libraries requiring manual remediation, and limited internal developer availability.

Phase 5: Validation and Re-Testing (1 to 6 weeks)

After remediation, everything needs to be re-tested. The same assistive technologies, the same user flows, the same WCAG criteria. This phase produces the conformance report and documentation that makes your investment legally defensible.

Phase 6: Final Conformance Report and Handoff (1 week)

Final documentation may include the audit report, remediation status, validation results, testing methodology, unresolved risks, VPAT or Accessibility Conformance Report when applicable, and recommendations for ongoing monitoring.

Documentation should be maintained throughout the project rather than created only at the end.

Realistic Total Timeline

• Small organizations: 2 to 6 months
• Mid-size organizations: 4 to 8 months
• Large organizations: 8 to 20 months

If a vendor tells you they can remediate your entire site in two weeks, they’re either not doing manual testing, not producing documentation, or not doing the work correctly. Real accessibility takes time because it involves human judgment on every page, every form, every document, every video, and every user flow. Automated scanners catch only 30 to 40% of WCAG criteria. The remaining 60 to 70% requires a person.

The Cost of Getting It Wrong

Organizations that underestimate cost and timeline usually fall into one of three traps:

Trap 1: Buying an overlay instead.

Accessibility overlays cost $490 to $1,500 per month and promise instant compliance. They don’t work. The FTC fined AccessiBe $1 million for false claims. In 2024 and 2025, more than 1,000 lawsuits were filed against websites running accessibility overlays. You pay for years and end up with nothing.

This isn’t just our opinion. The Overlay Fact Sheet, signed by hundreds of accessibility advocates, developers, and disability organizations, states plainly that no existing overlay can make a website fully accessible. The signatories include the American Foundation for the Blind, the National Federation of the Blind, and the World Wide Web Consortium’s Web Accessibility Initiative. When the organizations representing the users these tools claim to serve unanimously say they don’t work, that’s not a debate. It’s a consensus.

Trap 2: Doing a partial project.

An organization budgets $15,000 for a site that needs $40,000 of work. They audit, fix the top issues, and call it done. But the documentation is incomplete, the deeper barriers remain, and they’re still vulnerable. Partial compliance is not compliance.

Trap 3: Waiting until after a lawsuit.

Federal web accessibility lawsuits hit 2,452 in 2024 and jumped to 3,117 in 2025, a 27% increase. Single-plaintiff settlements run $5,000 to $35,000. Legal defense costs $5,000 to $50,000 for early settlements and $50,000 to $150,000+ for litigated cases. DOJ civil penalties reach up to $115,231 for a first violation and $230,464 for subsequent violations. Class action settlements have exceeded $5 million.

And you still have to do the remediation afterward, usually under a court-ordered deadline of 90 to 180 days. Emergency remediation costs 5 to 10 times more than proactive work due to rushed developer overtime, mandatory third-party auditor fees at $200 to $350 per hour, and required multi-year compliance reporting.

How to Budget Correctly

Start with a real audit from a firm that does manual testing and produces defensible documentation. Use the audit to scope the remediation accurately. Budget for documentation as part of the project, not as an add-on. Plan for ongoing monitoring from day one.

Here’s a framework for allocating your annual accessibility budget:

• 25 to 30%: Continuous audit and testing (manual plus automated)
• 30 to 40%: Core engineering and component remediation
• 15 to 20%: Document and PDF remediation
• 10 to 15%: Staff training and upskilling
• 5 to 10%: Contingency for third-party vendor audits and unexpected scope

If the total seems high, remember: accessibility is a compliance function, not a marketing expense. It belongs in the same budget category as your HIPAA program, your data security audits, and your quality reporting. And if you build accessibility into new development from the start, it adds only 5 to 15% to your design and development budget. Retrofitting existing code costs 10 to 30 times more.

The question isn’t whether you can afford to do it correctly. It’s whether you can afford not to.