Accessibility
Accessibility Statement
Effective: 22 September 2026 · Last updated: 22 September 2026
We want this site to be usable by everyone, including people who browse with a keyboard, a screen reader, magnification, or their own colour and spacing settings. This page says what we have done, what we have measured, and — just as importantly — what we have not.
1. Conformance status
The Web Content Accessibility Guidelines (WCAG) define requirements for making web content more accessible. This site targets WCAG 2.2 level AA.
We describe this site as partially conformant with WCAG 2.2 level AA. Partially conformant means most of the standard is met, but we cannot claim full conformance because the site has not been independently audited or tested with real assistive technology. We would rather say that than claim more than we have verified.
2. What we have tested
These were checked against the live site, on every page, programmatically rather than by impression:
| Requirement | Result |
|---|---|
| Contrast (1.4.3) | Every piece of text measured against its actual composited background, in both light and dark themes. No failures. |
| Reflow (1.4.10) | No horizontal scrolling at 320px wide — the equivalent of 400% zoom on a desktop screen. |
| Text spacing (1.4.12) | Line height, letter, word and paragraph spacing increased to the values the standard requires. Nothing is clipped or overlapped. |
| Keyboard access (2.1.1) | Every interactive element is reachable and operable by keyboard. Forms use native controls rather than styled substitutes, and questions are grouped in real fieldsets. |
| Bypass blocks (2.4.1) | A skip link is the first thing you reach by keyboard, and it moves focus to the main content rather than only scrolling to it. |
| Focus visible (2.4.7) | A clear outline on every focused element, and no element relies on colour alone to show focus. |
| Focus not obscured (2.4.11) | The header sticks to the top of the page, so we checked focus is never hidden behind it while tabbing. |
| Target size (2.5.8) | Targets are large enough, or spaced far enough apart to meet the spacing exception. |
| Headings and structure (1.3.1) | One main heading per page, no skipped levels, and form errors are programmatically linked to the field they describe. |
| Names and roles (4.1.2) | Every control has an accessible name. Nothing is announced as an unlabelled button. |
Beyond the standard: motion is disabled for anyone whose system asks for reduced motion, the automation finder moves focus as you move between questions so the change is not silent, and the decorative background animation on the home page is hidden from assistive technology entirely.
3. Known limitations
We are telling you these rather than waiting for you to find them:
- The site has not been tested with screen readers such as NVDA, JAWS or VoiceOver. Our checks were automated and manual-by-keyboard, which catches structure and contrast but not how a screen reader actually reads a page.
- It has not been tested with voice control or switch access.
- It has not been audited by an independent accessibility specialist, and no part of it has been reviewed by a disabled user.
- The animated background on the home page is decorative and hidden from assistive technology, but it has not been tested against every combination of browser and reduced-motion setting.
None of these are reasons to avoid telling us about a problem. If something does not work for you, that is the most useful information we can get.
4. Tell us about a problem
If any part of this site is difficult or impossible for you to use, email hello@twishivplatforms.com and say what happened, which page, and what you were using — browser, screen reader, or anything else that helps us reproduce it. You do not need to know why it failed or use any particular terminology.
We will acknowledge within 2 business days and give you a substantive answer within 10 business days, including what we intend to do and by when. If a fix will take longer, we will tell you that rather than go quiet.
If you need information from this site in another format — a document, a summary, or the content of a page read out or sent differently — ask, and we will provide it. Contact details are on our contact page, and our postal address is B-203, Rosedale Heights, Vasna Bhayli Road, Bhayli, Vadodara, Gujarat 391410, India.
5. How this was assessed
Self-evaluation. The checks described above were run against the built, deployed site rather than a development version, because the deployed site is what visitors actually get.
Accessibility work is not finished here. As the site changes we re-run these checks, and we intend to test with real assistive technology and to seek an independent review.
Questions about this document: hello@twishivplatforms.com · +91 93131 52136