Accessibility

Accessibility Statement

Last reviewed: 22 April 2026

Our commitment

InfiQuant is committed to making our website accessible to as many people as possible. We design and build with accessibility in mind so users — including those who rely on assistive technology — can read our research, manage their accounts, and use the platform without barriers.

Conformance status

We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Most of the website meets that bar today; some interactive areas of the dashboard are still being reviewed.

What we’ve done

Semantic landmarks (header, nav, main, footer) and a skip-to-content link.
Visible keyboard focus styles on all interactive elements.
Forms with associated labels, inline error messages, and aria-live announcements.
Cookie consent rendered as role="alertdialog" with a focus trap and Esc-to-dismiss.
Mobile menu and modal dialogs trap focus and restore it on close.
Animations honour prefers-reduced-motion and disable themselves when set.
Automated accessibility checks run in CI using axe-core against every release.

Known limitations

Some chart and live-data widgets may not yet expose their underlying data to screen readers in a structured form. We’re working on tabular fallbacks.
Our colour palette favours dark backgrounds. While contrast meets AA on body text, some decorative elements fall below AA — we accept that trade-off and exclude purely decorative tokens from contrast scoring.

Assistive technology compatibility

We test the marketing site against the latest stable releases of:

VoiceOver on macOS and iOS (Safari)
NVDA on Windows (Firefox, Edge)
TalkBack on Android (Chrome)

Reporting an accessibility issue

If you encounter an accessibility barrier — anything from a missing label to a flow you can’t complete with the keyboard — please email accessibility@infiquant.co.in. Include the page URL, the device and assistive technology you’re using, and a description of what went wrong. We aim to respond within 5 business days.

Related policies

What we’ve done

Semantic landmarks (header, nav, main, footer) and a skip-to-content link.

Visible keyboard focus styles on all interactive elements.

Forms with associated labels, inline error messages, and aria-live announcements.

Cookie consent rendered as role="alertdialog" with a focus trap and Esc-to-dismiss.

Mobile menu and modal dialogs trap focus and restore it on close.

Animations honour prefers-reduced-motion and disable themselves when set.

Automated accessibility checks run in CI using axe-core against every release.

Known limitations

Some chart and live-data widgets may not yet expose their underlying data to screen readers in a structured form. We’re working on tabular fallbacks.

Our colour palette favours dark backgrounds. While contrast meets AA on body text, some decorative elements fall below AA — we accept that trade-off and exclude purely decorative tokens from contrast scoring.

Reporting an accessibility issue