Accessibility.

QualCanvas is committed to ensuring our software is accessible to researchers with disabilities. We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across all marketing pages and are actively working toward the same level in the canvas workspace.

Conformance level

Marketing pages (`/`, `/pricing`, `/methodology`, `/customers/*`, `/for-teams`, `/for-institutions`, `/trust*`, `/cite`, `/colophon`, `/changelog`, `/press`, `/accessibility-statement`): WCAG 2.2 Level AA targeted, regularly audited with axe-core and verified manually with NVDA on Windows and VoiceOver on macOS and iOS.

Known limitations

We name the gaps we know about rather than gloss over them:

• The canvas workspace itself has known keyboard-navigation gaps in zoom and pan controls. Workaround: keyboard shortcuts for code-application and codebook navigation are unaffected. Full canvas keyboard parity is targeted for Q3 2026.
• Some third-party embeds (Stripe checkout, GTM-loaded scripts) inherit their own accessibility profile, which we cannot fully control. We avoid third-party embeds on critical paths where possible.
• The interactive coding demo on the landing page is keyboard-navigable by design; the touch-selection variant on small screens uses native browser selection, which on iOS has its own ergonomic quirks.

Testing approach

We run axe-core via Playwright as part of CI, plus quarterly manual audits with NVDA (Windows), VoiceOver (macOS + iOS), and TalkBack (Android). The dev team uses keyboard-only navigation as part of normal development.

Feedback and contact

If you encounter an accessibility issue on QualCanvas, please tell us. We respond to accessibility reports within five business days and aim to fix critical-path issues within 30 days.

Email: [email protected]