Accessibility
Klarvant sells a product that audits other organisations' digital governance. Holding ourselves to the same standard on our own surfaces is the only honest position. This page records our accessibility commitment, the conformance level we work to, how we got there, and how to tell us when we fall short.
Commitment
Web Content Accessibility Guidelines 2.1 at the AA level is the conformance bar for every public surface Klarvant operates: this marketing site, the Klarvant Namespace Command product UI, and any document the product produces. Where AAA criteria can be met without compromising the brand register or the technical accuracy of the content, we meet them.
Klarvant is filing as a B Corporation in 2026. Accessibility is one of the impact areas we are assessed against. We treat this page as evidence, not as a one-off compliance artefact.
How we got here
Step 1
Every rendered page is reviewed against the WCAG 2.1 AA criteria. Colour contrast is computed from the brand colour tokens against actual surface backgrounds. Semantic landmarks, heading hierarchy, alt text, ARIA usage, keyboard reachability, focus order, and touch-target sizes are catalogued.
Step 2
Every finding rated Major or Critical is fixed before deploy. Findings rated Minor are queued and scheduled, not ignored. The remediation is committed alongside the page change, so the audit history and the fix history travel together.
Step 3
VoiceOver (macOS and iOS), NVDA (Windows), and keyboard-only walkthroughs run on every major page release. A human, not an automated tool, makes the call on whether the announced experience matches intent.
Step 4
The audit is rerun whenever a section is rewritten, whenever a new page ships, and on a six-month cadence regardless. New findings are filed, prioritised, and tracked the same way as any other engineering work.
Standards
Tell us
If any part of klarvant.com or Klarvant Namespace Command does not work for you with assistive technology, on keyboard, or at the zoom level you need, we want to know. Reports go to the accessibility team and are triaged within two working days. We will acknowledge receipt, explain what we will do, and tell you when.
Statement reviewed 24 May 2026. Next planned review: November 2026, or sooner if a major page rewrite ships.
