70 million Indians have disabilities. Your website probably excludes most of them. In some sectors, that's now illegal. Even where it isn't, it's leaving ₹100s of crores on the table. Here's what accessibility actually means in 2026.
What Website Accessibility Actually Means
Website accessibility means that people with disabilities — visual, auditory, motor, cognitive — can perceive, understand, navigate, and interact with your website. That's it. No mystery, no magic.
Practically, it means a blind person using a screen reader can navigate your site and complete a purchase. A person with limited hand mobility can use your forms with only a keyboard. A person with colour blindness can read your text without squinting. A person with a cognitive disability can understand your content without a PhD.
The technical standard is called WCAG (Web Content Accessibility Guidelines), published by the W3C. The current version that matters is WCAG 2.2, released in late 2023 and now the de facto compliance target worldwide. India's government accessibility guidelines reference WCAG directly.
Accessibility isn't a feature you bolt on after launch. It's a design and development approach that, when done right, makes your site better for everyone — not just people with permanent disabilities. Think of a parent holding a baby trying to use your checkout one-handed, or someone in bright sunlight who can't see low-contrast text.
Why Accessibility Matters for Indian Businesses
Legal: The RPwD Act 2016 Is Real
The Rights of Persons with Disabilities Act, 2016 (RPwD Act) replaced the outdated 1995 Disabilities Act and expanded the definition of disability from 7 to 21 categories. Section 46 explicitly requires accessible information and communication technology.
Government websites and services funded by the government must comply with the Guidelines for Indian Government Websites (GIGW), which mandate WCAG 2.0 AA compliance. But the RPwD Act's language is broad enough to cover private-sector digital services, especially those in banking, insurance, telecom, e-commerce, and education.
Enforcement has been slow — but it's accelerating. The Chief Commissioner for Persons with Disabilities has been issuing directives, and PIL (Public Interest Litigation) cases are creating legal precedent. If you're in a regulated sector, waiting for a notice is a bad strategy.
India has approximately 70 million people with disabilities (Census 2011 + WHO estimates). With 900+ million internet users in 2026, the accessible market you're ignoring is larger than the entire population of many European countries.
Market: 70M+ Customers You're Probably Ignoring
The disability market in India is massively underserved online. Most e-commerce sites, fintech apps, and SaaS products are partially or fully inaccessible. The businesses that fix this first gain a structural advantage — loyalty from an underserved audience that has limited alternatives.
Beyond permanent disabilities, temporary and situational disabilities affect hundreds of millions more. A broken arm, an eye infection, a noisy environment, aging eyes. India's rapidly aging population means the number of people needing accessible interfaces is growing every year.
SEO: Google Rewards Accessible Websites
This isn't marketing fluff. The overlap between accessibility best practices and SEO signals is significant:
- Alt text on images — improves image search ranking and helps screen readers
- Proper heading hierarchy (H1 → H2 → H3) — helps crawlers understand content structure
- Descriptive link text — better than "click here" for both users and search engines
- Fast page load times — accessibility tools often surface performance issues
- Mobile responsiveness — essential for both accessibility and Google's mobile-first indexing
Accessible sites consistently outperform inaccessible competitors in organic search rankings.
Brand Reputation: Inclusion Is a Differentiator
In 2026, consumers — especially younger demographics — actively prefer brands that demonstrate social responsibility. An accessible website signals that you care about all your customers, not just the easy ones. That's a brand asset you can't buy with advertising.
Who Needs to Comply
Here's the honest breakdown of legal requirements in India as of 2026:
Mandatory compliance (GIGW + WCAG 2.0 AA):
- All central and state government websites and apps
- Public sector undertakings (PSUs)
- Government-funded educational institutions
- Government service delivery platforms
Strongly expected (RPwD Act Section 46 + sector regulators):
- Banks and financial institutions (RBI has issued digital accessibility guidelines)
- Insurance companies (IRDAI is moving toward accessibility mandates)
- Telecom operators
- E-commerce platforms above a certain scale
- EdTech platforms
- Healthcare platforms with public-facing services
Not yet legally required but smart to adopt:
- Private-sector B2B and B2C websites
- Startup MVPs and SaaS products
- Small business websites
If you're building for international markets — the US (ADA + Section 508), EU (European Accessibility Act, effective June 2025), or UK (Equality Act 2010) — accessibility is already legally required. Indian businesses exporting digital services need WCAG 2.2 AA compliance today.
Common Accessibility Barriers
Most websites fail accessibility because of a handful of recurring problems. Here's what breaks, grouped by the type of disability it affects.
Visual Barriers
- Images without alt text (screen readers announce "image" with no context)
- Low colour contrast between text and background (affects 300M+ people with colour vision deficiency worldwide)
- Text embedded in images (can't be resized or read by assistive technology)
- No support for browser zoom (site breaks at 200% zoom)
- Videos without captions or audio descriptions
Auditory Barriers
- Video content without captions or transcripts
- Audio-only content (podcasts, voice messages) without text alternatives
- Autoplay audio or video with no pause control
Motor Barriers
- Interactive elements too small to tap (below 44×44 CSS pixels)
- No keyboard navigation support (can't Tab through forms or menus)
- Drag-and-drop interactions with no keyboard alternative
- Time-limited interactions with no extension option
Cognitive Barriers
- Complex navigation with too many options
- Jargon-heavy language without explanations
- Animations that can't be paused or disabled
- Inconsistent layout between pages
- Error messages that don't explain what went wrong or how to fix it
WCAG Guidelines Overview
WCAG is organised around four principles, remembered by the acronym POUR: Perceivable, Operable, Understandable, Robust. Each principle has guidelines, and each guideline has success criteria at three levels.
| Level | What It Means | Who Needs It | Examples |
|---|---|---|---|
| Level A | Minimum baseline. Without this, some users literally cannot use your site. | Everyone. No exceptions. | Alt text on images, keyboard navigation, no keyboard traps, page titles |
| Level AA | The standard compliance target. Addresses the most common barriers for the widest range of disabilities. | Government, banking, e-commerce, and any business targeting compliance. | Colour contrast ratio 4.5:1, text resize to 200%, visible focus indicators, captions on video |
| Level AAA | Highest standard. Covers edge cases and provides the best possible experience. | Specialised sites serving disability communities, government accessibility showcases. | Contrast ratio 7:1, sign language for video, reading level grade 9 or below, no time limits |
Target WCAG 2.2 Level AA. That's the sweet spot — legally defensible, covers the vast majority of users, and achievable without unreasonable cost. Level A alone isn't enough. Level AAA is aspirational for most commercial websites.
Quick Accessibility Audit: A Self-Check
Before you hire anyone, run through this checklist on your own website. You don't need tools for most of these — just a keyboard, your browser, and 30 minutes.
Accessibility Self-Audit Checklist
- ☐ Keyboard navigation: Put your mouse away. Can you Tab through every interactive element (links, buttons, forms) and activate them with Enter or Space? Can you see where the focus is at all times?
- ☐ Screen reader test: Turn on VoiceOver (Mac) or NVDA (Windows, free). Navigate your homepage. Does it make sense? Are images described? Are form fields labelled?
- ☐ Zoom test: Zoom your browser to 200%. Does the layout break? Is text still readable? Do elements overlap?
- ☐ Colour contrast: Check your body text and heading colours against their backgrounds. Use the free WebAIM Contrast Checker. Minimum 4.5:1 for normal text, 3:1 for large text.
- ☐ Alt text: Right-click any image → Inspect. Does it have an
altattribute with a meaningful description? Decorative images should havealt=""(empty, not missing). - ☐ Heading structure: Install the HeadingsMap browser extension. Is there exactly one H1? Do headings follow a logical H1 → H2 → H3 hierarchy without skipping levels?
- ☐ Form labels: Click on the text label next to any form input. Does the cursor jump into the input field? If not, the label isn't programmatically associated.
- ☐ Link text: Read your links out of context. Do they make sense? "Click here" and "Read more" fail this test. "View our pricing plans" passes.
- ☐ Video captions: Play any video on your site. Are captions available? Are they accurate (not auto-generated garbage)?
- ☐ Error handling: Submit a form with missing required fields. Does the error message clearly identify which field has the problem and how to fix it?
- ☐ Mobile touch targets: On your phone, try tapping every button and link. Are any too small or too close together?
- ☐ Motion and animation: Does your site respect the
prefers-reduced-motionsystem setting? If a user has motion sensitivity settings enabled, do animations stop?
Scoring: If you failed 3 or more items, your site has significant accessibility barriers. If you failed 6 or more, assistive technology users likely cannot use your site at all.
Making Your Website Accessible: Practical Steps
Here's what to actually fix, in priority order.
1. Alt Text on Every Meaningful Image
Every image that conveys information needs descriptive alt text. Not "image1.jpg". Not "photo". Describe what the image shows and why it matters in context. A product photo needs the product name and key visual details. A team photo needs names or a description of the scene.
Decorative images (backgrounds, dividers, aesthetic flourishes) should have empty alt attributes: alt="". This tells screen readers to skip them.
2. Heading Structure
One H1 per page (your page title). H2s for major sections. H3s for subsections within those. Never skip levels (no jumping from H2 to H4). Never use headings for visual styling — if you want big bold text that isn't a heading, use CSS.
3. Colour Contrast
Body text: minimum 4.5:1 contrast ratio against its background. Large text (18px+ bold or 24px+ regular): minimum 3:1. UI components and graphical objects: minimum 3:1.
The most common failure: light grey text on white backgrounds. It looks "clean" to designers but is unreadable for millions of users. Dark mode helps but isn't a substitute — both modes need to pass contrast checks.
4. Keyboard Navigation
Every interactive element must be reachable and operable with a keyboard alone. The Tab key should move focus in a logical order. Focus must be visible — a clear outline or highlight around the currently focused element. Never remove focus outlines in CSS without providing an alternative.
Common failures: custom dropdown menus that don't respond to arrow keys, modal dialogs that trap keyboard focus, skip-to-content links that are missing or broken.
5. Form Labels and Error Messages
Every form input needs a programmatically associated label using the <label> element with a for attribute matching the input's id. Placeholder text is not a label — it disappears when the user starts typing.
Error messages must identify the specific field with the error, describe what's wrong, and suggest how to fix it. "Please fill in all required fields" is not helpful. "Email address is required — please enter a valid email address" is.
6. ARIA Landmarks and Roles
Use semantic HTML first: <nav>, <main>, <header>, <footer>, <article>, <aside>. These automatically create ARIA landmarks that screen readers use for navigation.
Only add ARIA attributes when HTML semantics aren't sufficient. The first rule of ARIA: don't use ARIA if native HTML will do the job. Misused ARIA is worse than no ARIA — it creates a confusing experience for screen reader users.
7. Captions and Transcripts
All video content needs synchronised captions. Not auto-generated captions — those are roughly 70-80% accurate, which means every fifth word is wrong. Professional captioning or careful editing of auto-generated captions is required.
Audio content (podcasts, voice explanations) needs full text transcripts. This also creates indexable content for SEO — a genuine dual benefit.
Accessibility for Indian Language Sites
India's linguistic diversity creates unique accessibility challenges that most Western-focused guides ignore.
Language declaration: Set the lang attribute correctly on your HTML element (lang="hi" for Hindi, lang="ta" for Tamil, etc.). For multilingual pages, use lang attributes on specific elements where the language changes. Screen readers use this to switch pronunciation rules.
Font rendering: Many Indian language scripts (Devanagari, Bengali, Tamil, Telugu) require specific OpenType features for correct rendering. Test with actual screen readers in the target language — NVDA supports Hindi, and TalkBack on Android supports most Indian languages.
Text resizing: Indian scripts often have more complex character shapes than Latin scripts. Ensure your CSS doesn't break when text is resized to 200%. Avoid fixed-height containers for text content.
Right-to-left support: Urdu and Sindhi use RTL scripts. If you serve these audiences, your layout needs proper RTL support with the dir="rtl" attribute and logical CSS properties (margin-inline-start instead of margin-left).
Transliteration and translation: If you offer content in multiple scripts (e.g., Hindi in Devanagari and Roman transliteration), make the switching mechanism accessible. Don't rely on icon-only buttons — label them clearly.
Tools to Test Accessibility
Free Tools
- axe DevTools (browser extension) — The industry standard. Scans your page and reports WCAG violations with fix suggestions. Catches roughly 30-40% of accessibility issues automatically.
- WAVE (WebAIM) — Visual overlay that highlights accessibility issues directly on your page. Great for non-developers.
- Lighthouse (built into Chrome DevTools) — Includes an accessibility audit score. Limited but useful as a quick health check.
- WebAIM Contrast Checker — Enter foreground and background colours, get instant pass/fail for WCAG AA and AAA.
- HeadingsMap (browser extension) — Visualises your heading structure. Instantly reveals hierarchy problems.
- NVDA (Windows) — Free, open-source screen reader. Essential for manual testing.
- VoiceOver (Mac/iOS) — Built-in screen reader on Apple devices. No installation needed.
- TalkBack (Android) — Built-in screen reader on Android. Important for testing Indian language accessibility.
Paid Tools
- axe Monitor — Automated scanning across your entire site on a schedule. Tracks compliance over time. From $500/year.
- Siteimprove — Enterprise-grade accessibility monitoring with compliance dashboards. Used by large organisations.
- UserWay — Widget-based accessibility layer plus audit tools. Quick fix but not a substitute for proper remediation.
- AudioEye — Combines automated fixes with manual auditing. Higher cost but comprehensive.
- Accessibility Checker by Equally AI — AI-powered scanning with remediation suggestions tailored to your tech stack.
Automated tools catch only 30-40% of accessibility issues. The rest require manual testing — navigating with a keyboard, testing with a screen reader, and checking content quality. Never rely on automated scores alone for compliance claims.
Cost of Accessibility Implementation
Costs in the Indian market, based on real project data:
Accessibility audit (comprehensive): ₹50,000 – ₹2,00,000 depending on site size and complexity. Includes automated scanning, manual testing, and a prioritised remediation report.
Remediation of an existing website: ₹1,00,000 – ₹8,00,000 for a typical 20–50 page business website. Complex web applications (e-commerce, SaaS dashboards) can run ₹5,00,000 – ₹20,00,000+.
Building accessible from scratch: Adds roughly 10-15% to standard development costs. If your website build is budgeted at ₹5,00,000, expect ₹50,000 – ₹75,000 additional for WCAG AA compliance built in from day one.
Ongoing monitoring and maintenance: ₹15,000 – ₹50,000/month for quarterly audits, automated monitoring, and remediation of new issues as content changes.
The cheapest time to make a site accessible is during initial development. Retrofitting costs 3-5x more because you're unpicking decisions made without accessibility in mind.
Accessibility Overlays and Plugins: A Cautionary Note
You've probably seen widgets that promise one-line-of-code accessibility compliance — UserWay, accessiBe, AudioEye overlays. Here's the honest take.
What they actually do: Add a floating toolbar that lets users adjust font size, contrast, cursor size, and similar visual preferences. Some inject ARIA attributes and attempt to fix labelling issues automatically.
What they don't do: Fix structural issues (heading hierarchy, keyboard navigation, missing form labels, proper semantic HTML). They can't fix a fundamentally inaccessible codebase. They often interfere with screen readers rather than helping them.
The accessibility community's position: The National Federation of the Blind (US) and multiple disability advocacy organisations have publicly criticised accessibility overlay products. Several have been subject to lawsuits themselves.
When they're acceptable: As a temporary measure while you're actively remediating your site — not as a permanent solution. They can improve the experience for users with low vision who adjust display settings, but they don't make your site compliant.
Our recommendation: Spend the overlay subscription budget on actual remediation work. Fix the code, not the symptoms.
Maintaining Accessibility Over Time
Accessibility isn't a one-time project. It degrades every time someone adds content, updates a page, or pushes new code. Here's how to keep it intact.
Build it into your content workflow: Train content editors on alt text, heading structure, descriptive link text, and colour contrast. Create a one-page checklist they reference before publishing.
Automate what you can: Add axe-core to your CI/CD pipeline. Every pull request gets an automated accessibility check. This catches regressions before they reach production.
Quarterly manual audits: Automated tools miss 60%+ of issues. Schedule a manual audit every quarter — even a quick 2-hour screen reader walkthrough catches issues that automation misses.
Designate an accessibility owner: Someone on your team needs to own this. It doesn't have to be a full-time role, but without clear ownership, accessibility slides down the priority list after launch.
Test with real users: If your budget allows, include people with disabilities in your user testing. Their feedback reveals issues that no automated tool or sighted tester will find.
Frequently Asked Questions
Is website accessibility legally required for private companies in India?
The RPwD Act 2016 covers ICT accessibility broadly, but enforcement against private companies has been limited so far. However, regulated sectors (banking, insurance, telecom, education) face increasing pressure from sector regulators. The trend is clearly toward mandatory compliance. Building accessibly now is cheaper than retrofitting under legal pressure later.
What WCAG level should I target?
WCAG 2.2 Level AA. It's the globally accepted compliance standard, referenced by the RPwD Act and international regulations (ADA, EAA). Level A alone is insufficient — it misses critical requirements like colour contrast. Level AAA is aspirational and not required for legal compliance in any jurisdiction we're aware of.
How long does it take to make an existing website accessible?
For a typical 20–50 page business website: 4–8 weeks for a full audit and remediation. Complex web applications: 2–6 months. The timeline depends on how many issues exist, the complexity of the codebase, and how much custom interactivity the site has. Static content sites are faster; dynamic applications with custom components take longer.
Can accessibility overlays make my site compliant?
No. Accessibility overlays (like accessiBe, UserWay widgets) provide surface-level adjustments but don't fix structural accessibility issues. They've been criticised by disability advocacy organisations and have failed to prevent lawsuits in the US. Use them as a temporary band-aid while you fix the actual code, not as a permanent solution.
Does making my site accessible hurt the design?
No. This is the most persistent myth in web accessibility. Accessible design constraints — sufficient contrast, clear typography, logical hierarchy, adequate spacing — produce better designs for everyone. Apple, Gov.uk, and Stripe are all WCAG AA compliant and are widely considered among the best-designed sites on the web.
How does accessibility affect my SEO rankings?
Positively. Alt text improves image search visibility. Heading structure helps search engines understand your content hierarchy. Descriptive link text distributes page authority more effectively. Page speed improvements from accessibility work boost Core Web Vitals. Semantic HTML improves crawlability. There is no SEO downside to accessibility — only upside.
What's the first thing I should fix on my website?
Keyboard navigation and alt text. These two fixes address the largest number of users with the least effort. If someone using only a keyboard can navigate your entire site and all images have meaningful descriptions, you've already eliminated the majority of critical accessibility barriers.
Do mobile apps need to be accessible too?
Yes. The RPwD Act covers ICT broadly, which includes mobile applications. Both iOS (VoiceOver) and Android (TalkBack) have built-in screen readers, and users expect apps to work with them. WCAG 2.2 applies to mobile interfaces, and both the Apple App Store and Google Play Store are increasingly enforcing accessibility standards for listed apps.
Want to make your website accessible and compliant? We offer accessibility audits and remediation services for Indian businesses — from quick-win fixes to full WCAG 2.2 AA compliance. Get in touch →