Website Designer in Pune: What India's IS 17802 Accessibility Standard Means for Your Website in 2026
IS 17802 is India's own national standard for web accessibility, built on the same foundation as WCAG 2.1 Level AA — the internationally recognised benchmark for making websites usable by people with visual, hearing, motor, or cognitive disabilities. It already governs government websites, public sector undertakings, and, as of 2025-2026, every SEBI-regulated financial entity in the country. If you're briefing a website designer in Pune for a new build or a redesign in 2026, this is no longer a niche compliance topic reserved for banks and brokers — it has quietly become the working definition of "a properly built website" in India, and understanding it will change what you ask for and what you accept as finished work.
What IS 17802 Actually Is
IS 17802 was published by the Bureau of Indian Standards as the country's formal accessibility standard for information and communication technology products, including websites and mobile applications. It doesn't invent a new rulebook from scratch — it maps closely onto WCAG 2.1 AA, the same success criteria that accessibility professionals worldwide already test against, and it's meant to work alongside the older Guidelines for Indian Government Websites (GIGW) framework and the Rights of Persons with Disabilities (RPwD) Act, 2016, which gives disabled citizens a legal right to accessible information and services (Deque, "Digital Accessibility Laws in India").
In practice, that means IS 17802 is less a brand-new checklist and more a formal, India-specific stamp on standards your website designer in Pune should already be building toward. Government departments, PSUs, and regulated financial platforms don't get to treat it as optional; everyone else currently sits outside its direct legal reach, but the standard itself has become the reference point regulators, auditors, and increasingly clients cite when they ask "is this website accessible?"
Why 2026 Is the Year This Stopped Being Theoretical
For most of its life, IS 17802 sat in the background as a standard mainly discussed by government IT departments and accessibility consultants. That changed when the Securities and Exchange Board of India (SEBI) issued a digital accessibility circular directing every SEBI-regulated entity — stockbrokers, investment advisors, research analysts, mutual fund platforms, and other listed or regulated intermediaries — to bring their public-facing digital properties into line with IS 17802, WCAG 2.1/2.2 AA, GIGW alignment, and the RPwD Act (BarrierBreak, "SEBI Digital Accessibility Readiness Guide"; Digitala11y, "SEBI Mandates Digital Accessibility Across All Regulated Platforms"). The scope isn't limited to the homepage either — it explicitly covers websites, mobile apps, investor portals, trading platforms, disclosure documents, and multimedia content.
This matters even if your business has nothing to do with securities, because it's the clearest signal yet of where an Indian regulator lands when it decides to enforce accessibility with real deadlines, named audit standards, and reporting obligations. It's reasonable to expect that other regulated sectors will eventually look at the SEBI template when they consider their own digital accessibility rules — though that is an inference based on how Indian regulatory frameworks have tended to spread, not a confirmed or scheduled expansion, and nothing here should be read as claiming IS 17802 is currently mandatory outside government bodies, PSUs, banks, and SEBI-regulated entities.
The Actual SEBI Compliance Timeline
What makes the SEBI circular genuinely useful to study — even if you'll never file a compliance report with SEBI — is that it lays out, in unusually concrete terms, what "doing accessibility properly" looks like as a project, not just a design opinion. The published timeline runs roughly like this (Pivotal Accessibility, "A Chronological Guide to SEBI's Digital Accessibility Circulars"; Deque, "SEBI Sets a New Standard for Digital Accessibility in Finance in India"):
- By September 2025: regulated entities had to submit an inventory of every platform in scope — every website, app, and portal that needed to be assessed.
- By December 2025: each entity had to appoint an accessibility auditor.
- By 31 March 2026: a readiness report was due, essentially a self-assessment of where each platform stood against the standard.
- By 30 April 2026: full accessibility audits had to be completed — and crucially, SEBI requires these audits to be carried out by an auditor certified by the International Association of Accessibility Professionals (IAAP), not just anyone who claims accessibility expertise.
- By 31 July 2026: all issues identified in those audits had to be remediated — not just documented, but actually fixed.
- By 30 April 2027: a final compliance report is due, closing the loop on the whole process.
Read as a project plan rather than a legal notice, this timeline tells you something practical: proper accessibility work is inventory, audit, fix, and re-verify — not a single afternoon spent running an automated scanner. If your website designer in Pune proposes to "make the site WCAG compliant" as a single line item with no audit stage and no re-test, it's worth asking what part of that four-stage process they're actually planning to skip.
What IS 17802 / WCAG 2.1 AA Actually Requires on a Real Website
Talking about "accessibility standards" in the abstract is where a lot of client conversations go vague. What the standard actually asks for is specific and testable. A website designer in Pune working to WCAG 2.1 AA (and therefore IS 17802) should be able to walk you through each of the following on your own site, not just cite the standard's name.
Colour Contrast
Body text needs a contrast ratio of at least 4.5:1 against its background, and large text (roughly 18pt or 14pt bold and above) needs at least 3:1. This is the single most commonly failed criterion on Indian business websites, largely because light-grey text on white backgrounds and low-contrast brand colours look "clean" in a mockup but are genuinely unreadable for users with low vision. There's a growing set of CSS tools that make this easier to get right by construction rather than by manual checking after the fact — our companion piece on new CSS baseline features for 2026 covers contrast-color(), a function that lets the browser pick an accessible text colour automatically against any background you set.
Keyboard Navigation
Every interactive element — links, buttons, form fields, menus, sliders, modal dialogs — must be operable using only a keyboard, in a logical order, with no keyboard traps that leave a user stuck inside a widget. This matters for users with motor disabilities who can't use a mouse, and also for screen-reader users, who navigate primarily by keyboard regardless of any visual pointer.
Visible Focus Indicators
When a user tabs to a link, button, or field, there must be a visible outline or highlight showing exactly where focus currently sits. Many modern designs strip this out with outline: none for aesthetic reasons and never replace it with an equally visible alternative — which quietly breaks the site for keyboard users even though it looks fine to everyone clicking with a mouse.
Alt Text on Meaningful Images
Every image that conveys information needs a text alternative that a screen reader can announce; purely decorative images should be explicitly marked so screen readers skip them instead of reading out meaningless filenames. This is a basic requirement that's cheap to implement correctly during a build and expensive to retrofit across hundreds of pages later.
Form Labels and Error Messages
Every form field needs a programmatically associated label (not just placeholder text, which disappears once a user starts typing and isn't reliably read by all assistive technology). Error messages need to identify which field failed and why, in text that's actually associated with that field — not just a colour change or an icon that a screen-reader user can't perceive.
Captions and Transcripts on Video and Audio
Pre-recorded video needs captions, and audio-only content needs a text transcript, so that deaf and hard-of-hearing users can access the same information as anyone else. This one is frequently overlooked on Indian corporate and NGO sites that embed explainer videos or recorded webinars without any caption track at all.
Skip Links and Logical Heading Structure
A "skip to main content" link at the top of the page lets keyboard and screen-reader users bypass repeated navigation menus instead of tabbing through the same header on every single page. Alongside that, headings need to follow a logical, nested order (one H1, then H2s, then H3s beneath the relevant H2) so that screen-reader users can jump between sections the way sighted users scan a page visually.
None of this is exotic. It overlaps heavily with plain good front-end practice, and much of it is also what pushes a site's Core Web Vitals and general usability scores up — we go into that overlap in more depth in our piece on Core Web Vitals and accessibility for website designers in Pune, since the two are far more connected than most briefs treat them.
A Practical Audit Checklist Your Website Designer in Pune Should Walk You Through
If you're not SEBI-regulated and have no legal deadline hanging over you, you still don't need to treat accessibility as an abstract ideal. A competent website design and development partner should be able to sit with you and go through a checklist like this one, page by page, on your actual site — not in a generic slide deck.
Step 1: Automated Scan First
Run an automated accessibility scanner (there are several free browser-based tools) across your key pages — home, contact, product or service pages, any forms. Automated tools typically catch 30-40% of WCAG issues reliably: missing alt text, missing form labels, insufficient contrast, missing page language attributes. This is the fast, cheap first pass, not the whole audit.
Step 2: Manual Keyboard Walkthrough
Unplug the mouse and try to complete your site's most important task — filling a contact form, submitting a donation, adding something to a cart — using only Tab, Shift+Tab, Enter, and arrow keys. If you get stuck, lose track of where focus is, or can't reach a menu item, that's exactly the kind of failure an automated scanner will miss but a real user will hit immediately.
Step 3: Screen Reader Spot-Check
Turn on a screen reader (built into both Windows and macOS at no cost) and navigate your homepage and one form. You don't need to become an expert user overnight — even a rough pass reveals whether images are announced sensibly, whether buttons have meaningful names instead of "click here" or "button," and whether your form errors make sense read aloud with no visual context.
Step 4: Contrast Check on Real Brand Colours
Check your actual brand palette, not a generic template, against the 4.5:1/3:1 thresholds — light brand colours on white or pale backgrounds are the most common failure point for Indian small-business and NGO sites, since brand guidelines are usually set for print or logo use, not for body text on screens.
Step 5: Content Audit for Video, PDFs, and Downloads
List every video, embedded audio clip, and downloadable PDF or document on the site and check whether each one has captions, a transcript, or a tagged, screen-reader-readable structure. This step gets skipped constantly because it sits outside the "webpage" mental model, even though the SEBI circular explicitly names disclosures, documents, and multimedia content as in scope.
Step 6: Fix, Then Re-Test
Treat remediation as its own stage with its own sign-off, mirroring the SEBI timeline's separation of "audit completed" (30 April 2026) from "issues remediated" (31 July 2026). A fix that isn't re-tested against the same checklist is a fix nobody has actually verified.
Who Should Care Even Without a Legal Mandate
It's worth being precise here rather than alarmist: IS 17802 does not currently carry direct legal force over every Indian business. The SEBI circular binds SEBI-regulated entities specifically — brokers, advisors, research analysts, and regulated platforms — with named deadlines running through 2027. If you run a manufacturing company, a services business, a school, or an NGO with no SEBI relationship, nothing in that circular applies to you today.
That said, three practical reasons make this worth acting on ahead of any mandate reaching your sector. First, it's now the concrete standard India's own market regulator points to when it wants a website to be usable by everyone, which makes it a credible reference point for any client, funder, or partner who asks about your site's accessibility, whether or not they can enforce it. Second, the overlap between accessible design and general site quality is real and immediate: proper heading structure, labelled forms, and fast, keyboard-operable interfaces tend to score better on both usability and technical SEO, and a search-engine-optimisation strategy built on a site that's genuinely easy to navigate has less friction to fight against than one bolted onto a hard-to-use interface. Third, retrofitting accessibility later — after years of pages, templates, and third-party plugins have accumulated — is markedly more expensive than building it in from the first sprint, which is exactly the lesson the SEBI timeline demonstrates at scale: inventory, audit, remediate, and re-verify is a multi-month process even for entities that started with dedicated compliance budgets.
NGOs deserve a specific mention here. Fundraising and donation platforms serve an unusually wide range of visitors — older donors, visitors on assistive technology, and people accessing the site from a wide range of devices and connection speeds — and an inaccessible donation form is a direct, measurable loss of donations, not just a compliance gap.
Frequently Asked Questions
Does IS 17802 legally apply to my business if I'm not SEBI-regulated?
Not directly, in most cases. IS 17802 is currently binding on government bodies, public sector undertakings, banks and other explicitly regulated sectors, and — since the 2025-2026 circular — on SEBI-regulated financial entities specifically. If your business sits outside those categories, there's no direct legal requirement to comply with IS 17802 today. It's still worth treating as the practical benchmark, since it reflects where Indian regulators have set the bar and overlaps heavily with good usability and SEO practice, but you shouldn't be told it's already mandatory for every website in India, because it isn't.
Is IS 17802 different from WCAG, or basically the same thing?
They're closely aligned rather than identical. WCAG 2.1 AA is the international standard, developed by the World Wide Web Consortium and used worldwide as the reference for accessible digital content. IS 17802 is India's own Bureau of Indian Standards publication, built on that same WCAG 2.1 AA foundation and intended to work alongside India-specific frameworks like the Guidelines for Indian Government Websites and the RPwD Act. In practice, a site built to WCAG 2.1 AA standards will satisfy the bulk of what IS 17802 asks for, since the underlying success criteria are the same set of testable rules.
What happens if a SEBI-regulated entity misses the compliance deadlines?
The circular lays out a defined sequence of deadlines running from the September 2025 platform inventory through the final compliance report due 30 April 2027, with audits, remediation, and reporting obligations at each stage. Missing a milestone puts an entity out of step with a regulatory circular from its own market regulator, which is the kind of gap SEBI-regulated firms generally treat seriously given their existing compliance relationship with the regulator. The specific penalties or enforcement mechanics for non-compliance sit with SEBI's own regulatory processes, so any entity in scope should confirm current obligations directly with their compliance team or auditor rather than relying on a general summary.
Can an existing WordPress or custom-coded website be retrofitted for WCAG 2.1 AA / IS 17802, or does it need a full rebuild?
Retrofitting is usually possible and is what most organisations actually do, rather than rebuilding from scratch. The practical difficulty depends on how the existing site was built: a WordPress site using a well-structured, actively maintained theme and standard blocks can often reach a large share of WCAG 2.1 AA compliance through targeted fixes — contrast adjustments, alt text, form labelling, focus styles — without touching the underlying architecture. A custom-coded site with deeply nested custom components, especially interactive widgets like carousels, tabbed panels, or custom dropdowns built without accessibility in mind, tends to need more substantial component-level rework, because keyboard and screen-reader behaviour for custom interactive elements has to be coded deliberately rather than inherited from standard HTML. Either way, an audit before you start tells you which of those two situations you're actually in.
Does this standard also cover PDFs and videos on a website, or just the web pages themselves?
It covers more than the HTML pages. The SEBI circular explicitly lists disclosures, documents, and multimedia content alongside websites, apps, and portals as being in scope, and WCAG 2.1 AA more broadly expects that downloadable documents and embedded media meet the same accessibility bar as the page hosting them — meaning PDFs need proper tagging and reading order for screen readers, and videos need captions (with transcripts for audio-only content). A site that passes an accessibility check on its HTML pages but hosts untagged PDF brochures or uncaptioned video content hasn't actually met the standard; both need to be included in any real audit.
Where to Go From Here
If you're planning a new site or a redesign in 2026, the practical move is to raise accessibility with your website designer in Pune at the brief stage, not as an afterthought once the design is signed off — Govindani Infotech Pvt. Ltd. builds every website design and development project with WCAG-aligned structure, contrast, and keyboard behaviour from the first template rather than bolting it on afterward, and pairs that with SEO work that benefits directly from the same clean heading structure and fast, navigable interface that accessibility requires. This is especially relevant if you're building or maintaining an NGO donation platform, given our team's depth of experience — 500+ non-profit websites engineered — in exactly the kind of high-traffic, high-diversity-of-visitor platforms where an inaccessible form costs real donations, not just compliance points; we've covered that donor-side angle specifically in why accessibility is becoming a donor-trust issue for NGO websites. If you want an honest read on where your current site stands against IS 17802 and WCAG 2.1 AA, get in touch through our contact page and we'll walk through it with you directly, at our Parvati Paytha office in Pune or over a call.
Sources:
- Deque — Digital Accessibility Laws in India
- BarrierBreak — SEBI Digital Accessibility Readiness Guide
- Pivotal Accessibility — A Chronological Guide to SEBI's Digital Accessibility Circulars
- Digitala11y — SEBI Mandates Digital Accessibility Across All Regulated Platforms for Financial Industry
- Deque — SEBI Sets a New Standard for Digital Accessibility in Finance in India