Access and inclusion
Accessibility at Varve
Varve is built for people who think visually, work across disciplines, and need their tools to meet them where they are. We treat keyboard access, readable contrast, predictable focus, responsive layouts, and honest product communication as part of the product—not a final polish pass.
Current status
We target WCAG 2.2 AA for the website and browser-facing interfaces. Varve is in public beta, and this page is an accessibility information statement—not a declaration of conformance, legal advice, or a substitute for an independent accessibility audit.
We have not completed a professional audit against ADA, Section 508, EN 301 549, or a platform-specific screen-reader certification. Please do not use this page as procurement or compliance evidence without an independent review of the version and workflow you intend to use.
What we currently support
- Keyboard navigation and visible focus treatment across the tested website paths.
- Light and dark themes with semantic color tokens and contrast checks.
- Reduced-motion preferences for website motion and decorative transitions.
- Responsive reflow from 320 CSS pixels through wide desktop layouts.
- Coarse-pointer target sizing for website controls and responsive editor surfaces.
- Accessible names, landmarks, status messaging, and keyboard alternatives around canvas workflows where available.
How we test
Our repeatable checks include automated axe scans, keyboard and focus-order flows, computed-style contrast checks, reduced-motion checks, responsive drawer behavior, and reflow at 320, 375, 430, 480, 600, 768, 900, 1280, and 1920 pixels. We also review light and dark visual snapshots for the website and selected editor surfaces.
The implementation and evidence record is maintained in the platform UX, accessibility, and responsiveness audit. See the keyboard shortcuts documentationfor the current keyboard command surface.
Known limitations
- Testing is currently English-first and does not establish RTL or translated-layout coverage.
- Automated checks and Linux Chromium testing do not replace NVDA, VoiceOver, TalkBack, or other assistive-technology testing.
- Emulated viewport and pointer checks do not replace testing on physical mobile hardware.
- Native desktop accessibility behavior still needs a dedicated cross-platform screen-reader pass.
- Design files and exported content created with Varve need their own accessibility review; authoring-tool checks do not make every output accessible.
Report an accessibility barrier
Tell us what you were trying to do, which version and platform you used, what happened, and what would have made the task possible. Please do not include private design files or personal information unless we ask for it through a secure channel.