SEBI’s Digital Accessibility Mandate: What It Really Means for Your Platforms

SEBI’s digital accessibility mandate has moved accessibility from a “good-to-have” UX initiative into a clear compliance expectation for regulated entities. It now directly affects how your websites, apps, portals and digital documents are designed, built, tested and maintained. This post breaks down what the mandate really means for your platforms, in practical language.

1. What is SEBI’s digital accessibility mandate?

In recent circulars, SEBI has made it clear that investor‑facing digital platforms must be accessible to persons with disabilities, and that regulated entities are responsible for assessing, fixing and documenting accessibility across their digital estate. In practice, this means your public websites, investor portals, mobile apps, onboarding journeys and documents are expected to align with recognised accessibility standards (like WCAG and IS 17802) and be usable with assistive technologies.

The mandate sits at the intersection of securities regulation and disability rights. On one side is SEBI’s objective: fair, transparent, inclusive markets where investors can actually use digital channels without barriers. On the other side are obligations under the Rights of Persons with Disabilities (RPwD) Act, which already requires equal and barrier‑free access to information and communication technologies. SEBI’s step is to translate that into specific expectations for the securities market ecosystem.

2. Which platforms are in scope?

A common misconception is that “this is for our corporate website only.” In reality, the mandate is much broader. Think of any digital touchpoint where an investor or client interacts with you:

Public websites – marketing sites, product pages, FAQs, disclosures, policy pages.
Investor portals and dashboards – portfolio views, transaction history, statements, reports.
Mobile applications – trading apps, advisory apps, onboarding apps.
Onboarding and e‑KYC journeys – account opening, video KYC, agreements, consent flows.
Digital documents – PDFs of statements, offer documents, reports, letters, and downloadable forms.
Support channels – online complaint forms, chatbots, knowledge bases and ticket portals.

If a digital interface is part of how you inform, onboard, transact with or support investors, it’s effectively in scope. Ignoring “back‑office‑looking” screens (like portals and reports) and only fixing the marketing site will leave you exposed.

3. What does “accessible” actually mean here?

Accessibility is not a vague idea like “easy to use” or “nice design.” In the context of SEBI and RPwD, it usually refers to conforming to technical standards such as:

WCAG 2.x (Web Content Accessibility Guidelines) – global guidelines that define success criteria like minimum colour contrast, keyboard access, text alternatives for images, structure, error handling, etc.
IS 17802 and related Indian standards – India’s digital accessibility standard that adapts global practices to the Indian context.
GIGW-style principles – guidelines for Indian web and app design, emphasising accessibility and inclusiveness.

Applied to your platform, “accessible” typically means:

Text is readable with sufficient contrast and size.
All interactive elements can be used via keyboard, not just mouse or touch.
Screen readers can correctly understand and announce your content and controls.
Images, icons and media have proper text alternatives or captions where needed.
Forms are labelled, error messages are clear and focus is managed correctly.
Layout and code structure are logical, with meaningful headings and landmarks.
Timeouts, animations and auto‑updating content are handled in a user‑friendly way.

The key shift is that accessibility is now measurable. You can test your platforms against these criteria and identify specific pass/fail issues, rather than treating accessibility as a purely subjective goal.

The real message of SEBI’s digital accessibility mandate is not “add a few alt tags and move on.” It’s that accessibility is now a core part of how regulated entities are expected to design and operate digital channels. Those who treat it as a structured, ongoing practice – rather than a one‑off compliance tick – will be better positioned not just to satisfy regulators, but also to offer more inclusive, robust and trusted digital experiences to all investors.

4. What is SEBI expecting from you in practice?

While the exact wording of circulars is legalistic, the expectations are straightforward when translated into steps:

Map your digital estate
You should know which websites, apps, portals, journeys and documents are investor‑facing and therefore in scope. Many organisations discover that they have far more touchpoints than they initially thought.
Conduct a formal accessibility assessment
This involves structured testing of your key platforms against recognised standards. It should combine automated checks with manual testing and, ideally, limited assistive technology testing. The output is an issue list and a report – not just a generic “pass/fail” statement.
Prioritise and remediate issues
You’re expected to actually fix the problems, not just document them. High‑impact barriers (like non‑keyboard‑accessible menus, unreadable text, broken forms) should be addressed first, followed by broader improvements.
Re‑test and validate
After remediation, you should re‑test affected areas to verify that issues have been resolved and that no new barriers have been introduced. This validation stage is crucial for demonstrating progress and readiness.
Maintain evidence and documentation
You’ll need audit reports, remediation logs, platform‑wise status summaries, and supporting documents that show what was tested, what was found, what was fixed, and what remains. These become part of your compliance record.
Engage qualified / certified professionals where required
SEBI has signalled that independent accessibility audits should be carried out by qualified professionals (for example, IAAP‑certified), and that entities should be able to show that competent experts were involved.

Seen this way, the mandate is effectively asking you to run a mini‑programme: discover → audit → fix → validate → document.

5. What does it change for technology and product teams?

For technology, design and product teams, SEBI’s digital accessibility mandate changes expectations in several ways:

Accessibility is now a non‑functional requirement, like security or performance – not an afterthought. New features should be built with accessibility in mind from the start, not “fixed later.”
Design systems and components must be accessible by default. If your component library (menus, buttons, cards, tables, modals) is accessible, every screen built with it benefits. If it’s not, every screen carries risk.
Development workflows need accessibility gates. This could mean accessibility checklists in pull requests, automated tests as part of CI/CD, or manual checks for critical user journeys before release.
Content teams must write and publish with accessibility in mind. That means headings, alt text, link wording, PDFs, and plain language for important investor communications.
Vendors and agencies must be aligned. If you outsource web/app work, your contracts and briefs should include accessibility requirements. Otherwise, third‑party work may undermine your compliance efforts.

In other words, compliance is not just a one‑time “project” but an ongoing way of working.

6. What are the risks of ignoring it?

There are three main risk layers if you treat accessibility as optional:

Regulatory risk
Non‑compliance with SEBI directions can trigger inspections, show‑cause notices, and supervisory actions. If investors complain about inaccessible platforms, those complaints can become part of your supervisory history.
Legal and rights‑based risk
Under the RPwD Act and related frameworks, denial of equal access can lead to complaints and directions from disability commissioners or courts. Accessibility cases globally have increasingly targeted financial institutions.
Business and reputational risk
Accessibility barriers can lead to investor frustration, increased support load, and lost business, especially among senior or differently‑abled investors who may rely more on digital channels. Being seen as non‑inclusive is also reputationally risky in an ESG‑conscious environment.

From SEBI’s perspective, digital accessibility is part of investor protection. From yours, it’s about managing risk and improving user experience at the same time.

7. What should you do next?

If you haven’t started yet, a practical approach is:

Inventory your platforms – list websites, apps, investor portals, onboarding flows, and key document types.
Run a scoped audit – start with your most critical investor touchpoints, not everything at once.
Create a remediation plan – sequence changes over sprints, focusing on high‑impact barriers first.
Embed accessibility into your workflows – update design guidelines, coding standards, QA checklists, and vendor contracts.
Plan for periodic review – set a cadence (for example annual or semi‑annual) for re‑testing and updating your documentation.