Website Accessibility in India: A Practical WCAG Checklist for 2026
Website accessibility means building a site that people with visual, hearing, motor, or cognitive disabilities can actually use — through readable color contrast, full keyboard navigation, screen-reader-friendly markup, and clearly labeled forms. In India, this isn't only a government-website concern: the Rights of Persons with Disabilities Act, 2016 extends the expectation of equitable digital access to private organizations too, and the practical benchmark most sites are measured against is WCAG 2.1 Level AA.
Why Accessibility Matters Beyond Compliance
Accessibility work rarely stays confined to the people it's named for. Alt text and clean heading structure are exactly what search engines parse to understand a page, so accessibility and SEO overlap more than most site owners realize. Captions on video help someone watching with the sound off in a waiting room as much as they help a hearing-impaired visitor. Higher color contrast helps everyone reading a phone screen outdoors in bright sunlight, not only someone with low vision. Building accessibly tends to make a site better for the whole audience, not a separate group within it.
One caveat worth stating plainly: this article is general information, not legal advice. Which specific accessibility obligations apply to a given business is worth confirming with a professional familiar with the Rights of Persons with Disabilities Act rather than relying on a blog post.
The Indian Legal Backdrop, Briefly
The Rights of Persons with Disabilities Act, 2016 sets a broad expectation of equitable access to digital platforms that isn't limited to government bodies. The Guidelines for Indian Government Websites (GIGW) go further for the public sector specifically, mandating WCAG 2.1 Level AA for government websites and apps. Sector regulators have also started formalizing digital accessibility expectations for the entities they oversee. A small business website isn't named directly in most of this, but the direction is consistent enough that WCAG 2.1 AA is a sensible practical bar to build toward, regardless of exactly who is required to today.
A Practical WCAG Checklist for Small Business Websites
Alt text on every meaningful image — describe what the image shows or does, and leave purely decorative images blank rather than stuffed with keywords.
Color contrast — body text should meet at least a 4.5:1 contrast ratio against its background; light grey text on white is a common failure.
Full keyboard navigation — every link, button, and form field should be reachable and usable without a mouse.
Descriptive link text — "view our WhatsApp automation services" tells a screen reader user what a link does; "click here" doesn't.
Proper heading hierarchy — one H1 per page, then H2s and H3s in order, without skipping levels just to make text look a certain size.
Labeled form fields — visible labels on every field, not placeholder text alone, which disappears the moment someone starts typing.
Captions or transcripts — for any video content, so the information doesn't depend on sound.
Text that resizes cleanly — layout shouldn't break when a visitor zooms in to 200%.
Visible focus indicators — a clear outline showing which element is selected when tabbing through a page with a keyboard.
Accessible documents — PDFs and downloads should have real text and structure, not just scanned images of text.
What Checking Your Own Site Actually Involves
A useful accessibility check doesn't need to be elaborate, but it does need more than a glance. Three passes catch most of what matters: an automated scan to flag obvious issues like missing alt text and low contrast, a manual keyboard-only pass through the site's main paths — browsing, filling a form, completing a checkout or booking — to see where a mouse-only design breaks down, and a spot check with a screen reader on the homepage and one or two key pages to hear how the content actually reads aloud. None of the three catches everything alone; together they surface the issues that actually stop someone from completing a task.
How This Overlaps With SEO and GEO
Most of the checklist above isn't a separate workstream from search visibility — it's the same groundwork. Descriptive alt text, a clean heading hierarchy, and well-structured content are what both traditional search engines and AI answer engines like ChatGPT and Perplexity rely on to understand what a page actually says. A site built accessibly tends to arrive already partway toward being well-optimized, which is one reason Arcknet folds accessibility into digital marketing and SEO work rather than treating it as an unrelated checklist.
A Realistic Starting Point
Most small business sites in India weren't built with accessibility in mind, and that's a fixable starting position, not a failure. The checklist above is roughly ordered by what to tackle first: contrast and keyboard navigation affect whether someone can use the site at all, while document accessibility and video captions matter but block fewer people in the meantime. Treating accessibility as an ongoing part of how a site is maintained, alongside speed and security, keeps it from becoming a one-time project that quietly goes stale as new pages get added.
Where to Start If Your Site Isn't There Yet
Retrofitting an entire site at once is rarely realistic, so prioritize by impact: fix navigation, forms, and color contrast first, since those block someone from completing a task at all. Media captions and document accessibility can follow. For anything newly built, it's far cheaper to design it accessibly from the start than to go back and fix it later. Arcknet builds this in by default on new website development projects on Wix Studio, WordPress, or Shopify — if you'd like an honest read on where your current site stands, get in touch.
Comments