SEBI Gives Financial Firms More Time—But Digital Accessibility Compliance Isn't Going Away

By PXW | Accessibility Bytes 💌

Date Published: Jul 31, 2026

Date Modified: Jul 31, 2026

SEBI has given regulated entities more time to meet digital accessibility requirements. But this is not a relaxation of the requirement itself.

On July 31, 2026, the Securities and Exchange Board of India (SEBI) issued a new circular extending the timeline for compliance with its digital accessibility requirements.

The most important change is straightforward:

The deadline for conducting accessibility audits of digital platforms and remediating the findings has been extended to October 31, 2026.

For SEBI-regulated organizations that have already started their accessibility programs, this creates additional implementation time.

For organizations that have not started, however, the message is very different: the clock is still running.

SEBI Digital Accessibility Update: What Happened?

SEBI's latest circular, issued on July 31, 2026, is titled "Extension of timelines with respect to compliance of Digital Accessibility Circulars."

It follows a series of earlier SEBI circulars that progressively established digital accessibility requirements for Regulated Entities (REs).

The original framework was introduced in July 2025 under the Rights of Persons with Disabilities Act, 2016 (RPwD Act). SEBI subsequently issued further circulars and clarifications to define implementation requirements and timelines.

The latest development does not remove those requirements.

Instead, SEBI has provided additional time for one of the most important implementation stages:

Accessibility audit + remediation of audit findings → October 31, 2026

SEBI has also made it clear that other provisions of the earlier digital accessibility circulars continue to remain applicable.

What Is the New Date?

The immediate date organizations need to put on their compliance calendars is:

October 31, 2026
Conduct the accessibility audit of digital platforms and remediate the findings to ensure compliance.

This is particularly important because an accessibility audit is not the same thing as simply running an automated accessibility scanner.

A meaningful audit can involve manual keyboard testing, screen-reader testing, focus management, forms, dynamic content, contrast, zoom and reflow, mobile accessibility, document accessibility and real user workflows.

The audit identifies the barriers. Remediation is what removes them.

Where Does This Fit in the SEBI Timeline?

To understand the latest extension, it helps to look at how the framework has evolved.

July 31, 2025
SEBI introduced mandatory digital accessibility requirements for Regulated Entities under the RPwD Act framework.
August 29, 2025
SEBI extended several implementation timelines, including the accessibility audit and remediation deadlines.
September 25, 2025
SEBI issued detailed compliance guidelines covering digital platforms, accessibility audits, reporting and compliance mechanisms.
December 8, 2025
SEBI issued further clarification, including the recognition of investors' right to digital accessibility and requirements around readiness and compliance reporting.
July 31, 2026
SEBI issued the latest extension, moving the deadline for accessibility audits and remediation to October 31, 2026.

The pattern is important.

SEBI has not abandoned the accessibility framework. Instead, it has continued refining implementation while giving regulated entities additional time to execute it properly.

Who Should Be Paying Attention?

This is not a requirement limited to one type of financial organization.

The digital accessibility framework applies across the SEBI-regulated ecosystem, including organizations such as:

Stock brokers
Depository Participants
Investment Advisers
Research Analysts
Mutual funds
Portfolio managers
Market Infrastructure Institutions
Other SEBI-regulated entities

And the scope is not limited to the homepage of a corporate website.

Think about the actual digital journey of an investor.

Researching an investment
Creating an account
Completing KYC
Reading investment information
Accessing reports and disclosures
Using a trading or investment platform
Submitting forms
Accessing statements and documents
Raising a complaint or grievance

If any of these journeys contains an accessibility barrier, the investor's experience can break at the point where it matters most.

Why Financial Services Need to Take This Seriously

Accessibility in financial services is different from accessibility on a typical informational website.

A person may be able to tolerate an inaccessible article.

They cannot be expected to tolerate an inaccessible process for opening an account, understanding an investment, placing an order, accessing their holdings or managing their money.

Financial platforms are increasingly digital-first. For many investors, the website or mobile application is the actual branch.

If the digital branch is inaccessible, the customer may have no genuinely independent alternative.

Accessibility Is Also a Product Quality Issue

There is another reason this matters.

The same accessibility improvements that help users with disabilities frequently improve the product for everyone.

Clear navigation makes complex financial products easier to understand.
Better form labels and error messages reduce failed applications and support requests.
Strong keyboard navigation benefits users who prefer keyboard interaction and power users.
Better contrast improves readability across different screens and lighting conditions.
Logical content structures make lengthy financial information easier to scan and understand.
Accessible mobile interactions create a more predictable experience for users across devices.

This is why accessibility should not be treated simply as a compliance department's responsibility.

It touches product, engineering, design, QA, customer support, legal, compliance and business teams.

A Practical Example: Zerodha and Accessibility as Product Design

Consider the experience of using a trading application.

A conventional accessibility checklist might say:

"Make the buttons accessible."

But that is not really the business problem.

The real question is:

Can an investor independently understand what is happening and complete the task they came to perform?

Zerodha provides an interesting example through its Kite Accessibility Mode.

According to Zerodha's own support documentation, the feature is designed to make the Kite app easier to navigate for visually impaired clients and improve compatibility with TalkBack and voice-assistant applications.

The differences are particularly interesting because they focus on actual investor tasks, not simply visual adjustments.

For example, Accessibility Mode changes how certain interactions work:

Market depth can be opened directly instead of requiring a scroll-up.
Placing an order can be completed with a simpler interaction.
Holdings and positions can expose their information without requiring the same scrolling interaction as the standard interface.
SIP details and executed-order information can be accessed more directly.

This illustrates an important principle for financial-product teams:

Accessibility is not just about making an interface technically compliant. It is about making important financial tasks independently usable.

And that distinction matters enormously when the platform is being used for real financial decisions.

Where Does ROI Come Into the Picture?

"What is the ROI of accessibility?"

It is a fair question for any business leader.

And the answer should not simply be: "because SEBI requires it."

Compliance is one part of the business case. The larger opportunity is improving the digital product itself.

1. More Customers Can Use the Product

An accessible platform removes unnecessary barriers for people with disabilities and can improve usability for many other customers as well.

For financial organizations, where digital platforms are central to customer acquisition and retention, improving accessibility can mean making the product usable by a broader audience.

2. Fewer Failed Journeys

Imagine a customer who reaches the KYC stage but cannot understand a form field using a screen reader.

Or someone who cannot identify the error preventing an application from being submitted.

The company has already paid to acquire that customer. The problem is now occurring at the conversion stage.

Better accessibility can reduce this type of friction.

3. Lower Support Dependency

When customers cannot complete tasks independently, they often turn to customer support.

A more accessible interface can allow customers to complete more tasks without assistance.

4. Reduced Compliance Risk

The regulatory cost of ignoring accessibility can extend beyond the cost of fixing the website.

Organizations must consider regulatory exposure, investor complaints, remediation costs, reputational damage and the operational disruption caused by rushing accessibility work after a compliance issue emerges.

5. Better Product Development

Accessibility requirements often encourage better engineering practices: semantic markup, predictable interaction patterns, structured content, clearer errors and more robust component design.

These improvements can benefit the entire product.

The Cost of Waiting

An extension can look like additional breathing room.

But there is another way to look at it.

Every month an organization waits, the remediation window gets smaller.

A large financial platform may contain:

Multiple websites
Mobile applications
Investor portals
Login and authentication flows
KYC workflows
Trading interfaces
Research content
PDF reports
Forms and disclosures
Third-party integrations

Auditing these platforms is one task.

Fixing the findings is another.

Then comes regression testing.

Then documentation.

Then ongoing monitoring.

That is why October 31 should not be treated as the date to start the project.

October 31, 2026 should be the date by which the work is substantially completed—not the date on which the work begins.

What Should Enterprises Do Now?

The practical response to the new SEBI update should be a structured accessibility program.

Step 1: Identify Every Investor-Facing Digital Platform

Do not begin with only the corporate website.

Create a complete inventory of the digital platforms through which investors interact with the organization.

Include websites, mobile applications, portals, forms, investor dashboards, downloadable documents and other relevant digital services.

Step 2: Establish the Current Accessibility Baseline

Before fixing anything, determine where the organization stands.

Review the platforms against the applicable accessibility requirements and identify critical barriers.

Automated testing can help identify common technical issues, but it should be complemented by manual testing.

Step 3: Perform Real User-Flow Testing

This is particularly important for financial services.

Do not test only individual pages.

Test complete journeys:

Can a user log in?
Can they navigate the dashboard?
Can they understand financial information?
Can they complete KYC?
Can they submit a form?
Can they access statements and reports?
Can they raise a complaint?
Can they complete critical transactions independently?

Step 4: Prioritize the Findings

Not every accessibility issue creates the same level of risk.

Prioritize barriers that prevent investors from completing critical activities.

A missing decorative alt attribute and an inaccessible KYC workflow should not receive the same remediation priority.

Step 5: Remediate With Product and Engineering Teams

Accessibility should not become a ticket backlog owned entirely by compliance.

Product managers, designers, developers and QA teams need to work together to address the underlying causes.

Step 6: Re-Test After Remediation

Fixing an issue is not the end of the process.

Every significant remediation should be validated.

A change to a shared component can also affect dozens of pages or workflows, so regression testing is essential.

Step 7: Document Everything

Maintain evidence of:

Platforms audited
Testing methodology
Accessibility findings
Remediation completed
Re-testing results
Outstanding issues, if any
Compliance submissions
Ongoing accessibility processes

Documentation becomes especially important when accessibility moves from an informal initiative to a regulated compliance process.

Step 8: Make Accessibility Part of the Release Process

The biggest mistake would be treating October 31 as the finish line for accessibility.

Financial platforms change constantly.

New features are released. Interfaces are redesigned. Third-party services are integrated. New documents are published.

Any of these changes can introduce new accessibility barriers.

Accessibility therefore needs to become part of the organization's SDLC, QA, design review and release governance.

A Better Way to Think About the Deadline

There are two ways an enterprise can interpret SEBI's latest announcement.

The first is:

"Great. We have more time."

The second is:

"We now have a clearer window to do this properly."

The second approach is the more sustainable one.

Accessibility audits should not be rushed. Remediation should not be superficial. Compliance documentation should not be created at the last minute.

Most importantly, the people who actually use these platforms should be considered throughout the process.

The Bigger Message From SEBI

The July 31, 2026 extension should not be interpreted as SEBI stepping back from digital accessibility.

Quite the opposite.

The regulator has continued to build on the digital accessibility framework through multiple circulars, clarifications and compliance requirements.

The December 2025 clarification went a step further by recognizing investors' right to digital accessibility and introducing a more structured approach to readiness and ongoing audits.

The latest extension simply gives organizations additional time to complete a critical part of that journey.

The requirement has not disappeared. The deadline has moved.

Final Takeaway for SEBI-Regulated Organizations

If your organization operates an investor-facing digital platform, accessibility should already be on the compliance roadmap.

If you have completed your audit, use the additional time to strengthen remediation, regression testing and documentation.

If remediation is underway, use the extension to complete the work properly rather than applying temporary fixes.

And if you have not started, the message is simple: start now.

The new deadline is October 31, 2026.

But the real objective is bigger than meeting a date on a regulatory calendar.

It is about ensuring that an investor—regardless of disability—can independently access information, understand their options and use the financial services they are entitled to access.

Compliance may be the reason organizations start. Better digital experiences are what make the investment worthwhile.