QgenticQgentic
Qgentic / legal / accessibility
Accessibility Statement · qgentic.co and the Qgentic console

Built to be Usable by Everyone.

This statement covers the qgentic.co website and the Qgentic customer console. Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Compliance software is used under deadline pressure, often for long stretches — an interface that strains its operator is a defect.

Prepared: 31 July 2026.

What We Have Built

Measures Already in Place.

Contrast, Verified in CI

Text and interface contrast on product surfaces is checked by an automated WCAG contrast test that runs in our build pipeline — a contrast regression fails the build rather than reaching users. Both light and dark themes are covered.

Keyboard & Structure

Every page carries a skip-to-content link, a logical heading hierarchy, and visible focus states. Interactive controls are native HTML elements (buttons, links, details/summary accordions) that work with a keyboard and with assistive technology out of the box.

Reader Preferences Respected

Colour theme follows your operating-system preference by default, with a manual override. Text scales with browser zoom and font-size settings; layouts are responsive down to small screens without horizontal scrolling.

Known Limitations

Where We Are Not Yet Conformant.

We prefer an honest list to a vague claim. Known gaps at the date above: the animated product demos on this site are supplementary to the written product descriptions alongside them — but their narration does not yet carry synchronised captions; and some downloadable sample artefacts (CSV/JSON evidence bundles) are raw machine formats whose accessibility depends on the tool used to open them. We review this list as the product evolves.

Feedback & Enforcement

Tell Us When Something Does Not Work.

If any part of this site or the Qgentic console is difficult or impossible for you to use, contact us via the contact form — describe the page, the assistive technology or settings in use, and what went wrong. We treat accessibility reports as defects: they are triaged with the same severity as functional bugs. If you are not satisfied with our response, you may escalate to the Equality Advisory and Support Service (EASS).

Same Standard as Our Filings. We hold this statement to the discipline we apply to regulatory claims: say what is true, list what is not yet done, and fix defects when they are reported. Direct enquiries to us.