Accessibility Statement

QNSI's accessibility commitment, the standard we build to, known gaps, and how to report a barrier.

Last updated: 2026-07-13 · Effective: 2026-07-13

Generated from the single legal source of truth (apps/web/lib/legal/). Do not edit by hand - edit the source and run pnpm gen:legal-docs. The authoritative published version of every document is on the QNSI Legal and Trust Center.

Commitment

QNSI aims to meet Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across the public website, the developer documentation, and the customer portal. Public-sector and regulated buyers are frequently required to procure only from vendors that make this commitment, and we take it as a product requirement, not a checkbox.

What we build to

  • Semantic HTML with a logical heading structure and landmark regions.
  • Keyboard operability for interactive controls; visible focus states.
  • Colour is not the sole carrier of meaning; contrast targets AA.
  • Text alternatives for non-text content; captions where media is used.
  • Respect for reduced-motion and colour-scheme preferences.

Known gaps (stated honestly)

QNSI has not yet completed an independent third-party accessibility audit, and we do not claim a formal VPAT/ACR. Complex data visualisations and some deep-technical evidence pages are the most likely places to fall short of AA today. We are not going to claim conformance we have not tested.

If you need a formal conformance report for a procurement process, contact us and we will tell you exactly where we stand.

Report a barrier

If any part of QNSI is not usable for you, tell us at qnsi-support@heossi.com and describe the barrier and the assistive technology you use. We treat accessibility defects as defects.