digi.ai.in
← digi.ai.in / blog
2026-07-279 min readCost

The Real Cost of Skipping Accessibility Until Later

Retrofitting accessibility later costs more than building it in — the exact multiple is disputed, but the direction is not.

Fixing accessibility after a site or app is already built almost always costs more than designing for it from day one. How much more is genuinely disputed across the industry — estimates range from a 10-30% cost bump to a 30x multiplier — but every source that measures it points the same direction, and in India the calculation now includes regulatory exposure that didn't exist a few years ago.

This post lays out the actual numbers, where they disagree, and what that means for a founder or ops lead in Pune or anywhere else in India deciding whether to deal with accessibility now or "later."

The retrofit multiplier: what the numbers actually say

There's no single, agreed-upon figure for how much more expensive retrofitting is compared to building accessibly from the start. Here's what different sources report, side by side:

Source Claimed cost of retrofitting vs. building in from the start
BarrierBreak 10-30x more expensive; a defect caught in QA costs ~$350 to fix, the same defect in production costs $800+ source
AudioEye 6x more expensive when retrofitted instead of planned in during content creation source
2Hats Logic 10-30% higher cost, not a multiple source
Project Cost Estimator (2026) 2.5-4x more expensive than building accessibly from scratch source
Tim Springer, CEO, SSB BART Group (via WSJ) Retrofitting typically runs ~10% of total website cost; phasing accessibility in during natural upgrades runs 1-3% source

Worth being honest about this spread. Most of these figures come from accessibility-tooling vendors or consultancies who have a commercial reason to make retrofitting sound expensive. None of them show their working in a way you can independently verify. The one number attributed to a named, quotable person rather than an anonymous "research shows" is Springer's — and even that is a rough industry estimate, not a controlled study.

The practical takeaway isn't "believe the 30x number." It's this: every source that has looked at this question, regardless of methodology, finds retrofitting more expensive than building in from the start. The size of the gap depends on how deep the existing problems are, how the codebase is structured, and how late you catch things — a bug caught in a design review is cheaper to fix than one caught after launch, in any framework, for any reason. Accessibility isn't special in that sense. It's just usually caught later than most other defects, because most teams don't test for it until something forces them to.

What "later" usually means in practice

For most Indian web and app teams, accessibility gets deferred because nobody flags it during design or build. It typically resurfaces in one of three ways:

  1. A client or investor due-diligence checklist asks about WCAG compliance and nobody has an answer.
  2. A regulator or a government tender requires it — increasingly common if you sell into the public sector or regulated finance in India (more on this below).
  3. A user or advocacy group complains, or in the US, a lawsuit gets filed.

In the US, the third path is now a real cost driver: 8,800 web accessibility lawsuits were filed in 2024 source, and settlement figures are commonly cited in the range of $25,000-$55,000 excluding legal fees and remediation source, with a more recent estimate putting settlements at $25,000-$75,000 for 2025-2026 source. If you build for US customers or sell into US markets, this is a real line item, not a hypothetical.

For India specifically, there's no equivalent public dataset of lawsuit volume or settlement amounts. That doesn't mean there's no exposure — it means the exposure runs through a different channel, described below.

The state of the web: it's not getting steadily better

If you assume the web is gradually becoming more accessible on its own, the data doesn't support that. WebAIM's annual scan of the top one million home pages found:

  • 2024: 95.9% of home pages had detectable WCAG 2 failures, averaging 56.8 errors per page — a 13.6% increase over 2023 source.
  • 2025: average errors dropped to 51 per page, a 10.3% decrease source.
  • 2026: errors rose again to 56.1 per page, a 10.1% increase, "reversing a trend of gradual improvements" source.

The pattern is not a steady decline or improvement — it oscillates year to year. That matters for planning: you can't assume the industry baseline is drifting toward compliance and that you'll be fine by default if you wait. Whatever the average site looks like this year, there's a real chance it looks worse next year, and yours will be judged against whatever the standard is at the time someone checks.

What accessibility gets you beyond avoiding a complaint

The W3C's Web Accessibility Initiative frames the business case in four parts: SEO benefit, reduced legal risk, demonstrated corporate social responsibility, and increased customer loyalty source. The same page cites the 2008 National Federation of the Blind settlement with Target as the early landmark case that put accessibility on general counsel's radar in the US.

Market-size claims here need a caveat. One accessibility vendor cites a figure that people with disabilities, plus friends and family, control $13 trillion annually in disposable income globally, and that 97% of the internet is inaccessible to people with disabilities, against a backdrop of 1.3 billion people worldwide living with a disability source. These numbers could not be independently cross-verified against a primary source like WHO or a market-research firm in this research, so treat them as directional industry figures rather than audited statistics. The more conservative, verifiable point is simpler: a meaningful share of your addressable market cannot use an inaccessible product properly, and that's true whether or not the $13T figure is precisely right.

India's specific compliance picture

This is where the calculation changes for a studio or business operating in India, and it's worth being precise about which rules apply to whom.

The Rights of Persons with Disabilities Act, 2016 (RPwD Act) mandates equitable digital access for India's 26.8 million persons with disabilities source. Two sections matter most:

  • Section 42 requires equal ICT access, including websites, digital content, and electronic media.
  • Section 46 requires accessibility for government documents, services, and public information made available digitally source.

GIGW 3.0, issued by the National Informatics Centre under MeitY, governs government websites specifically. It incorporates WCAG 2.1 Level AA as the baseline and adds 88 mandatory checkpoints on top of that source source. If you're building anything for a government client or PSU tender, this is the standard you'll be measured against, not a vague "WCAG compliance" line item.

IS 17802 is the Bureau of Indian Standards' formal adoption of WCAG 2.1. A June 2025 SEBI circular explicitly references IS 17802 alongside WCAG 2.1 and GIGW for regulated financial-sector entities — stock exchanges, brokers, mutual funds, insurers, and fintechs source. If you're building for a fintech, brokerage, or insurance client, this is no longer optional guidance — it's a named requirement from the market regulator.

The market context that makes this urgent regardless of regulation: digital transactions in India grew 56% in FY 2022-23 and are projected to quadruple by FY 2026-27, and 79% of India's web traffic already comes from mobile devices source. India's Supreme Court has also recognized internet access as a fundamental right, reinforcing the constitutional weight behind digital accessibility obligations source. More of your users are arriving on more constrained devices and connections every year, which is exactly where accessibility failures — small tap targets, poor contrast, missing alt text — cause the most friction.

The genuine gap in the India picture: unlike the US, no public dataset of lawsuit volume or settlement values for accessibility exists for India in the research behind this post. Enforcement here appears to run through STQC-empanelled audits and regulatory circulars — SEBI, GIGW — rather than a visible pattern of private civil litigation. That's a real difference from the US market, and it means the "you'll get sued" argument common in US accessibility content doesn't translate directly here. The more accurate India argument is regulatory and commercial: government and financial-sector tenders increasingly name specific standards, and a site that fails them simply doesn't qualify, lawsuit or no lawsuit.

A practical checklist for deciding when to act

If you're weighing whether to deal with accessibility now or defer it, these are the questions that actually change the answer:

  • Do you sell to government, PSU, or regulated financial clients? If yes, GIGW 3.0 or the SEBI/IS 17802 requirement isn't optional — build to WCAG 2.1 AA from the start.
  • Do you have US customers or users? If yes, factor in the lawsuit volume and settlement-cost data above as a real, if uncertain, liability.
  • Is more than half your traffic on mobile? Given the 79% mobile-traffic figure for India source, accessibility fixes like contrast, tap-target size, and reflow tend to double as general mobile-usability fixes — so the cost is shared with work you'd want to do anyway.
  • Are you mid-build or already launched? If mid-build, every source in this research agrees it's cheaper to fix now than after launch — whether that's a 10% cost premium or a 10x one depends on how deep the problems run, not on whether you should act.
  • Do you have a way to test regularly, not just once? WebAIM's data shows accessibility on the web doesn't steadily improve on its own — it oscillates year to year source. A one-time audit without a retest cadence just delays the same problem.

Questions people also ask

Is the "10x more expensive to retrofit" claim actually true?

It's one of several figures in circulation, ranging from a 10-30% cost increase source to a 30x multiplier source, mostly from vendors with a commercial interest in the number being large. None are independently audited studies. The safer statement is that every source agrees retrofitting costs more than building in from the start — the exact multiple depends on your specific codebase and how late you're catching problems.

Does India have accessibility lawsuits like the US does?

No public dataset showing lawsuit volume or settlement figures for India accessibility cases turned up in this research, unlike the US where 8,800 web accessibility lawsuits were filed in 2024 source. India's enforcement mechanism instead runs through regulatory requirements — the RPwD Act, GIGW 3.0 for government sites, and SEBI's 2025 circular referencing IS 17802 for financial-sector entities source.

Which Indian businesses are actually required to meet WCAG standards?

Government websites and public-sector tenders must meet GIGW 3.0, which sets WCAG 2.1 AA as the baseline plus 88 additional checkpoints source. Regulated financial entities — stock exchanges, brokers, mutual funds, insurers, fintechs — are covered by a June 2025 SEBI circular referencing IS 17802 and WCAG 2.1 source. Beyond these, the RPwD Act's Section 42 establishes a broader mandate for equal ICT access source, though enforcement outside government and finance is less clearly mapped out in available sources.

Written by the studio behind digi.ai.in. Questions? hi@digi.ai.in or WhatsApp +91 98605 96905
WhatsApp us