SEBI Digital Accessibility Timeline Extension 2026: Website and App Compliance Plan

By Ravi Sisodia · Reviewed by CA Divyanshu Sengar · Updated 5 October 2026

SEBI's 31 July 2026 circular extended digital-accessibility compliance timelines. Regulated entities should use the revised dates to finish accessibility audit, remediation, procurement and evidence rather than treat the extension as a pause.

Finin2min 2-Minute Summary

• SEBI issued an extension-of-timelines circular for digital accessibility on 31 July 2026.
• The revised timeline should be read from the circular itself; regulated entities should avoid using superseded project dates.
• Website and mobile-app accessibility requires design, code, content and testing controls rather than a one-time compliance certificate.
• Third-party widgets, trading components, PDFs and customer-service journeys belong in the accessibility inventory.
• Audit findings should be risk-ranked, remediated, retested and supported by closure evidence before the revised deadline.

Reset the project plan to the actual circular

Replace old compliance dates in board/compliance trackers with the 31 July circular's revised dates. Keep the superseded date in change history so teams understand why the project timeline moved.

Do not infer a broader exemption from a deadline extension; underlying accessibility obligations and scope remain.

Inventory customer journeys, not just pages

Cover onboarding, login, order/trading flow, statements, complaints, alerts, downloadable documents and help content. A home page can pass while the critical authenticated journey remains unusable.

Include vendor-provided widgets and SDKs in testing and contracts because an inaccessible third-party component still affects the regulated entity's customer interface.

Audit closure needs retesting

Track each defect by severity, WCAG/accessibility criterion, affected journey, owner and fix version. Retest with automated and human methods appropriate to the defect rather than closing from a developer comment.

Keep evidence of unresolved exceptions and the approved remediation plan.

Accessibility case: trading journey passes homepage audit but fails execution

A regulated website may have accessible navigation and disclosure pages while the authenticated order-entry modal cannot be used with a keyboard or screen reader. The customer-impacting defect is therefore in the most important journey even though a superficial site scan looks positive.

Test end-to-end flows: login, search, order placement, confirmation, contract note, funds/securities views and complaint submission. Include error messages, time-outs and OTP/authentication steps because accessibility failures often appear only under exception conditions.

For each issue, record severity and an interim accommodation if remediation cannot be immediate. The revised SEBI timeline should drive completion, but customer support should already know how to assist affected users without bypassing security.

• Test authenticated high-value journeys, not only public pages.
• Include keyboard, screen-reader and zoom/reflow scenarios.
• Record interim support route for unresolved defects.
• Retest after each material front-end release.

PDF and statement accessibility matters too

Digital accessibility should include contract notes, account statements, disclosures and downloadable PDFs, not only HTML and native-app screens. A customer who can place an order but cannot read the resulting confirmation remains unable to complete the service journey independently. Include document templates in the accessibility release and regression process.

• Test recurring statement/document templates.
• Include generated PDFs in release regression.

Accessibility compliance checklist

• 31 July circular dates adopted.
• Web/app/document journey inventory.
• Independent accessibility assessment.
• Defect severity and remediation owner.
• Vendor component coverage.
• Retest and closure evidence.
• Governance reporting until revised deadline.

Questions readers commonly ask

Did SEBI cancel digital-accessibility requirements?

No. It extended timelines.

Which date source should a team use?

The 31 July 2026 SEBI circular and any later verified amendment.

Is an automated scanner enough?

No. Important usability/accessibility issues require broader testing, including human review.

Should third-party widgets be included?

Yes. They form part of the customer experience and should be covered by accessibility governance.

Official / primary sources

• SEBI - Digital Accessibility Timeline Extension - 31 July 2026 circular
• SEBI Legal Listings - Current circular status

Disclaimer

Important: General educational and professional-reference material. Verify the current operative instrument, effective date and exact facts before acting. Consultation papers are not final law unless SEBI subsequently adopts them. Educational and professional reference only; confirm the current law, rates and the facts of your case before relying on this page.