If you run a broker, mutual fund, or fintech site on Webflow, accessibility just became a regulatory file — not a nice-to-have. In July 2025, SEBI issued Circular No. SEBI/HO/ITD-1/ITD_VIAP/P/CIR/2025/111, requiring regulated entities (REs) to make investor-facing digital platforms accessible under the Rights of Persons with Disabilities Act, 2016.

That includes your marketing site, investor portal, document library, mobile app, and every PDF you publish. Webflow is a strong platform for finance marketing — fast iteration, CMS-driven disclosures, polished design. But SEBI does not grade your intentions. It grades whether a keyboard-only user can open an account, read a circular, and file a complaint without hitting a wall.

This is what the mandate actually requires, the deadlines that matter in 2026, and the specific gaps we see on Webflow builds — plus what developers need to add so the site can survive an IAAP audit.

Note: This is a technical guide for Webflow teams, not legal advice. Confirm reporting authority and format with your compliance counsel.

What SEBI now requires — and who it covers

The July 2025 circular applies to SEBI-regulated entities (REs) — intermediaries and market infrastructure institutions: stock exchanges, depositories, brokers, mutual funds, portfolio managers, investment advisers, research analysts, and other SEBI-registered players. If your investor-facing website, app, or portal belongs to an RE, it is directly in scope.

Listed companies are a separate case. Corporate IR websites are governed by LODR Regulation 46 (disclosure content and timeliness), not Circular 2025/111 — unless that listed entity is also an RE. General obligations under the RPwD Act may still apply to any establishment providing public digital services. Map your entity type before scoping the audit.

• Websites and landing pages — corporate sites, product pages, onboarding flows
• Investor portals and trading interfaces — web and mobile
• Published documents — circulars, KYC forms, offer documents, factsheets
• Multimedia — videos, webinars, embedded charts with data updates

SEBI followed up with compliance guidelines (Circular 2025/131, September 2025) and timeline clarifications for investment advisers and research analysts (Circular 2025/121, August 2025). For most REs, the core deadlines below still stand.

The 2026 compliance timeline

SEBI compressed a full accessibility programme into roughly ten months. If you have not started, you are in the remediation window.

• March 31, 2026 — Submit readiness and compliance status for each digital platform to your reporting authority (SEBI-bound REs email digitalacc@sebi.gov.in).
• April 30, 2026 — Complete IAAP-certified accessibility audits, including usability testing by persons with disabilities.
• July 31, 2026 — Remediate all audit findings and reach full conformance.
• From April 30, 2027 onward — Annual accessibility audits and reporting become ongoing compliance.

The three standards on your audit checklist

SEBI names three technical baselines. Your Webflow site needs to satisfy all of them — auditors will not pick the easiest one.

• WCAG 2.1 Level AA (or latest version) — the international benchmark for perceivable, operable, understandable, and robust web content. WCAG 2.2 AA is the safer target in 2026.
• GIGW (Guidelines for Indian Government Websites) — India-specific requirements around navigation, readability, and government-style web conventions.
• IS 17802:2021 — India's national digital accessibility standard covering websites, apps, and documents.

Underpinning all three is the Rights of Persons with Disabilities Act, 2016 and its 2017 Rules.

Where Webflow helps — and where it stops

Webflow is better than most visual builders for accessibility if you use it deliberately. Native elements ship with semantic HTML and ARIA support. You can set alt text, add custom attributes, and style :focus-visible states in the Designer.

But Webflow does not auto-generate WCAG conformance. Common failure modes on finance sites we audit:

• No skip link — keyboard users tab through the entire nav on every page load.
• Custom interactions without keyboard paths — modals, mega-menus, and IX2-driven dropdowns that only respond to clicks.
• Missing form labels — placeholder-only inputs on lead-gen and KYC pre-screening forms.
• CMS images without alt text — team photos, chart thumbnails, and fund manager headshots published blank.
• Live data embeds without ARIA — tickers and calculators that update visually but stay silent to screen readers.
• Third-party widgets — chat bots, cookie banners, analytics overlays that inject inaccessible markup after publish.

The developer fixes that actually move the needle

1. Skip navigation (site-wide)

Add a skip link as the first focusable element in your site header. Pair it with a tabindex="-1" target on your main content wrapper.

/* Site Settings → Custom Code → Head */
.skip-link {
  position: absolute;
  left: -9999px;
  top: 1rem;
  z-index: 9999;
  padding: 0.75rem 1.25rem;
  background: #17573e;
  color: #fff;
  font-weight: 600;
  text-decoration: none;
  border-radius: 6px;
}
.skip-link:focus-visible {
  left: 1rem;
  outline: 3px solid #c4cc25;
  outline-offset: 2px;
}
#main-content:focus { outline: none; }

2. Visible focus states

/* Designer → Add focused state OR site CSS */
a:focus-visible,
button:focus-visible,
[tabindex]:focus-visible {
  outline: 3px solid #c4cc25;
  outline-offset: 2px;
}

3. ARIA on live embeds

<!-- Custom embed: live data widget -->
<div role="region" aria-label="Market data chart"
     aria-live="polite" data-feed="nav">
  <!-- chart renders here -->
</div>

4. Heading hierarchy and landmarks

One H1 per page. Section elements for major blocks. No skipping from H2 to H5 because the style panel made it convenient.

5. Forms wired for real users

Every input needs a visible <label> or aria-label. Error messages must be programmatically associated — not just red text below the field.

Documents, PDFs, and investor disclosures

SEBI explicitly calls out accessible documents. Factsheets, SID/KIM PDFs, and annual reports must be tagged PDFs — not flat exports from InDesign or Word.

• Export tagged PDFs from the source tool, then verify with Acrobat's accessibility checker or PAC.
• Never publish a scanned image PDF for a mandatory disclosure.
• Link text matters too — "Click here" for a KIM download fails WCAG 2.4.4.

Audits, reporting, and investor complaints

SEBI requires audits by IAAP-certified professionals, with usability testing involving persons with disabilities. Investors can lodge accessibility complaints on SEBI's SCORES platform. REs must remediate reported issues to close complaints.

A practical rollout sequence for Webflow teams

Teams already building B2B and fintech sites on Webflow have a head start. The gap is not platform choice — it is whether accessibility is in your component spec from day one.

Lessons

SEBI connected investor protection to accessibility law and gave REs a hard deadline. For Webflow developers, the work is concrete: skip links, focus, labels, alt text, tagged PDFs, and keyboard-safe interactions.