Digital Accessibility in India: From Compliance to Inclusive Digital Experience

India has built some of the most ambitious digital public infrastructure on earth. Hundreds of millions of people transact on UPI, hold documents in DigiLocker, file taxes online, and access welfare through government portals and apps. Digital-first is no longer a strategy in India — it is the default.

Which raises a question that too few product teams ask: is all of it usable by everyone?

For the more than 26 million Indians who live with a disability — and the far larger number who experience low vision, reduced dexterity, or cognitive load as they age — a digital service that isn't accessible isn't merely inconvenient. It is a locked door to banking, healthcare, education and government itself. Digital accessibility is how you unlock it. And in India, it is now both a legal obligation and a competitive advantage.

This guide covers what digital accessibility means in India, the law and standards you must meet, and — the part most teams miss — how to move beyond ticking a compliance box to building a genuinely inclusive digital experience.

Why digital accessibility matters more in India than almost anywhere

Three forces make this urgent here in a way they aren't everywhere:

• Scale. When a single government portal serves hundreds of millions, even a small accessibility failure excludes a city's worth of people.

• Digital public infrastructure. As essential services — payments, identity, health records, subsidies — move onto digital rails, an inaccessible interface becomes exclusion from the state, not just from a website.

• Demographics and diversity. India's population is ageing, multilingual, and spans an enormous range of literacy and device access. Designing for that range isn't a niche accommodation; it is designing for the actual user base.

Accessibility, in other words, is not a minority concern in India. It is a mainstream design requirement wearing an unfamiliar name.

The law: what India requires of digital products

The legal anchor is Section 42 of the Rights of Persons with Disabilities Act 2016, which requires that information and communication technology — websites, apps, documents and electronic media — be made accessible to persons with disabilities. Section 46 extends the duty to service providers, public and private.

Two national standards operationalise this:

• IS 17802 — the Bureau of Indian Standards standard for the accessibility of ICT products and services, published in two parts: Part 1 (2021) sets the requirements, and Part 2 (2022) defines how conformance is determined. It is India's own digital-accessibility standard, closely modelled on the international benchmark.

• GIGW 3.0 — the Guidelines for Indian Government Websites and Apps, issued by the National Informatics Centre. GIGW 3.0 requires conformance with WCAG 2.1 Level AA, adding the cognitive, low-vision and mobile success criteria that earlier versions lacked.

If you build or operate a government website or app in India, GIGW 3.0 compliance is effectively mandatory. If you build consumer digital products, IS 17802 and the RPwD Act apply to you too. (Digital is one of three verticals of accessibility obligation in India — for the full legal picture across buildings and transport as well, see our complete guide to accessibility audit and certification in India.)

The global benchmark: WCAG, EN 301 549 and the European Accessibility Act

India's standards don't exist in isolation — they converge on the Web Content Accessibility Guidelines (WCAG), the international standard maintained by the W3C. WCAG is built on four principles, known by the acronym POUR: content must be Perceivable, Operable, Understandable and Robust. Conformance comes at three levels — A, AA and AAA — with AA the standard regulatory target worldwide.

The current version, WCAG 2.2 (published in 2023), adds success criteria that matter enormously in practice: minimum target sizes for touch, visible focus indicators, accessible authentication that doesn't rely on memory, and help with dragging movements. It is the benchmark serious teams now design to, even ahead of regulation.

Two further references raise the bar for India-based teams with global ambitions:

• EN 301 549 — the European standard for ICT accessibility, which incorporates WCAG and is the reference for public procurement across the EU.

• The European Accessibility Act (Directive (EU) 2019/882), whose accessibility requirements applied from June 2025. Any Indian SaaS company, e-commerce business or app maker selling into the European market now faces a hard accessibility requirement — making WCAG conformance a market-access issue, not just a compliance one.

For a fuller map of how the Indian and international standards fit together, see the Universal Access guidelines.

From compliance to inclusive experience: the four shifts

Meeting a standard is necessary. It is not the same as being usable. A product can pass an automated scan and still be exhausting to operate with a screen reader, or bewildering for someone with a cognitive disability. Moving from compliance to genuine inclusion means making four shifts.

1. From checklists to user journeys

Compliance asks "does this page pass?" Inclusion asks "can a person actually complete the task?" — from landing on the homepage, through search and form-filling, to confirmation. Accessibility lives in the whole journey, not in isolated pages, and a single broken step (an unlabelled button, a time-out that can't be extended) can defeat everything around it.

2. From automated scans to human testing

Automated tools catch perhaps a third to a half of accessibility issues — missing alt text, poor contrast ratios, absent form labels. They cannot tell you whether a screen-reader user can understand your navigation, whether your error messages make sense, or whether a keyboard-only user can escape a modal. Only testing with people who use assistive technology reveals that. This is why a credible audit pairs technical testing with a lived-experience walkthrough.

3. From retrofit to "shift left"

Fixing accessibility after launch is the most expensive way to do it. Building it in from the first design sprint — accessible components, semantic structure, tested patterns — costs a fraction and produces a better product. The cheapest accessible product is the one that was designed accessible.

4. From "edge case" to design driver

The most inclusive teams stop treating disability as an exception to design around and start treating it as a source of better design for everyone. Captions help commuters in noisy trains; high contrast helps anyone in bright sunlight; clear language helps every user under stress. This is the heart of Design for All (EN 17161) — accessibility as a way of designing, not a feature to bolt on.

What a digital accessibility audit covers

A thorough digital accessibility audit assesses:

• Websites and web apps — against WCAG 2.2 AA, with keyboard, screen-reader and zoom testing.

• Mobile apps — native accessibility APIs on Android and iOS, touch target sizes, and gesture alternatives.

• Documents — accessible PDFs and forms, which are often the weakest link in a government service.

• Self-service kiosks and terminals — the physical–digital boundary that IS 17802 and EN 301 549 both cover, and that most audits overlook.

The output is not a raw error dump but a prioritised remediation plan, scored against the standard and validated with users — the same six-stage process used across the Universal Access framework.

The business case: accessibility pays

Beyond the legal duty, digital accessibility is simply good business:

• Reach. You stop excluding a significant share of your potential users and customers.

• SEO. The same discipline that makes a site accessible — semantic structure, alt text, clear headings, fast keyboard-navigable pages — is what search engines reward.

• Risk. RPwD obligations, GIGW mandates for public bodies, and the European Accessibility Act for exporters all carry real consequences.

• Procurement. Government and enterprise buyers increasingly require accessibility conformance to even bid.

Getting started

Digital accessibility in India has moved decisively from "nice to have" to "must have" — and, for the best teams, to "how we build." Whether you run a government portal that must meet GIGW 3.0, a consumer app that should meet IS 17802, or a SaaS product selling into the EU under the Accessibility Act, the path is the same: assess honestly, fix by priority, and design inclusively from here on.

Ready to find out where your digital products stand? Request a digital accessibility audit →

Part of our accessibility series — start with the pillar guide, Accessibility Audit & Certification in India. Explore further: the standards behind certification · the audit framework · certification tiers.

Universal Access is a joint initiative of The Institute of Human-Centred Design and the Inter University Centre for Disability Studies (IUCDS), Mahatma Gandhi University, aligned with the RPwD Act 2016 and the Accessible India Campaign.