Accessibility

Accessibility commitment.

Horizont aims for a WCAG 2.2 AA baseline on every public surface, with explicit accommodations for cohort participation. We measure, we ratchet, and we publish when we fall short.

Last updated: 2026-05-12

The baseline

Every shipped route is audited against WCAG 2.2 Level AA. Specifically:

Keyboard navigability for all interactive elements — no mouse-only flows.
Visible focus indicators that meet 3:1 contrast against the focused control's surface.
Text contrast ≥ 4.5:1 for body, ≥ 3:1 for large headings and graphic objects.
Touch targets ≥ 24 × 24 CSS pixels (AA minimum) — tracked in CI with a per-route ratchet so regressions block merge.
Semantic HTML with explicit ARIA only where semantics fall short.
Layouts that survive 200% zoom and 400% reflow without losing content or functionality.

Where we currently fail AA, we hold a per-route ratchet so the failure count can only decrease over time. The ratchet is published in CI logs and treated as a debt to pay down — not a quota to live up to.

Cohort accommodations

Beyond the digital baseline, we offer accommodations for cohort participation. Tell us at enrollment (or any time after) and we'll coordinate with the educator.

Captions — every cohort recording ships with captions. Live sessions support real-time captioning on request.
Sign-language interpreters — available on request for in-person and Zoom sessions; we cover the cost.
Screen-reader-friendly materials — slides, code handouts, and reading lists are provided in plain-text or marked-up formats on request.
Campus physical access— the Athens campus is wheelchair-accessible across all teaching spaces. The fabrication and manufacturing bays have additional accessibility considerations — email us first and we'll walk through fit-for-purpose arrangements.
Extended deadlines + flexible attendance — case by case, decided by the educator with our backing.

Report something

If you hit an accessibility barrier — anywhere, on any product, in any flow — please tell us. We treat accessibility reports as bug reports with priority parity.

a11y@horizont.so— we respond within two business days, and we'll tell you what we're doing about it within five.

Known issues

We publish known accessibility issues in our public engineering backlog. The current Linear project "Agora Platform" includes a target-size audit ratchet ticket where individual route violations are tracked.

The baseline

Every shipped route is audited against WCAG 2.2 Level AA. Specifically:

Keyboard navigability for all interactive elements — no mouse-only flows.

Visible focus indicators that meet 3:1 contrast against the focused control's surface.

Text contrast ≥ 4.5:1 for body, ≥ 3:1 for large headings and graphic objects.

Touch targets ≥ 24 × 24 CSS pixels (AA minimum) — tracked in CI with a per-route ratchet so regressions block merge.

Semantic HTML with explicit ARIA only where semantics fall short.

Layouts that survive 200% zoom and 400% reflow without losing content or functionality.

Cohort accommodations

Beyond the digital baseline, we offer accommodations for cohort participation. Tell us at enrollment (or any time after) and we'll coordinate with the educator.

Captions — every cohort recording ships with captions. Live sessions support real-time captioning on request.

Sign-language interpreters — available on request for in-person and Zoom sessions; we cover the cost.

Screen-reader-friendly materials — slides, code handouts, and reading lists are provided in plain-text or marked-up formats on request.

Campus physical access— the Athens campus is wheelchair-accessible across all teaching spaces. The fabrication and manufacturing bays have additional accessibility considerations — email us first and we'll walk through fit-for-purpose arrangements.

Extended deadlines + flexible attendance — case by case, decided by the educator with our backing.