Accessibility

Accessibility statement.

VitaLog targets WCAG 2.2 Level AA conformance. We're not perfect, we're disclosing where we are, where we're not, and how to tell us we missed something.

Effective: 2026-05-06 · Reviewed quarterly · Last review: 2026-05-06

Standard

VitaLog is built to WCAG 2.2 Level AA as the conformance target. We use this standard because it is the basis of the EU Accessibility Act (Directive 2019/882, binding for consumer digital services in the EU since 28 June 2025), the equivalent Swedish DOS Act, and the US Section 508 baseline.

This is a statement of intent and current conformance, not a certification. We aim to be honest about where we still have work to do.

What we conform to today

Keyboard navigation: every primary action is reachable by Tab / Enter / Space. Focus trap on modals (auth, dialog confirms, onboarding wizard, first-run tour). Escape closes overlays.
Screen-reader support: semantic HTML throughout, ARIA labels on icon-only buttons, aria-live regions for tab changes, save status, rest-timer completion, and toasts.
Color contrast: text against background hits 4.5:1 (normal) / 3:1 (large) in both dark and light themes. The light-theme accent (#0a7a5f) was specifically chosen to clear 5.9:1 on white.
Touch targets: minimum 44×44 px on coarse pointers (WCAG 2.5.5). Dense controls in the rest-timer, auth-modal close, and floating action buttons all enforced.
Reduce-motion: every animation respects prefers-reduced-motion; an in-app override is also available for users on devices that don't expose the OS setting.
High-contrast mode: data-theme="high-contrast" ships as a Settings option with #fff-on-#000 + thicker focus rings.
Forms: explicit <label> per input, aria-describedby for error text, sensible autocomplete hints, inputmode on numeric/email fields.
Themed dialogs: every destructive action (delete, archive, ban, cancel) goes through a themed modal with focus trap, Escape support, and screen-reader announcement. Native window.confirm / prompt are gone from user-frequent paths.

Known gaps

Where we know we don't yet meet WCAG 2.2 AA, with target fix dates:

Charts & data visualizations: most charts (bloodwork trends, body-map heat, PK simulation) lack a tabular alternative. Screen-reader users can read the underlying values from the data tables but the visual encoding is not announced. Target: Q3 2026.
Drag-and-drop reordering: protocol cards and dashboard widgets support drag-to-reorder but no keyboard-accessible alternative. Target: Q2 2026.
Some tooltips: a small number of icon-only badges still rely on title-attribute tooltips that aren't reliably surfaced on touch devices. Target: rolling, as we encounter them.
PDF exports: generated PDFs (clinical summary, bloodwork report) are not yet tagged for screen readers. Target: Q4 2026.
Body-map SVG: the workout body-map is interactive but doesn't currently expose an accessible name for each muscle region beyond title. Target: Q2 2026.

If you've hit a gap that isn't on this list, please tell us, we'll add it.

Feedback & alternative formats

If you encounter an accessibility barrier, want content in a different format, or simply have a suggestion:

Email: accessibility@vitalog.io, we read every message and respond within 5 business days. Urgent issues (something blocking you from using the app) we treat as priority and respond within 48 hours.

What to include: the page or screen, what device + browser + assistive tech you're using, what you were trying to do, and what went wrong. Screenshots help, but a written description is fine, and reading them is the founder's job, not a chatbot.

If you're not satisfied with our response, you can escalate to Sweden's DIGG (the supervisory body for the Swedish DOS Act), or to your country's accessibility regulator.

Testing methodology

We use a combination of automated and manual testing:

Lighthouse + axe-core in CI on every build.
Manual keyboard-only walk-throughs of every primary flow on each release.
Screen-reader testing with NVDA (Windows + Firefox) and VoiceOver (macOS + Safari, iOS).
High-contrast and reduce-motion verification on Windows + macOS.
Touch-target audits with the device emulator at iPhone SE (smallest common viewport).

We do not currently use a paid third-party accessibility audit. As resources allow, we'll commission one.