Accessibility-Failure Rework Cost: WCAG Remediation Math
Updated May 2026. Sources: Deque, Level Access, UsableNet ADA Lawsuit Report 2024, W3C Web Accessibility Initiative.
The headline numbers
- Retrofit cost premium over design-time conformance: 6 to 15 times
- Typical first-audit findings (mid-sized SaaS): 200 to 800 WCAG 2.2 AA issues
- US ADA web/app lawsuits per year (UsableNet 2024): 4,000 to 4,500
- Typical single-site settlement: $10K to $75K
- Cost of building WCAG 2.2 AA in from the start: 2 to 5% of design + front-end capacity
The retrofit cost premium
The 6-to-15-times-cost retrofit premium is one of the more durable findings in the accessibility-engineering literature. Deque's decades of consulting work, Level Access's benchmarking research, and the W3C Web Accessibility Initiative's guidance all triangulate to similar numbers. The premium emerges from three structural realities of the typical retrofit project.
First, retrofitting often requires re-doing component-library work that was already shipped. A button component that does not handle keyboard focus correctly needs to be updated everywhere it is used, not just where the accessibility audit flagged the failure. The fan-out from a single root cause to many call-site updates is the dominant cost driver on most retrofit programmes.
Second, design decisions made without accessibility in mind sometimes need to be re-done at the design layer, not just at the code layer. A colour palette that fails WCAG contrast requirements needs new design tokens; a layout that breaks under 200% zoom needs new responsive rules; a flow that depends on hover interactions needs a touch-and-keyboard alternative. These design-layer fixes propagate through the component library and into the brand system, which is where retrofit costs blow out compared to original design-time investment.
Third, retrofitting under deadline pressure (typically driven by a lawsuit demand letter, a major enterprise customer's VPAT request, or an inbound regulatory query) almost always costs more than retrofitting on a normal sprint cadence. The premium-on-the-premium for emergency retrofits is meaningful: teams that find themselves working a 90-day VPAT deadline typically spend 50 to 100% more than they would have spent at their normal pace.
The ADA lawsuit risk
UsableNet's 2024 ADA Web and App Accessibility Lawsuit Report tracks roughly 4,000 to 4,500 federal accessibility lawsuits filed per year in the US, with retail, restaurants, travel, and food service as the most-targeted sectors. The plaintiff bar has matured into structured-litigation campaigns; a single law firm may file hundreds of substantially similar complaints per year, targeting companies with crawlable accessibility issues and identifiable revenue.
Settlement amounts typically range $10K to $75K for a single-site claim, often with a remediation commitment attached. Class-action and multi-site claims can run substantially higher (the Domino's case, which was eventually settled, generated estimated total legal costs in seven figures across the multi-year litigation). The Robles v. Domino's Pizza Supreme Court denial of certiorari in 2019 left the 9th Circuit's pro-plaintiff ruling in force, which has been widely cited as the most important modern precedent encouraging the current wave of ADA web litigation.
The pragmatic risk calculation: any consumer-facing US commercial site without WCAG 2.2 AA conformance has non-trivial annualised lawsuit risk. A reasonable working estimate, drawn from UsableNet's longitudinal data and from observed industry settlement patterns, is roughly 1 to 3% per year for an exposed mid-sized site. The expected-value cost (probability times settlement) is often a meaningful fraction of the cost of just fixing the underlying issues.
The shift-left investment
Building WCAG 2.2 AA conformance into the product from the start typically costs 2 to 5% of total design and front-end engineering capacity in the first year, dropping to roughly 1 to 2% in subsequent years as the design system and component library are hardened. The investment shape is mostly upfront capacity (training, component-library updates, design-system rework, pre-merge automated testing setup) rather than ongoing tax.
The components of a typical shift-left accessibility programme are: a design-system audit and update pass (often the largest single line item, typically 4 to 12 engineering weeks for a mid-sized component library), automated pre-merge testing with axe-core or Pa11y (1 to 3 weeks setup, ongoing maintenance modest), periodic manual audits by users with disabilities (typically 1 to 2 days per major release), and a component-library convention that no new component ships without keyboard, screen-reader, and contrast validation.
Deque's published research on automated testing puts the catch rate at roughly 30 to 40% of WCAG 2.2 AA issues. The remaining 60 to 70% requires manual testing. The most common failure mode for shift-left programmes is over-reliance on automated checks: teams that ship without manual review typically catch the easy contrast and label issues but miss the keyboard-navigation, focus-management, and cognitive-load issues that drive the majority of real-user accessibility problems.
The procurement angle
B2B SaaS organisations face a different cost driver from consumer sites: enterprise procurement increasingly requires a Voluntary Product Accessibility Template (VPAT) demonstrating WCAG 2.2 AA conformance. Public-sector customers (Section 508), large enterprise customers, and any customer with disabled employees may make the VPAT a deal-blocking requirement. A late VPAT response (or a VPAT that admits material non-conformance) can cost a deal directly, with revenue impact that dwarfs the rework labour. The implication: B2B SaaS accessibility ROI usually starts with the first lost-deal VPAT rather than with ADA litigation risk. The regulatory-compliance rework page covers the broader procurement-driven compliance pattern.
Sources
- UsableNet. 2024 ADA Web and App Accessibility Lawsuit Report. usablenet.com.
- W3C Web Accessibility Initiative. Web Content Accessibility Guidelines (WCAG) 2.2. w3.org/TR/WCAG22.
- Deque Systems. Industry research on automated testing catch rates and retrofit cost premiums.
- Level Access. Industry benchmarking research on accessibility programme cost.
- Robles v. Domino's Pizza, LLC. 913 F.3d 898 (9th Cir. 2019); cert. denied, US Supreme Court 2019.
- Section 508 of the Rehabilitation Act of 1973 (US federal agencies and contractors).
Frequently asked questions
What does accessibility remediation cost?▼
Retrofitted fixes are 6 to 15 times more expensive than designing for WCAG conformance from the start. Per-finding labour: 1 to 4 hours for colour-contrast or aria-label fixes; 40+ hours for component-level keyboard-navigation rework. First-audit findings on a typical SaaS site: 200 to 800 WCAG 2.2 AA issues.
How big is the ADA lawsuit risk?▼
UsableNet 2024 tracks 4,000 to 4,500 federal accessibility lawsuits per year. Single-site settlements typically $10K to $75K; class-action and multi-site claims can run substantially higher. Most-targeted sectors: retail, restaurants, travel, food service.
Is accessibility legally required in the US?▼
ADA Title III is widely interpreted by courts to cover commercial sites that serve as places of public accommodation. Robles v. Domino's Pizza (9th Cir. 2019) is the leading modern precedent. Section 508 covers federal agencies and contractors. State laws (Unruh Act in California, NYSHRL in New York) add layers.
What does WCAG 2.2 AA conformance cost from the start?▼
2 to 5% of design and front-end engineering capacity in year one, dropping to 1 to 2% in subsequent years. Investment is mostly upfront capacity (component-library hardening, training, automated testing setup) rather than ongoing tax.
Does automated accessibility testing catch enough?▼
No. Automated testing (axe-core, Pa11y, Lighthouse) catches 30 to 40% of WCAG 2.2 AA issues per Deque. The remaining 60 to 70% requires manual testing (keyboard navigation, screen-reader, cognitive load), ideally including testing by users with disabilities.
Do B2B SaaS companies need accessibility?▼
Increasingly yes, driven by VPAT requirements in enterprise procurement. A late or weak VPAT can be a deal-blocker, with revenue impact that often dwarfs the rework cost. Public-sector procurement (Section 508) makes VPATs effectively mandatory for federal-adjacent business.