When SEBI first announced its digital accessibility requirements for regulated entities, many organisations had the same reaction: “We understand this is important, but what exactly do we have to do, by when, and how deep do we go?” The 2025 clarification circulars were issued precisely to answer those questions. They don’t change the direction of the mandate; instead, they sharpen it, remove ambiguity, and set more concrete expectations.
In this post, we’ll walk through the main takeaways from those clarifications and what they really mean for your websites, apps, portals and digital documents.
July 31, 2025 – SEBI Core Digital Accessibility Circular
This is the main SEBI circular that makes digital accessibility mandatory for all regulated entities under the RPwD Act and related standards.
September 25, 2025 – SEBI Compliance Guidelines for Digital Accessibility
This circular provides detailed compliance guidelines and timelines for implementing the July circular.
December 08/10, 2025 – SEBI’s clarification on Digital Accessibility Circulars
This is SEBI’s clarification / consolidation circular, revising some timelines and explaining requirements in more detail.
1. Accessibility is a defined, ongoing compliance obligation
One of the most important messages in the 2025 clarifications is that digital accessibility is not a one‑time project. It is an ongoing compliance obligation, just like cybersecurity controls or investor grievance redressal. SEBI emphasises that accessibility must be built into how regulated entities design, develop, test and maintain their digital platforms.
Know more about SEBI’s Digital Accessibility Mandate and What It Really Means for Your Platforms for Digital Testing.
That has two implications. First, you cannot simply run a single audit, fix a few issues and then declare yourself “done”. SEBI expects you to have a process: periodic assessments, remediation cycles, and continuous improvement. Second, responsibility for accessibility cannot sit with a single enthusiastic individual. It has to be embedded in your governance – in product decisions, IT change management, content publishing, vendor contracts and internal audits.
2. Scope is broader than “website only”
The clarifications make it clear that SEBI is not talking only about your public marketing website. The scope covers all investor‑facing digital platforms and journeys. This includes:
-
Public corporate and product websites
-
Investor portals and dashboards
-
Online trading and transaction interfaces
-
Mobile apps used by investors and clients
-
Onboarding and e‑KYC / video KYC journeys
-
Self‑service and complaint portals
-
Downloadable documents such as PDFs, statements and forms
If a digital interface is part of how you inform, onboard, transact with or support investors, SEBI expects it to be accessible. For many organisations this is the biggest shift: they realise they must look beyond the “pretty” front page and into the deeper transactional flows they’ve historically treated as pure IT assets.
3. Use recognised accessibility standards, not ad‑hoc checklists
The 2025 clarifications emphasise that accessibility should be assessed against recognised technical standards, not arbitrary or vendor‑specific checklists. While SEBI does not attempt to rewrite WCAG or IS 17802, it clearly points entities towards:
-
Web Content Accessibility Guidelines (WCAG 2.x level AA or later)
-
Indian standards for digital accessibility (such as IS 17802)
-
Relevant government guidelines (for example, GIGW‑style principles)
The main message is: don’t invent your own definition of “accessible”. Use frameworks that are globally and nationally accepted, and map your testing and remediation work to those criteria. This not only improves quality, it also makes your evidence and reports more defensible in front of regulators, internal audit and disability commissioners.
The real takeaway from SEBI’s 2025 digital accessibility clarifications is simple: accessibility is now an expected part of how regulated entities design and operate digital platforms. It is not only about avoiding penalties; it’s about building inclusive, robust and trustworthy digital experiences that serve all investors – including those with disabilities.
The entities that move early and treat accessibility as a strategic capability, rather than a compliance chore, will be in the strongest position as expectations continue to evolve.
4. Formal audits and qualified professionals are expected
Another key clarification is around who should be assessing accessibility. SEBI goes beyond saying “test your platforms” and strongly indicates that formal audits should be carried out by qualified accessibility professionals—for example, those holding recognised certifications, with demonstrable expertise in auditing complex digital systems.
This doesn’t mean your internal QA or UX teams are irrelevant; on the contrary, they play a crucial role in ongoing testing. But for regulatory purposes, SEBI signals that there must be independent, expert-level review at defined intervals. Many entities interpret this as engaging IAAP‑certified accessibility auditors or specialist firms who can:
-
Perform structured audits
-
Provide detailed, traceable issue reports
-
Stand behind their findings if questions arise from regulators or internal stakeholders
The clarifications also encourage entities to avoid “check the box” audits that generate a generic pass/fail certificate without meaningful detail.
Meet our team of SEBI & IAAP audit specialists.
5. Prioritisation and remediation planning are part of compliance
SEBI’s clarifications don’t expect entities to achieve perfection overnight, especially if they have large legacy systems. Instead, the focus is on structured prioritisation and credible remediation planning.
Key ideas include:
-
Classifying issues by severity and impact on users with disabilities
-
Fixing blocking barriers in critical journeys (login, onboarding, trading, payments, statements) before cosmetic issues
-
Documenting decisions: what will be fixed now, what will be deferred, and why
-
Ensuring accessibility requirements are integrated into upcoming redesigns and projects
The takeaway is that a clear, documented remediation roadmap is better than chaotic ad‑hoc fixes. Regulators will often be more comfortable with an honest, prioritised plan than with superficial claims of full compliance.
6. Re‑testing and validation are not optional
A subtle but important point in the clarifications is the emphasis on re‑testing after remediation. Fixing code is only half the story; you need to confirm that:
-
the specific issues flagged in the audit are actually resolved
-
the fixes have not introduced new accessibility barriers elsewhere
-
the overall user experience for people with disabilities has improved in practice
SEBI’s guidance points towards a lifecycle approach: audit → remediation → re‑testing → updated status. Entities are encouraged to maintain “before and after” evidence, including screenshots, code references and test results. For larger platforms, this re‑testing may be done by a mix of the original auditors, internal teams and additional tools.
7. Documentation and evidence are central
From a compliance perspective, documentation is as important as the work itself. The clarifications emphasise the need for entities to maintain:
-
Audit reports and issue logs
-
Remediation plans and status trackers
-
Records of fixes implemented (for example, change tickets, code merges)
-
Re‑test results or validation reports
-
Platform‑wise summaries of accessibility readiness
This documentation is crucial for internal audit, board oversight, and any regulatory queries. It allows you to demonstrate not just that you care about accessibility, but that you have a structured, traceable process. Without records, even good work can appear invisible.
8. Governance: accessibility must be owned, not just assigned
The 2025 clarifications also touch on governance. While they avoid prescriptive structures, they signal that entities should:
-
Assign clear ownership for digital accessibility (for example, a function or committee)
-
Integrate accessibility into broader SEBI compliance frameworks
-
Ensure cross‑functional participation from compliance, IT, product, design, content and operations
-
Build accessibility into policies, procedures and training
The key idea is that accessibility should not be an informal side project. It should have sponsors, roles, responsibilities and escalation paths, like any other material compliance area.
9. Vendor and third‑party considerations
Many regulated entities rely on vendors for their websites, apps, portals or document production. SEBI’s clarifications implicitly highlight that outsourcing does not outsources accountability. You remain responsible for the accessibility of investor‑facing systems, even if they are built or hosted by third parties.
Practically, this means:
-
Including accessibility requirements and standards in RFPs and contracts
-
Asking vendors for evidence of accessibility testing and remediation
-
Coordinating audits that include third‑party components
-
Avoiding “black box” solutions where you cannot influence accessibility fixes
Accessibility has to become a standard negotiation and due‑diligence point with vendors.
10. What should regulated entities do now?
Taken together, the 2025 clarifications paint a clear picture of where SEBI expects the industry to go. For most organisations, a realistic action plan looks like this:
-
Inventory platforms and journeys – list websites, apps, portals, key processes and document types that are investor‑facing.
-
Engage qualified auditors – plan a scoped accessibility audit for your most critical assets first.
-
Create a remediation roadmap – prioritise issues, align with release cycles, and secure budgets.
-
Embed accessibility into workflows – update design guidelines, dev standards, QA checklists and vendor requirements.
-
Set up governance and reporting – define owners, cadence of reviews, and documentation formats.
-
Plan periodic re‑testing – treat accessibility like security: something you revisit regularly, not once.

Leave a Reply