How we work
Accessibility
What has been done to make this site usable without a mouse or a screen — and what has not been done yet.
This site is built to be usable by people who do not browse the way a designer assumes. That is partly a matter of doing the job properly, and partly a legal duty: SEBI requires every regulated entity to comply with digital accessibility obligations under the Rights of Persons with Disabilities Act, 2016.
What has been done
- Everything works without JavaScript. Every disclosure, price and explainer is in the HTML itself. Two of the three research sites benchmarked while building this return a blank page with scripting off.
- Keyboard operable throughout. A skip-to-content link is the first thing you reach, every interactive element shows a visible focus ring, and nothing is reachable by mouse alone.
- Screen-reader structure. One
mainlandmark per page, headings in order, the page language declared, and every form control carries a name. - Contrast. Text and background are checked programmatically on every build, in both the light and dark themes, and the build fails if any text falls too close to what sits behind it.
- Respects your settings. Dark mode follows your system preference unless you override it, and all motion is disabled if you have asked your device to reduce motion.
- Reflows to a phone. Every page is checked at 390 px with no sideways scrolling, and wide tables scroll inside their own frame rather than pushing the page out.
- No traps. No pop-ups, no interstitials, no countdown timers, no auto-playing media and nothing that steals focus.
What is not done yet
This statement describes what has been built and tested, not a certification. There has been no independent accessibility audit, and no testing with real assistive technology by people who rely on it. Automated checks catch structure; they do not tell you whether a page is actually usable. Saying otherwise would be the same kind of unverified claim this site refuses to make everywhere else.
If something does not work for you
Tell us and it will be fixed — that is a faster route than any formal process, and an accessibility failure is treated as a defect, not a feature request. The contact and grievance routes are on the grievance page. If a page is unusable for you, we will also supply its content in whatever format does work.