Our commitment
runline aims to meet WCAG 2.2 Level AA for public marketing pages and the signed-in workspace chrome (navigation, dialogs, and forms). We test with keyboard-only navigation, prefers-reduced-motion, and automated axe checks in CI.
Accessibility
Accessibility statement
How Runline Labs, Inc. approaches access on runline. Last updated 2026-10-17.
What we support
Skip link to main content, visible focus rings, 24×24 px minimum targets on chrome controls, focus-trapped auth and theme dialogs, Escape to dismiss, and reduced-motion honoured for decorative animation. In-text links are underlined. Colour contrast on public pages uses design tokens that meet AA for body text.
Known limits
Some dense creator surfaces (Quantify grid, notebook inspector, lab chat) still carry open accessibility work tracked in our gap ledger. Those areas may announce incorrectly to screen readers or expose small icon controls until follow-up fixes land. We do not claim full AA conformance for every workspace module today.
Feedback and alternatives
If you need an accessible alternative, hit a barrier, or want a remediation timeline, email support@runline.space. We aim to acknowledge accessibility requests within five business days.
Compatibility
Automated axe and keyboard checks run in CI on Chromium, on desktop and a 360 px mobile viewport, for the routes in our accessibility suite. Firefox, Safari, and screen readers (VoiceOver / NVDA) are not covered by automated tests.
Related: Privacy · Contact · support@runline.space