Website Accessibility Compliance in India 2026: WCAG, SEBI Mandate, ADA/EAA Risk and the Real Cost to Fix It

Why Accessibility Is Suddenly on Every CTO's Desk

We've had "add alt text to your images" sitting in project checklists for a decade. What changed in the last twelve months is that accessibility stopped being a nice-to-have and started showing up as a hard compliance line item with real dates attached. If you're a SEBI-regulated entity — a broker, depository participant, mutual fund, or RTA — your accessibility audit was due April 30, 2026, and your remediation report is due July 31, 2026. That's days from when we're publishing this. If you sell software or run a website that touches the EU, the European Accessibility Act has already been in force for new digital content since June 28, 2025, with a hard deadline of June 28, 2030 for everything else. If you serve US customers, ADA Title III lawsuits are running past 4,000 filings a year, and even though the DOJ pushed the Title II deadline for state and local governments out to April 2027 and 2028, the private lawsuit pipeline hasn't slowed at all.

None of this is happening because accessibility got harder to build. It's happening because the market, left alone, keeps getting less accessible, not more. The WebAIM Million report — an annual scan of the top one million home pages — found in its 2026 edition that 95.9% of home pages still trip basic WCAG checks, with an average of 56 detectable errors per page, up roughly 10% from the year before.

This is the honest version of what's actually required: what an Indian business — or a global one with an Indian engineering team — has to comply with, what a real audit and remediation cost in 2026, and why the shortcut most vendors pitch, the overlay widget, doesn't hold up in a courtroom or a SEBI filing.

What "WCAG Compliant" Actually Means

WCAG — the Web Content Accessibility Guidelines — is the technical standard almost every regulation in this article points back to. It's built on four principles: content has to be Perceivable, Operable, Understandable, and Robust (POUR, if you want the acronym), and it comes in three conformance levels. Level A is the bare minimum. Level AA is what every regulation covered here actually requires. Level AAA is rarely mandated and often impractical to hit across an entire site.

Two versions of the standard matter right now. WCAG 2.1 AA is the baseline SEBI, GIGW 3.0, the EAA, and the DOJ's ADA rule all cite. WCAG 2.2, finalized in 2023, adds nine success criteria on top of 2.1 — larger minimum touch-target sizes, consistent placement of help mechanisms across pages, and not forcing users to re-enter information they've already given you, among others. Nothing in Indian or EU regulation mandates 2.2 yet, but every standard is heading in that direction, and building to 2.2 now costs very little extra over 2.1 if the work is done properly the first time.

Who Actually Has to Comply, and by When

Five different rules apply depending on who you sell to and who regulates you. Here's the honest map, much like the engineering-first approach we outlined for DPDP Act compliance — this is a build problem before it's a paperwork problem.

If you're an Indian SME selling only within India with no government contracts, nothing in this table is a hard legal mandate yet for you specifically — but the RPwD Act 2016 already gives persons with disabilities standing to challenge inaccessible digital services, and GIGW 3.0 is fast becoming the bar enterprise procurement teams expect vendors to clear. If you're SEBI-regulated, sell into the EU, or run any US-facing product, treat every date above as real and put it on a calendar.

What Compliance Actually Costs in India in 2026

Two different things get sold under "accessibility services," and vendors who quote one number for both are usually pricing you the cheap half: an audit (finding the problems) and remediation (fixing them). For context on how this compares to a typical build, see our website development cost guide.

Audit Cost by Site Size

Remediation & Ongoing Cost

The number that changes this math completely is timing. Building accessibility in during a new site or app build — accessible components, proper heading structure, keyboard navigation, color contrast — typically adds 5–8% to a normal design and development budget. Retrofitting the same standard into a site that already has 150 pages of inaccessible markup costs a multiple of that, because you're re-testing and re-shipping components you already built once. If a redesign is already on your roadmap, this is the cheapest point in the project's life to fix it.

Why the Overlay Widget Everyone Pitches You Doesn't Work

The fastest-selling "fix" on the market is a JavaScript overlay widget — a script tag that promises to make an existing site WCAG-compliant in minutes, no code changes required. It's also the fix regulators, courts, and the disability community have spent the last eighteen months actively dismantling.

In January 2025, the US Federal Trade Commission ordered accessiBe, the best-known overlay vendor, to pay $1 million for misrepresenting what its tool could actually do — the FTC found the company had marketed "full WCAG 2.1 AA compliance within 48 hours," which its own technology could not deliver. A related class-action settlement, capitalized at $1.2 million, began paying out claimants in early 2026. The National Federation of the Blind has stated plainly that overlay widgets "do not make websites accessible," and screen reader users report the widgets routinely interfere with the assistive technology they already use, breaking keyboard navigation instead of fixing it.

The legal record backs this up: in the first half of 2025, 22.6% of new US ADA lawsuits targeted websites that already had an overlay installed, and federal courts have consistently rejected the argument that installing one constitutes a good-faith compliance effort. For a SEBI filing specifically, an overlay does not satisfy the audit-and-remediation-report requirement — auditors check the underlying code, not whether a widget is present.

The Decision Framework We Use With Clients

Which path makes sense depends entirely on where you're starting from.

• New build or redesign already scheduled: bake WCAG 2.1 AA (and ideally 2.2) into the design system and component library from day one. This is close to free — it's the same work done in the right order.
• Existing site, under 25 pages, no regulatory deadline: a manual audit followed by a focused 2–4 week remediation sprint usually clears the highest-impact issues — navigation, forms, contrast, alt text — without a full rebuild.
• SEBI-regulated or enterprise platform with a hard deadline: a phased plan matched to the actual submission dates. Audit now if you haven't, remediate the issues that block core user journeys (login, KYC forms, transactions) first, and treat the rest as an ongoing retainer rather than a one-time project.

What a Proper Remediation Engagement Looks Like

A remediation engagement that actually holds up under audit runs in four stages, and it looks a lot like the same rigor we describe in our software audit services guide:

• Audit: manual testing plus automated scanning and real screen reader sessions — not just a Lighthouse score.
• Prioritize: by user impact and fix effort, not by raw violation count.
• Fix: in the same two-week sprint cadence as the rest of your product work, verified against a written scope.
• Verify & Monitor: screen reader retesting, automated regression checks in CI so a future deploy doesn't quietly reintroduce the same bugs, plus an annual re-audit.

None of this is exotic. It's disciplined engineering process applied to a category most teams have never had a process for.

The Business Case Beyond the Compliance Deadline

Compliance is the reason this is on your desk this quarter, but it's not the only reason it's worth doing well. Accessible markup — clean semantic HTML, proper heading order, real alt text, keyboard-navigable interactions — overlaps heavily with the same fundamentals that drive Core Web Vitals and SEO, as we cover in UI/UX Design ROI in 2026. India's officially registered population of persons with disabilities is 26.8 million and rising alongside an aging internet user base, and every one of those users is a visitor your site either serves or silently turns away. Fixing accessibility as a side effect of a website rebuild is rarely the reason a client calls us — but it's consistently one of the better returns buried inside a project they called us for anyway.

Working With Us

If a SEBI deadline, an EU customer, or a US contract just put accessibility on your roadmap — or you're planning a redesign anyway and want to build it in properly the first time — our Web Development team runs WCAG 2.1/2.2 AA audits and remediation as a standard part of every build, priced and scoped the same transparent way as the rest of our work: fixed scope, two-week sprints, no surprise line items. Book a free 30-minute consultation and we'll tell you honestly whether you need a full audit, a focused sprint, or nothing at all yet.