SEBI Digital Accessibility Compliance: A Readiness Guide for Regulated Entities

Most Important Takeaways

SEBI digital accessibility compliance is a legal mandate now

The Supreme Court's April 30, 2025 judgment (Pragya Prasun and Amar Jain v. Union of India) tied digital accessibility to Article 21's right to life. This one ruling is why SEBI moved from guidance to five enforceable circulars in under a year. Any Regulated Entity still treating accessibility as a design task is behind today's legal requirements.

The compliance clock is short and already running

SEBI's compliance roadmap packs several important milestones into about 10 months. Regulated Entities must submit their platform inventory by September 2025, appoint an auditor by December 2025, file the readiness report by March 31, 2026, complete accessibility audits by April 30, 2026, and finish all remediation by July 31, 2026. This leaves only four months between the readiness report and the final remediation deadline. That is a very short period to complete audits, fix accessibility issues, and verify the changes if work has not already begun.

"Scope" is much bigger than most REs initially assume

It's not just the main website. Legacy systems still holding investor data, white-label platforms, and third-party integrations all count and all need to appear in Annexure B with supporting evidence.

Multi-standard compliance is required, not a single checklist

WCAG 2.1/2.2 AA is the floor, but REs also need IS 17802, GIGW, and RPwD Act alignment simultaneously. This affects everything from document tagging (PDF/UA) to KYC verification methods (no blink-only liveness checks) to trading-interface session timeouts.

Governance and cost sit entirely with the RE

A Nodal Officer, IAAP-certified auditors, and a SCORES-integrated grievance process are mandatory. SEBI does not subsidize any of it. RE’s should start ensuring they have budgets to conduct accessibility audits considering accessibility is a on-going journey not a one-time project.

SCORES gives SEBI a strong way to enforce accessibility rules

The dedicated "Accessibility" complaint category means individual investors can now trigger regulatory scrutiny directly. Unresolved or repeated complaints can lead to targeted inspections. This is applicable alongside SEBI's broader penalty powers (which can range from daily fines to registration suspension in serious cases). Accessibility complaints are a compliance-risk signal SEBI is actively watching.

1. Scope and applicability

Which organizations are covered under SEBI's digital accessibility framework, and which websites, apps, portals, and KYC systems must comply?

SEBI's digital accessibility compliance framework requires every SEBI Regulated Entity (RE) that offers digital services to investors to ensure those services are accessible to persons with disabilities. The requirements apply broadly across investor-facing digital channels. It covers everything from informational websites to transaction platforms and customer support systems.

Which organizations are considered Regulated Entities (REs)?

The framework covers all SEBI-registered intermediaries as well as Market Infrastructure Institutions (MIIs). These include:

Which investor-facing platforms must comply?

• Public websites and informational web pages
• Mobile applications for both Android and iOS
• Online trading platforms, web-based trading terminals, and market data interfaces
• Investor dashboards and account management portals
• Digital onboarding processes
• e-KYC and Video-KYC systems
• Online forms and application portals
• Customer service tools, including interactive support features
• Investor communications, such as circulars, notices, account statements, terms and conditions, and downloadable PDF documents
• Videos and other multimedia resources provided to investors

What does compliance require?

Regulated Entities must design and maintain these digital platforms in line with recognized accessibility requirements. These include WCAG 2.1, the Guidelines for Indian Government Websites (GIGW), IS 17802 and The Rights of Persons with Disabilities (RPwD) Act, 2016.

• Alternative text for images so screen readers can describe visual content
• Closed captions for video content
• Audio descriptions where visual information needs additional explanation

How do SEBI's digital accessibility circulars support the RPwD Act, 2016, and what extra obligations do they place on financial service providers?

SEBI's digital accessibility circulars put the broad accessibility requirements of the Rights of Persons with Disabilities (RPwD) Act, 2016 into practice for the Indian securities market. The RPwD Act establishes the legal right to equal access and non-discrimination. SEBI's circulars explain how Regulated Entities (REs) must meet those requirements by introducing specific technical standards, governance measures, reporting obligations, and compliance timelines.

How do SEBI's circulars work with the RPwD Act?

The RPwD Act, 2016 provides the legal foundation for digital accessibility. It does this by requiring service providers to offer reasonable accommodation and prevent disability-based discrimination under Sections 40, 42, and 46. However, the Act sets out broad principles rather than detailed implementation requirements.

• Defining clear technical standards for accessibility through recognized frameworks such as WCAG 2.1 Level AA, GIGW 3.0, and IS 17802. This allows Regulated Entities to know exactly what an accessible digital platform should achieve.
• Introducing governance requirements that require Regulated Entities (REs) to establish reporting structures, conduct accessibility audits, and implement formal grievance redressal mechanisms.
• Setting compliance milestones and reporting requirements. This includes Digital Accessibility Readiness and Compliance Status Reporting. It enables accessibility to be monitored, measured, and enforced.

What additional obligations do SEBI's circulars place on financial service providers?

SEBI digital accessibility compliance introduces several operational and technical obligations specific to financial service providers.

1. Platform-wide technical accessibility

• Public websites
• Mobile applications for iOS and Android
• Online trading platforms
• Investment and account management portals
• e-KYC processes

The requirement also covers digital documents. It means materials such as account opening forms, annual reports, and mutual fund offer documents must be made available in accessible formats.

2. Accessible onboarding and e-KYC processes

• e-KYC and Video KYC processes must include built-in alternatives. Examples include human-assisted Video KYC, voice-assisted verification for visually impaired users, or scanned document uploads where appropriate.
• Client registration and KYC forms must include a mandatory field to record disability status. This allows users to choose specific facilitation measures, such as callback support from a helpdesk.
• Applications submitted by persons with disabilities must not be automatically rejected by digital systems. Instead, they must undergo a secondary human review to help prevent systemic discrimination.

3. Accessibility requirements for user interfaces and multimedia

• Alternative text for images
• Closed captions for videos
• Descriptive audio where needed
• Indian Sign Language (ISL) interpretation for explainer videos, including tutorials related to KYC and similar processes

4. Organizational accountability and accessibility audits

SEBI's circulars also introduce governance responsibilities that go beyond the RPwD Act's general obligations. Each Regulated Entity must appoint a designated Nodal Officer. They will be responsible for overseeing accessibility compliance, coordinating accessibility audits, and addressing user complaints related to accessibility.

In addition, organizations must carry out regular accessibility audits. These assessments be conducted by IAAP-certified (International Association of Accessibility Professionals) professionals or other recognized accessibility agencies.

5. Accessibility grievance redressal and escalation

• User-friendly helplines
• Online complaint forms
• Email support channels
• A documented escalation matrix that allows unresolved complaints to be referred to senior officers

Where necessary, accessibility-related complaints can also be escalated through SCORES. It is SEBI's standardized investor grievance redressal platform.

Which investor journeys and touchpoints must be demonstrably accessible under SEBI's mandate?

Under SEBI digital accessibility compliance mandate, Regulated Entities must ensure that every investor-facing digital journey and touchpoint is accessible to persons with disabilities. This means investors should be able to use digital services independently with the help of accessibility features.

The following investor journeys and touchpoints must be demonstrably accessible:

To support these requirements, SEBI requires Regulated Entities to comply with WCAG 2.1 Level AA (Web Content Accessibility Guidelines) and other applicable national standards under the Rights of Persons with Disabilities (RPwD) Act, 2016.

Regulated Entities must also conduct periodic accessibility audits, address identified accessibility issues, and submit Digital Accessibility Readiness and Compliance Status Reports to SEBI. These measures help demonstrate that investor-facing digital platforms remain accessible over time.

2. Regulatory intent and legal basis

How did the Supreme Court's April 30, 2025, judgment on digital accessibility influence SEBI's accessibility requirements for the securities market?

The Supreme Court's April 30, 2025, judgment in Pragya Prasun & Ors. v. Union of India and Amar Jain v. Union of India recognized digital access as part of the right to life and personal liberty under Article 21. This judgment prompted SEBI to establish mandatory digital accessibility obligations across the securities market for persons with disabilities.

• The ruling changed digital accessibility from a voluntary policy objective into a fundamental rights requirement under Article 21.
• This prompted SEBI to align its accessibility framework with the Rights of Persons with Disabilities (RPwD) Act, 2016.
• SEBI introduced platform-wide accessibility requirements covering investor-facing websites, trading applications, and e-KYC systems across Regulated Entities.
• These platforms must comply with recognized accessibility standards, including WCAG 2.1 Level AA and IS 17802.
• SEBI also introduced stronger accountability through accessibility monitoring, audits, and structured compliance reporting by Regulated Entities.
• Regulated Entities must submit Digital Accessibility Readiness & Compliance Status Reports to demonstrate ongoing accessibility compliance.
• SEBI updated its Investor Charters to recognize the Investors' Right to Digital Accessibility as a protected right.
• This change established accessible digital financial services as an entitlement instead of an optional convenience for investors.

How does SEBI treat digital accessibility as an investor protection issue, and what does this mean for compliance and Investor Charters?

SEBI treats digital accessibility as a fundamental investor protection issue. It makes it an essential part of regulatory compliance rather than an optional design improvement. This approach creates a rights-based regulatory governance framework. It requires Regulated Entities (REs) to protect investors' digital access through enforceable obligations.

How does this change the compliance approach?

• SEBI has shifted digital accessibility from an optional User Experience (UX) enhancement to an enforceable rights-based regulatory requirement.
• This approach redefines market integrity by treating digital accessibility as an essential requirement for fair investor participation.
• Platforms incompatible with screen readers or lacking keyboard navigation are now recognized as systemic barriers for persons with disabilities.
• These accessibility barriers are legally treated as obstacles preventing equal participation in India's capital markets.
• Compliance is directly linked to the Rights of Persons with Disabilities (RPwD) Act, 2016, strengthening its legal importance.
• Digital accessibility is no longer a "nice-to-have" interface improvement but a statutory right promoting systemic market fairness.

What does this mean for Investor Charters?

• SEBI's Clarification on the Digital Accessibility Circulars formally adds the "Investors' Right to have digital accessibility" to relevant Investor Charters.
• Including this right makes Regulated Entities explicitly responsible for providing accessible digital services to every investor.
• Investors experiencing accessibility barriers can submit complaints through the SEBI SCORES platform under the dedicated "Accessibility" category.
• These complaints may relate to websites, mobile applications, e-KYC processes, or online trading dashboards used by investors.
• Regulated Entities must resolve identified accessibility barriers before SCORES complaints can be officially closed.

How does SEBI enforce these requirements?

• Regulated Entities must submit Digital Accessibility Readiness and Compliance Status Reports to designated regulatory authorities.
• Initial and annual accessibility audits must evaluate investor-facing digital platforms against WCAG 2.1/2.2 AA and IS 17802.
• SEBI also enforces strict post-audit remediation timelines for correcting identified accessibility barriers across regulated digital platforms.
• This ensures digital accessibility remains an ongoing compliance responsibility and not a one-time implementation exercise.

3. Chronology of SEBI circulars

What are the five SEBI digital accessibility circulars issued in 2025? How did each circular expand or clarify the obligations of REs from digital KYC to full‑stack accessibility?

During 2025, SEBI issued five key circulars that gradually expanded accessibility obligations for Regulated Entities (REs). The framework evolved from ensuring accessible digital KYC to requiring full-stack digital accessibility across all investor-facing digital platforms.

The five SEBI digital accessibility circulars issued in 2025

How did the obligations expand from digital KYC to full-stack accessibility?

1. May 2025: Accessible digital KYC

• The first circular required equal access to e-KYC and Video KYC processes for persons with disabilities.
• Regulated Entities had to provide alternative onboarding methods. This includes human-assisted verification and voice-assisted identity verification.
• The framework also required accessible document uploads for investors unable to complete standard digital verification procedures.
• Applications submitted by persons with disabilities required human review before rejection. This prevents discriminatory automated decision-making practices.

2. July to September 2025: Full-stack digital accessibility

• SEBI digital accessibility compliance expanded accessibility requirements beyond KYC to every investor-facing digital platform operated by Regulated Entities.
• The mandate covered public websites, iOS and Android applications, trading platforms, portfolio portals, and digital circulars.
• Accessible PDFs and other investor documents also became mandatory under the expanded digital accessibility framework.
• Regulated Entities had to comply with Web Content Accessibility Guidelines (WCAG) 2.1, IS 17802, and GIGW 3.0.
• Platforms had to support alternative text, closed captions, descriptive audio, and Indian Sign Language (ISL) video interpretation.
• Every Regulated Entity had to appoint a Nodal Officer responsible for overseeing accessibility governance and compliance activities.
• Regulated Entities also had to establish an Accessibility Grievance Redressal Mechanism for accessibility-related investor complaints.
• Accessibility testing had to include participation from persons with disabilities (PwD) to validate real-world platform usability.

3. December 2025: Governance and continuous compliance

• SEBI clarified reporting expectations through Digital Accessibility Readiness and Compliance Status submissions for every platform.
• Accessibility rights were formally incorporated into standard Investor Charters. It strengthened investor protection across regulated financial services.
• Accessibility complaints became integrated with SEBI SCORES, creating a standardized regulatory grievance resolution process for investors.
• Regulated Entities must resolve underlying accessibility barriers before accessibility complaints can be treated as fully addressed.

What new requirements were introduced in the July 2025 circular on mandatory digital accessibility compliance for all REs? How did it shift accessibility from guidance to enforceable regulation?

The July 2025 Securities and Exchange Board of India (SEBI) circular turned digital accessibility into a mandatory regulatory requirement for Regulated Entities (REs). It introduced enforceable compliance obligations, mandatory audits, governance requirements, and reporting responsibilities across all investor-facing digital platforms.

New requirements introduced by the July 2025 circular

• The circular required every investor-facing digital platform to meet mandatory accessibility requirements across all Regulated Entities.
• Accessibility requirements covered public websites, iOS and Android mobile applications, trading platforms, and e-KYC systems.
• All covered platforms had to comply with WCAG 2.1, IS 17802, and GIGW accessibility standards.
• Every Regulated Entity had to appoint a Nodal Officer responsible for overseeing digital accessibility compliance activities.
• Regulated Entities also had to establish formal accessibility grievance redressal mechanisms for investors experiencing digital accessibility barriers.
• The circular introduced mandatory accessibility audits across all investor-facing digital platforms operated by Regulated Entities.
• Accessibility audits had to include usability testing performed by persons with disabilities to validate real-world accessibility outcomes.
• Regulated Entities were also required to submit formal Readiness and Compliance Status Reports to designated authorities.

How did the circular make accessibility enforceable?

• The circular explicitly enforced accessibility obligations under the Rights of Persons with Disabilities (RPwD) Act, 2016.
• This changed digital accessibility from a voluntary practice into a statutory compliance obligation carrying legal responsibility.
• SEBI integrated digital accessibility into its core regulatory framework alongside cybersecurity and investor protection requirements.
• As a result, accessibility became an essential regulatory obligation rather than a standalone technology or design consideration.
• Non-compliance could expose Regulated Entities to regulatory action as well as significant reputational risks.
• The framework also reflected landmark Indian judicial rulings recognizing digital access as part of the Right to Life.
• This strengthened accessibility requirements by firmly positioning digital access as a non-negotiable legal and regulatory right.

How did SEBI's December 8, 2025 clarification circular clarify auditor appointments, reporting, deadlines, and investor rights?

The December 8, 2025 SEBI clarification circular refined the Digital Accessibility Compliance framework for Regulated Entities (REs). Now, it focused on measurable accessibility progress, revised reporting arrangements, updated implementation timelines, and reinforced investor rights.

The circular introduced the following key clarifications:

Auditor appointments

Rather than insisting on appointing IAAP-certified accessibility auditors, SEBI emphasized demonstrating meaningful accessibility progress and a clear commitment to compliance.

Reporting

Instead of requiring completed accessibility audits, Regulated Entities must provide Digital Accessibility Readiness and Compliance Status Reports for every investor-facing platform. The circular also assigned BSE Ltd. as the reporting authority for Investment Advisers (IAs) and Research Analysts (RAs).

Deadlines

SEBI provided additional implementation time by extending the reporting deadline until March 31, 2026. Every investor-facing digital platform must be covered within the initial readiness and status submissions.

Investor rights

The circular formally established "Investors' Right to have digital accessibility" as a recognized investor entitlement. Regulated Entities must now reflect this right across all applicable Investor Charters.

4. Timelines and phased compliance

What are the key dates across SEBI's accessibility roadmap? What deliverables or milestones does each date correspond to in terms of lists of platforms, auditor engagement, readiness reporting, audits, and remediation?

SEBI digital accessibility compliance roadmap follows a phased implementation approach for Regulated Entities (REs). Each milestone focuses on a specific compliance activity. Thus, it helps REs progressively achieve accessibility across investor-facing digital platforms in line with WCAG 2.1, GIGW 3.0, and IS 17802.

September 30, 2025

• Regulated Entities must submit an initial action-taken or compliance report outlining their accessibility implementation progress.
• They must also provide a complete inventory of investor-facing digital platforms, including websites, mobile applications, portals, and e-KYC systems.

December 14, 2025

Key deliverables and milestones:

• Regulated Entities must appoint IAAP-certified accessibility professionals to conduct independent third-party accessibility audits.

March 31, 2026

• Regulated Entities must submit a Digital Accessibility Readiness & Compliance Status Report for every investor-facing digital platform.
• The report must clearly document the accessibility readiness and current compliance status of each covered platform.

April 30, 2026

• Initial accessibility audits must be completed and submitted within the prescribed compliance timeline.
• The audits must assess every covered digital asset, including downloadable documents such as PDFs.

July 31, 2026

• Regulated Entities must remediate all accessibility barriers identified during the accessibility audits.
• They must also achieve full accessibility compliance confirmation by the prescribed remediation deadline.

After completing these milestones, Regulated Entities must continue conducting comprehensive accessibility audits and submit annual accessibility reports every year.

What is expected of REs between the readiness report deadline (March 31, 2026) and the remediation deadline (July 31, 2026)? How should they plan and prioritize activities to avoid last‑minute compliance risks?

Between March 31 and July 31, 2026, Regulated Entities (REs) must move beyond planning and actively achieve digital accessibility compliance. This period focuses on completing audits, implementing remediation measures, validating fixes, and submitting follow-up reports before the final compliance deadline.

Audits (April–May)

• After submitting readiness reports, Regulated Entities must complete comprehensive third-party accessibility audits across all investor-facing digital platforms.
• Audits should thoroughly assess websites, mobile applications, digital channels, and supporting systems to identify outstanding compliance gaps.

Fixes (May–June)

• Regulated Entities must remediate all accessibility issues identified during the audits across affected digital platforms and services.
• Every corrective action should align with applicable accessibility standards, including WCAG Level AA and other relevant compliance requirements.

Validation

• Appointed auditors must re-test completed remediation work to verify previously identified accessibility issues have been successfully resolved.
• This validation confirms that corrective measures effectively address non-compliance before the final compliance reporting stage.

Follow-up reporting

• Regulated Entities must submit Action Taken Reports (ATRs) or revalidation compliance reports through the designated regulatory reporting portal.
• These reports should include the required approvals from management or the IT Committee before regulatory submission.

How should REs prioritize activities to avoid last-minute compliance risks?

• Component-level fixes: Prioritize accessibility improvements within shared design components or core technology frameworks before updating individual pages or systems.
• Rolling deployments: Release accessibility fixes through smaller, scheduled implementation cycles instead of waiting for a single large deployment.
• Auditor coordination: Establish clear Service Level Agreements (SLAs) with auditors to ensure timely re-testing and validation of completed fixes.
• Vendor compliance: Require third-party vendors to deliver compliant updates for integrated APIs, CRMs, and trading tools before deadlines.
• Continuous governance: Treat accessibility as an ongoing governance program supported by automated vulnerability tracking and continuous compliance monitoring.

5. Accessibility standards and technical requirements

Which specific accessibility standards does SEBI reference? How should REs interpret "minimum AA‑level compliance under the latest WCAG standards" in the context of financial platforms?

SEBI digital accessibility compliance requires Regulated Entities (REs) to make all investor-facing digital platforms and communications accessible by complying with WCAG 2.1 (or the latest version) Level AA, GIGW, IS 17802, and the statutory requirements of the Rights of Persons with Disabilities (RPwD) Act, 2016. Together, these standards establish the technical and legal foundation for digital accessibility across the securities market.

Which accessibility standards does SEBI reference?

• WCAG 2.1 / 2.2 Level AA: SEBI identifies WCAG 2.1 Level AA, or the latest equivalent standard such as WCAG 2.2 Level AA, as the primary technical benchmark. These guidelines ensure digital platforms remain Perceivable, Operable, Understandable, and Robust for all users.
• IS 17802: This Bureau of Indian Standards (BIS) standard aligns with WCAG while introducing additional accessibility requirements for Indian digital platforms, documents, and devices.
• GIGW (Guidelines for Indian Government Websites): GIGW complements WCAG by providing additional guidance for bilingual content, navigation, structured information, and overall website usability.
• Rights of Persons with Disabilities (RPwD) Act, 2016: The Act provides the statutory foundation for accessibility. It makes SEBI digital accessibility compliance requirements legally enforceable rather than optional recommendations.

What does minimum AA-level compliance mean for financial platforms?

• Financial data, charts, and graphs: Information presented through charts or colors must include equivalent alternative text (Alt Text), data tables, or sonification. This ensures visually impaired investors can interpret financial information without relying only on visual cues.
• Time-based security and sessions: Trading platforms must warn users before session timeouts and allow additional time or data saving. These measures prevent investors from losing information during critical activities, including onboarding or trade execution.
• Keyboard and voice operability: Investors must complete every stage, from login through trade execution, using only keyboards or assistive switch devices. Interactive elements, including buttons, form fields, and dropdown menus, must display clear and visible focus indicators.
• Accessible forms and error prevention: Order placement forms and dynamic content must use semantic HTML and WAI-ARIA (Web Accessibility Initiative - Accessible Rich Internet Applications) attributes. Error messages should clearly explain problems and recommend corrective actions for users with visual or cognitive disabilities.
• Accessible documents: Notices, annual reports, transaction statements, and other PDFs must include proper tagging, logical heading structures, and optical character recognition (OCR) support.
• KYC and authentication: Video KYC and digital onboarding processes must support captions, sign-language interpretation, and human-assisted offline alternatives whenever necessary.

What types of accessibility barriers, common on financial websites and trading apps are implicitly targeted by SEBI's requirement to comply with these standards?

SEBI's requirement to comply with IS 17802:2021, WCAG 2.1, and GIGW is intended to remove accessibility obstacles that prevent persons with disabilities from independently accessing digital financial services. These standards address several usability issues commonly found across financial websites, trading platforms, and investor applications.

Some of the key accessibility barriers addressed by SEBI's framework include:

Financial data presented only visually

Trading interfaces frequently rely on charts, graphs, and color indicators to communicate market information. Regulated Entities should provide alternative text, ARIA attributes, data tables, or equivalent accessible formats, so assistive technologies can interpret the same information.

Limited keyboard accessibility

Some trading dashboards require a mouse for navigation or transaction completion. Investors using keyboards or assistive input devices should navigate pages, operate menus, and complete trading activities through a logical keyboard focus sequence.

Poorly designed forms and verification workflows

Registration, multi-factor authentication, and digital KYC processes often contain inaccessible form controls or verification steps. Clearly labelled fields, accessible CAPTCHAs, and properly identified error messages help screen readers and voice-input technologies guide users successfully.

Documents that cannot be read by assistive technologies

Financial disclosures, annual reports, and account statements sometimes appear as image-based or unstructured PDFs. These documents should use accessible tagging and structured formatting so screen readers can accurately present their contents.

Video content without accessibility features

Educational videos, onboarding guidance, and Video KYC sessions may exclude users without captions or language support. Providing closed captions, transcripts, and Indian Sign Language (ISL) interpretation makes multimedia content accessible to a wider audience.

6. Governance, audits, and certified experts

Why does SEBI require REs to designate a Nodal Officer for digital accessibility? What responsibilities should this role typically cover?

SEBI requires Regulated Entities (REs) to appoint a Nodal Officer for digital accessibility to establish clear ownership of accessibility compliance across the organization. This role helps ensure continuous compliance with WCAG, GIGW, and the Rights of Persons with Disabilities (RPwD) Act. At the same time, it reinforces digital accessibility as a fundamental investor right rather than a standalone technical responsibility.

• Audit coordination: Coordinate periodic accessibility assessments of public websites, trading platforms, and mobile applications using IAAP-certified accessibility professionals.
• Remediation oversight: Monitor implementation of accessibility improvements, including screen-reader compatibility, alternative text, and resolution of audit findings.
• SCORES grievance handling: Oversee accessibility-related complaints submitted through the SEBI Complaints Redress System (SCORES) and ensure timely resolution.
• Policy integration: Embed accessibility requirements into internal policies, vendor agreements, Requests for Proposal (RFPs), and third-party software procurement processes.
• Training and sensitization: Develop accessibility training programs for employees and third-party developers covering accessibility standards and assistive technologies.

What is an accessibility audit under SEBI's regulations? Who should conduct these audits, and how often should they be performed?

SEBI's digital accessibility regulations require Regulated Entities to regularly assess whether their investor-facing digital services remain accessible for persons with disabilities. These assessments verify that accessibility requirements are consistently maintained across digital channels and not being implemented only once.

What qualifies as an accessibility audit?

• Scope of assessment: The review should cover public websites, iOS and Android applications, investment portals, trading terminals, digital onboarding platforms, and downloadable content, including PDFs.
• Evaluation criteria: Auditors should assess every platform against WCAG 2.1 Level AA or later versions, GIGW, and IS 17802 requirements.
• Assessment methods: A complete audit combines automated testing, manual source code inspection, and usability testing involving persons with disabilities.

Who should conduct these audits?

• Specialized expertise: Certifications such as Certified Professional in Web Accessibility (CPWA) and Web Accessibility Specialist (WAS) demonstrate advanced accessibility knowledge and practical assessment capabilities.
• Accurate compliance evaluation: Experienced accessibility professionals can identify complex barriers that automated scanning tools frequently overlook.
• Regulatory confidence: Independent certified assessments provide reliable evidence supporting compliance with the Rights of Persons with Disabilities (RPwD) Act, 2016.

How often should accessibility audits be performed?

• Baseline assessment: Regulated Entities should begin with a comprehensive audit establishing the current accessibility status of every covered platform.
• Periodic reviews: After the initial assessment, investor-facing digital platforms should undergo accessibility audits every year to maintain continued compliance.
• Compliance reporting: Audit findings and compliance reports should be submitted to the designated reporting authority within 30 days after each financial year.

7. Reporting, documentation, and Annexures

What specific information must REs provide in the Digital Accessibility Readiness & Compliance Status Report (Annexure B)? How do Annexure A mappings determine which authority receives this information?

Under SEBI's digital accessibility framework, Regulated Entities (REs) must submit a Digital Accessibility Readiness & Compliance Status Report using Annexure B. The report helps SEBI and designated authorities monitor accessibility readiness and identify compliance gaps. It also lets them track planned remediation across investor-facing digital platforms.

What information must REs include in Annexure B?

The report should present a platform-wise overview of every investor-facing digital system covered under SEBI's accessibility framework.

Platform details

Regulated Entities should identify every covered platform by providing its exact name and corresponding URL or application name. This includes websites, mobile applications, web portals, and digital onboarding or KYC systems.

WCAG compliance status

Each platform should indicate whether it satisfies the minimum accessibility requirement of WCAG 2.1 or WCAG 2.2 at Level AA.

Accessibility readiness

The report should describe the platform's current accessibility position by highlighting existing compliance gaps, known issues, and implementation challenges.

Remediation plan

Regulated Entities should specify the expected completion timeline and planned corrective actions for resolving identified accessibility issues.

Assessment oversight

The report should include details of the accessibility assessment conducted under the supervision of certified accessibility professionals, including IAAP-certified experts where applicable.

How does Annexure A determine the reporting authority?

Annexure A establishes the reporting pathway by linking each Regulated Entity with the appropriate authority responsible for receiving its Annexure B submission.

Direct reporting to SEBI

Regulated Entities directly supervised by SEBI should submit completed Annexure B reports through the designated email address, digital_acc@sebi.gov.in.

Reporting through Market Infrastructure Institutions

Mutual funds, stockbrokers, and other intermediaries should submit their reports to the appropriate Market Infrastructure Institution. The receiving authority depends on the entity's license category, such as the relevant stock exchange or depository identified through Annexure A.

How should REs compile the inventory of "every investor‑facing digital platform" for Annexure B—covering legacy systems, white‑label portals, and third‑party tools—and what level of evidence and documentation (audit reports, remediation logs, testing records) is expected to make submissions credible and defensible?

Regulated Entities (REs) should prepare Annexure B by identifying every digital touchpoint that investors use throughout their lifecycle. The inventory should cover all platforms supporting investor registration, transactions, portfolio access, and other investor-facing services while demonstrating compliance with WCAG 2.1 Level AA.

How should REs compile the inventory?

A complete inventory should capture every investor-facing platform, regardless of its age, ownership model, or technology provider.

Legacy systems

Include older or retired platforms that continue storing active investor information, even when unavailable for new onboarding. Record their current accessibility compliance status alongside operational restrictions.

White-label platforms

Treat white-label solutions as part of the Regulated Entity's own digital ecosystem. Document the parent website, associated subdomains, mobile applications, and connected APIs within the inventory.

Third-party tools

Include integrated services such as chat widgets, payment gateways, and KYC solutions operating inside investor platforms. Obtain formal WCAG conformance statements from every third-party technology provider supporting these services.

Consolidated platform records

Record each platform's URL, vendor details, platform category, and existing WCAG readiness using the prescribed Annexure B reporting format.

What evidence should support the submission?

SEBI expects Annexure B submissions to rely on verifiable documentation and not unsupported compliance declarations.

Accessibility audit reports

Maintain comprehensive audit reports prepared by certified accessibility professionals identifying failed WCAG success criteria and corresponding risk levels.

Remediation records

Preserve documented evidence showing identified issues, assigned developer tasks, corrective actions, and completion timelines for every accessibility improvement.

Testing documentation

Retain automated testing results together with manual usability testing records completed by persons with disabilities to demonstrate practical accessibility validation.

Vendor compliance evidence

Maintain signed VPAT (Voluntary Product Accessibility Template) documents or equivalent accessibility conformance certificates for embedded third-party products.

How can REs make submissions credible and defensible?

• Every accessibility issue reported through the SCORES platform should be traceable to the corresponding platform recorded within Annexure B.
• Accessibility fixes, testing records, and remediation logs should consistently demonstrate how reported issues were identified and resolved.
• The MD, CEO, or another Authorized Official should formally approve and digitally sign the IT system reporting before submission.

8. KYC, onboarding, and core investor flows

How must digital KYC and account‑opening flows be redesigned or audited to ensure they are inclusive and accessible for persons with different disabilities? Which specific onboarding steps tend to create accessibility barriers that REs must address under SEBI's guidelines?

SEBI requires Regulated Entities (REs) to design digital KYC and account-opening journeys that remain accessible for persons with different disabilities. Every onboarding workflow should comply with the Rights of Persons with Disabilities (RPwD) Act, 2016 and WCAG 2.1. It should support screen readers, keyboard navigation, and alternative interaction methods beyond visual or audio-based inputs.

Several onboarding stages commonly create accessibility barriers and require targeted redesigns under SEBI's guidelines.

Video KYC (V-CIP) and liveness verification

Automated liveness checks, including mandatory eye blinking or rapid facial movements, may exclude users with visual, facial, or motor disabilities. Regulated Entities should provide alternative verification methods, including document display or other facial verification approaches instead of blinking alone. Applications rejected through automated verification should always undergo human review before any account-opening decision becomes final.

Form filling and data capture

Long, complex forms with poor keyboard navigation or missing descriptions create difficulties for screen readers and assistive technologies. KYC forms should capture disability status and percentage while allowing investors to request suitable facilitative provisions during onboarding. Investors should also receive options such as human-assisted helpdesk callbacks whenever additional accessibility support becomes necessary.

Document upload

Restrictive photo submission requirements may prevent visually impaired investors from confirming uploaded documents before submission. Regulated Entities should support alternative document submission methods, including voice-assisted guidance and scanned document uploads.

e-Sign and wet signatures

Authentication methods relying only on OTP workflows or mouse-drawn signatures may disadvantage users with cognitive or motor disabilities. Regulated Entities should also accept thumb impressions that are wet-signed or stamped, scanned, cropped, and e-signed with other documents.

OTP verification and two-factor authentication

Short OTP time limits and inaccessible CAPTCHAs often create unnecessary challenges for investors with visual or cognitive disabilities. Authentication processes should include accessible two-factor authentication interfaces, remove audio-only CAPTCHAs, and provide longer session timeouts for verification.

Audit and governance requirements

• IAAP-certified accessibility professionals should conduct periodic audits covering all investor-facing digital platforms and onboarding workflows.
• Every Regulated Entity should appoint a senior Nodal Officer responsible for accessibility oversight and ongoing compliance management.
• Accessibility-related grievances should remain easy to report through formal, accessible grievance redressal mechanisms, including the SCORES platform.

9. Accessible documents, disclosures, and content

What document accessibility requirements apply to investor communications? What content workflows need to be updated to prevent new inaccessible documents from being generated after initial remediation?

Investor communications, including annual reports, prospectuses, and circulars, should remain accessible to all investors, including persons with disabilities. To achieve this, documents must follow recognized accessibility standards such as WCAG 2.1 Level AA and PDF/UA (ISO 14289). They should allow assistive technologies to interpret and present content accurately.

Document structure and navigation

Accessible documents should use a properly tagged PDF structure containing semantic elements such as headings, paragraphs, and lists. This structure enables screen readers to identify content correctly. It helps users navigate documents more efficiently.

Documents should also follow a logical reading order that presents information naturally. Content should remain understandable without confusion caused by complex, multi-column layouts or disconnected reading sequences.

Images, charts, and tables

Meaningful images, graphs, charts, and icons should include descriptive alternative text explaining their purpose and information. Decorative visual elements should be identified as artifacts, so screen readers can safely ignore them.

Tables should include clearly defined row and column headers using appropriate structural markup. Untagged layout tables should never replace properly structured data tables.

Headings, metadata, and formatting

• Documents should follow a consistent heading hierarchy from H1 through H6 without skipping heading levels. This approach improves navigation for users relying on assistive technologies.
• Each document should specify its primary language, include a meaningful document title, and provide interactive bookmarks for files exceeding two or three pages.
• Text should maintain a minimum color contrast ratio of 4.5:1 against background colors. Fonts should also remain fully embedded and mapped to Unicode for reliable accessibility support.

Authoring and document creation workflows

Accessibility should become part of the document creation process.

Authors using Word, Excel, or PowerPoint should avoid exporting documents through inaccessible PDF generation methods. They should apply native heading styles and run built-in accessibility checks before creating final PDFs.

Designers working with InDesign and Creative Cloud should use paragraph styles, export tags, and native alternative text during document development. PDFs should then be generated using accessibility-ready formats such as PDF/X-4 or PDF/UA.

Organizations should also replace outdated document generation processes with modern Document Composition Engines. This includes those like Adobe Experience Manager and data-driven reporting solutions. These systems automatically generate accessible PDF tags and XML structures during document creation.

Standardized templates

Organizations should maintain centrally managed templates for commonly used business documents, including Word and InDesign formats. These templates should already include accessible color contrast, predefined reading order, and designated placeholders for images.

Complex overlapping graphics and magazine-style layouts should be minimized. This is applicable unless designers carefully preserve a logical reading sequence.

Quality assurance before publication

Accessibility verification should combine automated validation with manual testing before investor communications are published. Automated accessibility checkers, including Grackle Docs, Adobe Acrobat Accessibility Checker, or VeraPDF, should identify structural tagging and color contrast issues before document release.

Manual reviews should also evaluate reading order, alternative text quality, and overall usability using screen readers such as JAWS or NVDA. These assessments confirm accessibility issues that automated tools cannot reliably detect.

Before publication, organizations should complete a final approval process verifying document metadata and accessibility compliance. Only the fully remediated, tagged PDF version should be uploaded to the investor portal.

10. SCORES, enforcement, vendors, and strategic impact

How does the new "Accessibility" complaint category in SCORES help investors report digital accessibility issues? What must Regulated Entities do after receiving a complaint, and how can these complaints affect SEBI's oversight?

The introduction of a dedicated "Accessibility" complaint category in SEBI SCORES gives investors a formal mechanism to report digital accessibility barriers. It strengthens digital accessibility as an enforceable investor right. Accessibility concerns now become part of SEBI's official regulatory and grievance redressal framework.

How does the new Accessibility category help investors?

Investors with disabilities can now report accessibility barriers affecting websites, mobile applications, or other investor-facing digital platforms directly through SCORES. This creates a structured process for raising concerns about inaccessible digital services under SEBI digital accessibility compliance framework.

What must Regulated Entities do after receiving a complaint?

• Platform remediation: The reported accessibility issue should be resolved by making the required technical improvements to the affected website, mobile application, or digital portal.
• Action Taken Report (ATR): After completing remediation, Regulated Entities should document the corrective measures within an Action Taken Report. Then, submit it through the SCORES platform within prescribed timelines.
• Continuous auditing: Accessibility complaints should also encourage regular accessibility audits by certified professionals to identify and prevent similar issues across other digital platforms.

How can these complaints influence SEBI's oversight?

• Targeted inspections: Multiple complaints involving similar accessibility issues or the same Regulated Entity may lead to focused inspections or thematic accessibility audits.
• Regulatory enforcement: Repeated failure to resolve verified accessibility barriers may trigger escalated regulatory action. This affects compliance assessments and can potentially result in enforcement measures for breaching Investor Right to Digital Accessibility requirements.
• Risk management expectations: Complaint trends can help SEBI identify emerging accessibility risks and strengthen future supervisory expectations. Over time, continuous accessibility verification may become a standard element of annual audits and broader operational risk management frameworks.

How should Regulated Entities manage accessibility for third-party platforms and vendors? How can they include accessibility in risk management and use SEBI's requirements to improve user experience and trust?

SEBI expects Regulated Entities (REs) to treat digital accessibility as a continuous operational responsibility. Meeting these requirements means embedding accessibility into vendor relationships, enterprise governance, and long-term digital strategy while creating more inclusive investor experiences.

Managing accessibility across third-party platforms and vendors

Third-party applications, white-label solutions, and vendor-provided platforms should meet the same accessibility requirements as internally developed digital systems.

Procurement and vendor contracts

Accessibility expectations should be clearly defined within every Request for Proposal (RFP) and master service agreement. Vendors should provide documented evidence demonstrating compliance with WCAG 2.1/2.2 Level AA, GIGW, and IS 17802 while committing to Service Level Agreements (SLAs) for future accessibility improvements.

White-label and SaaS platforms

Vendor-hosted portals, trading platforms, CRM dashboards, and other white-label solutions should support screen readers and complete keyboard navigation. Regulated Entities should verify these capabilities before deploying platforms for investors.

Third-party integrations

Integrated services, including payment gateways, APIs, and e-KYC or Video KYC modules, should deliver accessible user interface components. Accessibility requirements should apply consistently across every third-party feature supporting investor journeys.

Vendor accountability

Vendor agreements should clearly assign responsibility for resolving accessibility issues throughout the software development lifecycle. Continuous Integration and Continuous Deployment (CI/CD) accessibility testing should also become part of routine software delivery practices.

Including accessibility within risk management

SEBI digital accessibility compliance framework encourages Regulated Entities to manage accessibility alongside other significant operational risks, including cybersecurity.

Vendor risk assessments

Accessibility should become a formal evaluation criterion within vendor risk assessments. Previous accessibility audits, remediation history, and overall compliance performance should influence vendor risk ratings.

Compliance documentation

Regulated Entities should maintain complete records covering vendor testing, accessibility audits, corrective actions, and remediation timelines. These records support platform-level Digital Accessibility Readiness and Compliance Status Reporting required under SEBI digital accessibility compliance.

Complaint management

Organizations should establish processes for monitoring and resolving accessibility complaints received through the SCORES platform. These complaints should receive the same governance attention as cybersecurity incidents or financial grievances.

Nodal Officer oversight

A designated Nodal Officer should coordinate accessibility activities across internal teams, technology partners, and external vendors. This centralized oversight helps maintain consistent accessibility governance throughout the organization.

Using accessibility to improve user experience and trust

• Better user experience: Features such as logical reading order, higher color contrast, and screen reader compatibility improve usability for every investor. These improvements can reduce user drop-offs while making onboarding faster.
• Expanding the investor base: Accessible digital platforms allow more than 70 million persons with disabilities in India to participate independently in financial markets. This creates opportunities to serve an important and historically underserved investor segment.
• Stronger brand reputation: Demonstrating a commitment to accessibility strengthens investor confidence and reinforces responsible business practices. It also supports Environmental, Social, and Governance (ESG) objectives while fulfilling the Investor Charter's Right to Digital Accessibility.
• Long-term digital maturity: Embedding accessibility into design systems from the beginning reduces future redevelopment costs and simplifies ongoing compliance. This proactive approach helps Regulated Entities build resilient, inclusive, and future-ready digital platforms.