WCAG Compliance for Indian Websites: Accessibility Laws and Standards

WCAG compliance in India is no longer a "nice-to-have" checkbox buried in a developer's backlog. With over 2.68 crore persons with disabilities in India and the Rights of Persons with Disabilities Act, 2016 (RPwD Act) mandating accessible information and communication technology, website accessibility has legal teeth. The GIGW Guidelines 3.0, issued by the National Informatics Centre, require every government website to meet WCAG 2.0 Level AA standards. Private businesses face growing pressure too, both from disability rights advocacy and the simple fact that accessible websites convert better. If your website cannot be navigated with a keyboard, read by a screen reader, or understood by someone with a cognitive disability, you are excluding millions of potential users and exposing your organization to legal risk. This guide covers what WCAG requires, which Indian laws apply, what compliance costs, and how to get your website audit-ready.

What is WCAG?

WCAG (Web Content Accessibility Guidelines) is a set of international standards developed by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C). It defines technical criteria for making websites, web applications, and digital content accessible to people with disabilities, including blindness, low vision, deafness, hearing loss, limited movement, speech disabilities, photosensitivity, and cognitive limitations. WCAG is the globally accepted benchmark, referenced by accessibility laws in over 40 countries.

Think of WCAG as a building code for the internet. Just as physical buildings need ramps, elevators, and Braille signage to be usable by everyone, websites need proper heading structures, alt text, keyboard navigation, and color contrast to serve users who rely on assistive technologies. The difference? A physical ramp is visible. Most WCAG compliance happens in the code, invisible to users who do not need it but absolutely critical for those who do. India's disability rights framework has formally adopted WCAG principles through the GIGW Guidelines, making these technical standards a legal requirement for a large category of websites.

WCAG 2.1 vs WCAG 2.2: What Changed?

WCAG has evolved through three major versions, and the differences between them matter when you are deciding what standard to target. WCAG 2.0 was published in 2008 and remains the baseline referenced by India's GIGW Guidelines. WCAG 2.1, released in June 2018, extended coverage to mobile users, people with low vision, and those with cognitive disabilities. WCAG 2.2, published in October 2023, is the current version. Each new version is backward-compatible, meaning a site that meets WCAG 2.2 also meets 2.1 and 2.0.

Why should you care about the version difference? Because targeting WCAG 2.0 alone leaves gaps that affect a large portion of Indian internet users. Over 75% of Indian web traffic comes from mobile devices. WCAG 2.1's mobile-focused criteria (like Orientation, Reflow, and Target Size) directly address this. WCAG 2.2 goes further by tackling authentication barriers and drag-based interactions that exclude users with motor impairments. If you are building or auditing a website in 2026, target WCAG 2.2 Level AA. It costs the same effort as 2.1 and future-proofs your compliance.

The Four Principles of WCAG (POUR)

Every WCAG success criterion falls under one of four foundational principles. These principles are not technical specifications themselves but rather the organizing framework that makes WCAG work. If your website violates any one of these four principles for any group of users, it fails accessibility regardless of how many individual checkboxes you have ticked. The acronym POUR makes them easy to remember.

1. Perceivable

Information and user interface components must be presentable to users in ways they can perceive. This means content cannot rely on a single sense. A video without captions fails perceivability for deaf users. An image without alt text fails it for blind users. A graph that uses only color to distinguish data series fails it for color-blind users. Perceivable is the most frequently violated principle on Indian websites, primarily because of missing alt text (found on 65% of sites tested by accessibility auditors) and insufficient color contrast ratios.

2. Operable

User interface components and navigation must be operable by all users, regardless of how they interact with the website. The most critical requirement: every function available by mouse must also be available by keyboard. This matters because screen reader users, people with motor disabilities, and power users all rely on keyboard navigation. Dropdown menus that only open on hover, carousels that cannot be paused, and forms that trap keyboard focus are all common operability failures. The WCAG 2.2 addition of Dragging Movements (requiring a single-pointer alternative for every drag action) strengthened this principle further.

3. Understandable

Information and the operation of the user interface must be understandable. This goes beyond just writing in plain language (though that helps). Understandable means the website behaves predictably: navigation is consistent across pages, form errors are identified clearly with suggestions for correction, and the page language is declared in the HTML so screen readers use the correct pronunciation. For Indian websites that serve content in multiple languages, declaring the correct lang attribute is essential. A Hindi page with lang="en" forces the screen reader to attempt English pronunciation of Hindi words, making the entire page unintelligible.

4. Robust

Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies. In practical terms, this means clean, valid HTML, proper use of ARIA attributes, and ensuring that custom JavaScript components expose their state and role to screen readers. A beautifully designed custom dropdown that looks perfect but is invisible to assistive technology violates the Robust principle. As assistive technology evolves, robust code ensures forward compatibility rather than breaking with each browser or screen reader update.

Accessibility Laws in India: The Legal Framework

India's web accessibility obligations come from multiple pieces of legislation. Unlike countries such as the United States (ADA, Section 508) or the European Union (European Accessibility Act), India does not have a single dedicated "website accessibility law." Instead, the obligation is constructed from the RPwD Act 2016, GIGW Guidelines, and supporting provisions in the IT Act 2000 and the Consumer Protection Act 2019. Here is how each piece fits together.

RPwD Act, 2016: Section 46

The Rights of Persons with Disabilities Act, 2016 is the cornerstone of disability rights in India, replacing the older Persons with Disabilities Act, 1995. It recognizes 21 categories of disabilities (up from 7 in the previous Act) and mandates equal access to public services. Section 46 is the provision that directly addresses digital accessibility. It states that all service providers, whether government or private, must provide accessible information and communication technology to persons with disabilities. The Act is administered by the Department of Empowerment of Persons with Disabilities under the Ministry of Social Justice and Empowerment. Enforcement is handled through the Chief Commissioner for Persons with Disabilities (at the central level) and State Commissioners (at the state level). When the Chief Commissioner issues a directive to make a website accessible and the organization fails to comply, Section 89 provides for penalties including fines up to ₹5 lakh and imprisonment up to 2 years for repeat violations.

GIGW Guidelines 3.0

The Guidelines for Indian Government Websites (GIGW), published by the National Informatics Centre (NIC), are the operational standards for all Indian government web portals. Version 3.0, the current edition, mandates WCAG 2.0 Level AA compliance as a baseline, along with requirements for bilingual content (English and Hindi or the relevant state language), standardized navigation, and an accessibility statement on every government website. GIGW is not a law itself but carries enforcement weight because compliance is a prerequisite for government website hosting. NIC audits government websites periodically, and non-compliant sites are flagged for remediation. For the private sector, GIGW serves as a reference standard (the best practice benchmark) even though it does not directly apply.

Information Technology Act, 2000

The IT Act, 2000 does not contain explicit accessibility provisions, but its Section 79 due diligence requirements for intermediaries and digital service providers are increasingly interpreted to include accessibility. Legal experts note that as the definition of "reasonable due diligence" evolves, inaccessible digital platforms may face challenges under the IT Act, particularly when they serve as gatekeepers for essential services like banking, e-commerce, or healthcare. The IT Act also underpins the regulatory framework within which the RPwD Act's digital provisions operate.

Who Must Comply with WCAG in India?

The compliance obligation is clearest for government entities, but the circle of organizations that should be prioritizing WCAG compliance is much wider than most business owners realize. Here is the full breakdown.

If your company is a Private Limited Company bidding for government contracts through the GeM portal, WCAG compliance is not optional. Procurement rules increasingly include accessibility requirements as eligibility criteria. Similarly, if you are registered under Startup India and your product serves government customers, building accessibility in from day one saves costly retrofitting later.

WCAG Conformance Levels: A, AA, and AAA Explained

WCAG organizes its success criteria into three conformance levels, each building on the previous one. Understanding these levels is essential for setting realistic compliance targets. Not every website needs AAA compliance, but every public-facing website should aim for AA. Here is what each level means, how many criteria it contains, and what it looks like in practice.

Level AA is the standard that matters for compliance in India. The GIGW Guidelines reference WCAG 2.0 Level AA. International standards (EU's EN 301 549, US Section 508) also reference Level AA. When your WCAG audit report says "WCAG 2.1 AA compliant," it means you meet all 50 Level A and Level AA success criteria. That is the target for almost every business website, government portal, and e-commerce platform.

A common misconception is that Level A is "good enough." It is not. Level A is the bare minimum that prevents the most severe barriers, but it does not address contrast, resizing, or error handling. A Level A-only website still excludes users with low vision (who need adequate contrast), users with motor impairments (who need sufficient target sizes), and users with cognitive disabilities (who need predictable navigation). If you are going to invest in accessibility, invest in AA. The incremental effort from A to AA is modest compared to going from nothing to A.

How to Make Your Website WCAG Compliant: Step-by-Step

Making an existing website WCAG compliant is a structured process, not a vague goal. The steps below outline the practical workflow that accessibility professionals follow. Whether you are handling this in-house or hiring an external auditor, this sequence ensures nothing gets missed.

1. Conduct an Initial Accessibility Audit: Run automated scans using tools like WAVE, axe DevTools, or Lighthouse to identify the most obvious issues. Document every failure with its WCAG criterion reference (e.g., 1.1.1 Non-text Content). Automated tools catch 30% to 40% of issues, so this is a starting point, not the finish line. Estimated time: 2 to 3 working days for a 50-page site.
2. Perform Manual Expert Testing: A trained accessibility auditor tests the website using keyboard-only navigation, screen readers (NVDA, JAWS), and magnification tools. They check logical reading order, focus management, form usability, and dynamic content behavior. This catches the 60% to 70% of issues that automated tools miss. Estimated time: 5 to 10 working days.
3. Prioritize Issues by Impact: Classify each issue as Critical (blocks access entirely), Major (creates significant barriers), or Minor (causes inconvenience but does not block access). Fix critical issues first. A missing form label on a payment form is critical. A slightly low contrast on a decorative border is minor.
4. Remediate Code Issues: Fix HTML, CSS, and JavaScript to meet WCAG criteria. Common fixes include adding alt text, correcting heading hierarchy, implementing skip navigation links, fixing color contrast ratios, adding ARIA labels to interactive components, and ensuring all forms have associated labels. Estimated time: 15 to 45 working days depending on site complexity.
5. Test with Real Users: If budget allows, conduct usability testing with persons with disabilities. No automated tool or expert review fully replaces the insight of a screen reader user navigating your checkout flow or a user with motor impairments trying to complete a form. Even 3 to 5 user tests reveal issues that audits miss.
6. Update Design System and Templates: Ensure your UI component library, CMS templates, and design system enforce accessibility by default. Accessible components prevent future regressions. If every new page uses an accessible template, compliance becomes automatic rather than an afterthought.
7. Publish an Accessibility Statement: Create a public page declaring your conformance target (e.g., WCAG 2.1 Level AA), known limitations, planned improvements, and a contact method for accessibility feedback. GIGW requires this for government sites. For private businesses, it demonstrates good faith and commitment.
8. Establish Ongoing Monitoring: Accessibility is not a one-time project. New content, updated plugins, and design changes can introduce regressions. Set up automated monitoring (Pa11y CI, axe Monitor) to scan your site weekly. Schedule manual audits every 6 to 12 months.

WCAG Compliance Audit Checklist

Use this checklist as a quick reference before or during your WCAG audit. It covers the most impactful criteria at Level AA, organized by the POUR principles. This is not a replacement for a full audit against all 50 Level AA criteria but rather a practical starting point that catches the issues responsible for 80% of accessibility barriers.

Perceivable Checklist

• All images have descriptive alt text (not "image1.jpg" or blank)
• Videos have synchronized captions
• Audio content has transcripts
• Color contrast ratio is at least 4.5:1 for normal text and 3:1 for large text
• Information is not conveyed by color alone (charts, status indicators)
• Text can be resized to 200% without loss of content or functionality
• Content reflows at 320px width without horizontal scrolling

Operable Checklist

• All interactive elements are keyboard accessible (Tab, Enter, Space, Arrow keys)
• No keyboard traps (user never gets stuck in a component)
• Skip navigation link is present at the top of each page
• Focus indicator is visible on all interactive elements
• Timed content has a pause, stop, or extend mechanism
• Page titles are descriptive and unique for each page
• Touch targets are at least 24x24 CSS pixels (WCAG 2.2)

Understandable Checklist

• Page language is declared in HTML (lang="en" or lang="hi")
• Form inputs have visible labels associated via for attribute
• Error messages identify the field and suggest correction
• Navigation is consistent across pages
• No unexpected changes of context on focus or input

Robust Checklist

• HTML is valid and well-formed (no duplicate IDs, no unclosed tags)
• Custom components use appropriate ARIA roles, states, and properties
• Status messages are announced to screen readers without receiving focus
• All interactive widgets expose their name, role, and value to assistive technology

Most Common Accessibility Issues on Indian Websites

Accessibility audits across Indian websites, both government and private, reveal the same set of recurring issues. The WebAIM Million report (which tests the top one million websites globally) and India-specific studies by the Centre for Internet and Society consistently highlight five issues that account for over 80% of detected accessibility barriers. If your website fixes just these five, you eliminate the majority of obstacles for users with disabilities.

1. Missing or Inadequate Alt Text

Found on 65% of Indian websites tested. Images without alt text are invisible to screen readers. Decorative images should have empty alt attributes (alt=""), while informative images need descriptive text that conveys the image's purpose. A product image with alt="IMG_20240315" is functionally identical to having no alt text at all.

2. Insufficient Color Contrast

Found on 60% of sites. Light gray text on white backgrounds, thin fonts with low contrast, and placeholder text that blends into the background affect users with low vision and anyone using a screen in bright sunlight. The fix is straightforward: ensure 4.5:1 contrast for normal text and 3:1 for large text (18pt or 14pt bold). Free tools like the WebAIM Contrast Checker verify this in seconds.

3. Missing Form Labels

Found on 55% of sites. Forms without properly associated labels force screen reader users to guess what each field expects. A contact form where the screen reader announces "edit text" instead of "Full Name, edit text" is unusable without sighted assistance. Every <input> needs a <label> with a matching for attribute.

4. Empty Links Without Accessible Names

Found on 45% of sites. Social media icon links, hamburger menu buttons, and image links without text alternatives produce "link" or "button" announcements in screen readers, giving users zero information about where the link leads. Every link and button needs either visible text, an aria-label, or a title attribute.

5. Keyboard Inaccessibility

Found on 40% of sites. Custom dropdown menus, modal dialogs, sliders, and tab panels that only respond to mouse events lock out keyboard users entirely. This is the most severe type of accessibility failure because it blocks access to functionality, not just content. Every interactive element must be focusable and operable via keyboard.

Cost of WCAG Compliance in India

Let's talk numbers, because "it depends" does not help you plan a budget. The cost of WCAG compliance varies based on your website's size, technology stack, and current state of accessibility. Here is what Indian businesses typically spend across different scenarios.

For the typical mid-sized business website, expect to spend ₹1.5 lakh to ₹5 lakh for the initial audit and remediation cycle. That covers the expert audit, code fixes, content updates, and team training. Ongoing monitoring adds ₹10,000 to ₹20,000 per month. To put this in perspective, a single non-compliance directive from the Chief Commissioner of Persons with Disabilities can trigger legal costs, reputational damage, and remediation urgency that far exceed the cost of proactive compliance.

Companies pursuing ISO certification (particularly ISO 27001 for information security) find that many of the documentation and process framework requirements overlap with WCAG compliance. If you are already building a management system for ISO, adding accessibility as a component reduces the net cost by 20% to 30%.

Penalties for Non-Compliance in India

India's penalty framework for web accessibility non-compliance is not as straightforward as a fine schedule. Unlike the GDPR (which specifies percentage-of-revenue fines) or the ADA (which allows direct lawsuits for inaccessible websites), India's enforcement mechanism works through the disability rights commission system. Here is how it actually plays out.

Complaint and Directive Mechanism

Any person with a disability, or their representative, can file a complaint with the Chief Commissioner for Persons with Disabilities (CCPD) at the central level or the State Commissioner for Persons with Disabilities at the state level. If the Commissioner finds the complaint valid, they issue a directive to the organization to make its website accessible within a specified timeframe (typically 30 to 90 working days). The organization must comply with this directive or face escalating consequences.

Section 89: Penalties for Non-Compliance with Directives

Under Section 89 of the RPwD Act, 2016, failure to comply with a directive from the Commissioner attracts a fine of up to ₹5 lakh. For repeated or continuing violations, the fine can be compounded. In extreme cases involving willful non-compliance, the Act provides for imprisonment of up to 2 years. While imprisonment for website inaccessibility has not been enforced yet, the legal provision exists and creates real risk for organizations that ignore compliance directives.

Government Procurement Exclusion

Beyond direct penalties, non-compliant organizations can be excluded from government contract bidding. The Government e-Marketplace (GeM) and Central Public Procurement Portal increasingly include accessibility clauses. For IT companies that rely on government contracts (a ₹14,000 crore annual market), losing eligibility because of website inaccessibility is a significant commercial penalty even without a formal fine.

WCAG Compliance and Business Benefits

Accessibility is not just a legal obligation. It is a business advantage that most Indian companies overlook because they see it purely through a compliance lens. Here is what the data shows when companies invest in making their websites accessible.

Larger Addressable Market

India has over 2.68 crore persons with disabilities (Census 2011; the actual number is estimated to be significantly higher). Add to this the elderly population (14.4 crore persons aged 60+), people with temporary impairments (broken arm, eye surgery recovery), and situational limitations (using a phone in bright sunlight, browsing in a noisy environment). An accessible website serves all of these users. Businesses that ignore accessibility are voluntarily shrinking their addressable market.

Improved Conversion Rates

Studies by the Click-Away Pound Survey (UK) and Nucleus Research consistently show that accessible websites achieve 15% to 20% higher conversion rates than inaccessible ones. The reason is straightforward: fixes that help users with disabilities (clearer forms, better contrast, logical navigation, descriptive buttons) also improve usability for everyone. A "Submit" button that only says "Click Here" frustrates all users, not just screen reader users.

SEO Benefits

WCAG compliance and search engine optimization share significant overlap. Proper heading hierarchy helps both screen readers and Google understand content structure. Alt text for images improves both accessibility and image search visibility. Fast-loading, mobile-responsive pages with clean HTML rank better and are more accessible. Google has confirmed that user experience signals (which accessibility directly improves) influence search rankings. If you are investing in SEO for your business, accessibility should be part of that investment, not a separate budget line.

Government Contract Eligibility

As mentioned earlier, government procurement through GeM and CPPP increasingly includes accessibility requirements. An accessible, compliant website positions your business as a responsible vendor and opens doors to the ₹14,000 crore government IT procurement market.

Summary

WCAG compliance in India sits at the intersection of legal obligation, business opportunity, and basic digital ethics. The RPwD Act 2016 Section 46 mandates accessible ICT, the GIGW Guidelines 3.0 require WCAG 2.0 AA for government sites, and private businesses face growing legal and commercial pressure to make their websites accessible. A professional audit costs ₹50,000 to ₹2 lakh, remediation costs ₹1 lakh to ₹5 lakh for mid-sized sites, and the ROI includes a larger addressable market, better conversion rates, and improved search rankings. Start with an automated scan, invest in a manual expert audit, remediate high-impact issues first, and establish ongoing monitoring. If you are building a new website, integrating accessibility from the design phase costs a fraction of retrofitting later. IncorpX's compliance advisory services can help you navigate the audit process, coordinate remediation, and maintain ongoing compliance.