Accessibility

We design and build the Quolens marketing site and product dashboard to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Where we fall short, we treat that as a defect and fix it in priority order with other product work.

As of September 2026, the public marketing site and the signed-in dashboard are intended to conform to WCAG 2.2 Level AA for the screens we ship and actively maintain. This is a living claim: new surfaces are reviewed as they land, and older gaps are closed as we find them.

We do not claim formal third-party certification. Conformance is based on our own testing (automated + keyboard + limited assistive technology review), documented below.

In scope:

• Marketing site pages (home, pricing, methodology, chat, legal).
• Product auth and dashboard surfaces (home, prompts, citations, competitors, sentiment, reports, actions, agents, settings, and related flows).
• Shared public views (evidence reading room, share links).

Out of scope or best-effort: third-party embeds we do not control, raw exported artifacts, and experimental or admin-only tools that are not part of the customer product.

• Automated checks with axe-core against WCAG 2.A / 2.AA / 2.1 / 2.2 AA rulesets on representative routes (light and dark where themed).
• Keyboard walkthroughs: skip link, nav order, modals (focus trap, Escape, focus return), command palette.
• Reflow / zoom: 320px width and approximately 200% page scale on home and pricing.
• Assistive-technology tree review (roles, names, headings, live regions) on login, Settings, Prompts, and Citations — not a full VoiceOver/NVDA certification pass.

Decorative controls (for example chevrons marked aria-hidden) and dense sticky chrome can still produce axe “incomplete” contrast notes that we review case by case. Some share and admin-only routes are thinner than the core dashboard. We do not yet run continuous AT regression in CI.

If something is hard or impossible to use, email accessibility@quolens.ai with the page URL, what you were trying to do, and the browser or assistive technology you use. We aim to acknowledge within a few business days and tell you when a fix ships.