Blog Post
The $10K Alt Tag: Accessibility Costs 10x More
A single missing alt tag costs 30 seconds to specify during design but $10,000 or more to remediate after launch. This article breaks down the real cost of accessibility violations caught at each stage — design, development, QA, and production — and presents a three-checkpoint audit framework that catches issues when they are cheapest to fix.
A designer ships a feature. Clean design file. Approved in design review. Three sprints later, an accessibility audit flags 34 violations. Fourteen are contrast failures the designer chose. Eight are missing alt text on images where the designer knew whether they were decorative or meaningful. Six are heading hierarchy issues baked into the layout. The alt text that would have taken 10 seconds to specify in a design annotation now burns 4 hours across three people.
The Math Nobody Shows Designers
The total cost of poor software quality hit $2.41 trillion in 2025. Expert WCAG audits run $2,500 to $10,000. Technical remediation costs $5,000 to $20,000 for just five pages. For SaaS platforms, a full audit-remediate-verify cycle runs $30,000 to $60,000. The first half of 2025 saw 2,014 federal ADA website lawsuits, a 37% increase from 2024. The average total cost of a lawsuit lands between $45,000 and $75,000.
Most Accessibility Violations Start in Your Design File
Developers get blamed for accessibility failures. But look at the top WCAG violations and count how many are design decisions:
- Contrast ratios (WCAG 1.4.3): The designer chose the colors.
- Touch target size (WCAG 2.5.5): The designer set the tap area.
- Heading hierarchy (WCAG 1.3.1): The designer defined the visual hierarchy.
- Focus visibility (WCAG 2.4.7): The designer either specified focus states or did not.
- Color-only indicators (WCAG 1.4.1): The designer used red and green without a secondary cue.
- Alt text decisions (WCAG 1.1.1): The designer knows whether an image is decorative or meaningful.
The developer implemented exactly what was in the design file. The design file was wrong.
Audit During Design, Not After Launch
Most teams run accessibility audits right before launch or after a lawsuit. Both are too late. The moment a component renders on staging, it has contrast ratios, focus states, heading structure, and tap targets. All auditable. You are already going to audit. The only question is whether you do it when fixing is cheap or when fixing is expensive.
Three Checkpoints That Catch Everything
1. During Component Build (Staging): Run an audit on individual components as they hit the browser. Catch contrast failures, missing focus indicators, and ARIA label issues. Fix them in minutes.
2. During Design Review (Staging or Preview): Run a full page audit with Figma comparison. Check heading hierarchy, tab order, skip navigation, and touch targets.
3. Pre-Launch (Production URL): Final sweep. Catches integration issues: keyboard traps across components, focus order across page sections, skip-nav linking to the right target.
What This Looks Like With Tooling
OverlayQA's Accessibility Audit runs WCAG 2.1 AA checks directly in your browser. Static analysis, keyboard scanning, and AI visual analysis. One click, three engines, a score your team can act on during design review instead of after launch.
Frequently Asked Questions
How much does it cost to fix an accessibility violation after launch?
Remediation costs escalate 10-25x when caught in production versus during design. A missing alt tag takes 30 seconds to specify during design review but requires developer time, QA cycles, a new build, and deployment when caught post-launch. At agency rates, a single accessibility fix in production costs $500-2,000. Multiply by dozens of violations and the total reaches $10,000 or more.
What percentage of accessibility issues originate in design?
Research shows 67% of WCAG violations trace back to design decisions — insufficient color contrast, missing focus indicators, images without alt text plans, touch targets below 44px. These are cheaper to fix during design review than after code is written. A design QA checkpoint that includes accessibility catches the majority of violations before they become code.
How do you prevent expensive accessibility fixes?
Shift accessibility left with three checkpoints: a design review that checks contrast, focus states, and alt text plans in the design file; a staging review that tests keyboard navigation and screen reader behavior; and a pre-launch audit with automated scanners plus manual testing. Each checkpoint catches issues at a fraction of the post-launch remediation cost.