Our standard
We target WCAG 2.1 Level AA. Every time we ship a new feature, we run it through the following checks before release:
- Keyboard navigation — every interactive element is reachable and operable without a mouse
- Screen reader compatibility — tested with VoiceOver on iOS and macOS, NVDA on Windows, and TalkBack on Android
- Color contrast — all body text meets a minimum 4.5:1 contrast ratio; large text meets 3:1
- Motion — users with reduced-motion preferences set in their OS see no animated transitions
- Zoom — layouts stay usable up to 200% browser zoom
- Touch targets — all tappable elements are at least 44×44 CSS pixels on mobile
Assistive technology
Our site is designed to work with the most common assistive technologies:
- Screen readers: VoiceOver (iOS, macOS), TalkBack (Android), NVDA (Windows), JAWS
- Voice control: Voice Control (macOS, iOS), Dragon NaturallySpeaking
- Magnifiers & browser zoom: ZoomText, native browser zoom up to 200%
- Switch navigation: iOS Switch Control and Android Switch Access
What we still need to improve
We don't pretend to be perfect. Known gaps we're actively working on:
- The 3D product renders are visual-only; we're adding spoken descriptions and a "View supplement facts" text alternative on every product card
- The Dr. Vital column will be available as an audio version starting Q3 2026
- Video testimonials currently lack captions — captions are being added over the coming weeks
- The Vital Protocol™ quiz needs better screen-reader labeling on its custom radio controls
Found a barrier?
If any part of Vital doesn't work for you — a button you can't reach, text you can't read, a form you can't fill out — please tell us. We treat accessibility issues as bugs, not feature requests, and we fix them.
Email accessibility@health-vital.com with a short description of what you were trying to do, what happened, and what assistive tech (if any) you were using. We aim to respond within 3 business days and ship a fix within 30 days for anything that blocks core shopping or account functionality.
Formal certification
We have not completed a formal third-party WCAG audit yet — we're working toward one in Q4 2026. In the meantime, we self-audit on every release using axe-core, Lighthouse, and manual screen-reader testing. The self-audit is not a substitute for certified conformance, and we'll update this page the moment we have it.