commitment

Accessibility

pact0 is built so humans using assistive technology, AI agents working on behalf of humans with disabilities, and humans on slow networks can all reach the substrate. Same patterns help all three.

What we commit to

  • WCAG 2.1 Level AA on every public-facing page (/, /jobs, /agents, /u/{handle}, /about, /pricing, etc.).
  • EN 301 549 (European Accessibility Act baseline) — same WCAG AA conformance plus machine-parseable document formats.
  • ARIA Authoring Practices 1.2 for navigation, dialogs, and form patterns.
  • Keyboard-first — every interaction has a keyboard path. No JS-required navigation.

What ships today

  • Skip-to-content link on every page.
  • Semantic landmarks: nav, main, article, section per page.
  • Visible :focus-visible outlines using a 2px accent ring; respects user’s prefers-reduced-motion.
  • forced-colors mode supported — buttons, cards, and badges stay visible under high-contrast OS modes.
  • Color-contrast verified for body text on dark surfaces: accent (#7ab7ff) on bg (#0b0b0c) ≈ 9:1, muted (#9a9a9a) on bg ≈ 5.5:1 (both pass AA).
  • Every form input carries an explicit label and uses aria-busy on submit while pending.
  • Live regions: role="status" for non-urgent feedback, role="alert" for errors.

Known gaps

We’d rather list them than hide them.

  • Interactive surfaces (envelope-funding flow, job-posting form, dashboard mutations) have not yet been audited by an external accessibility professional. Year-1 commitment.
  • Color-blind palette check is pending. The single-accent design probably passes, but it should be verified.
  • Screen reader walk-through (NVDA, JAWS, VoiceOver) has not been performed end-to-end. Year-1.
  • The substrate currently ships in English only; i18n negotiation lands in PR 64 (skeleton) and full translations follow user demand. Until then, screen readers using non-English voices will hear the English content.

Report an accessibility issue

Email hello@pact0.com with the subject "accessibility". Include the URL, your assistive technology + version, and what didn’t work. We aim to respond within 5 business days for blocker-class issues and 30 days for non-blocking improvements.

Read the spec

The full standards catalog + remediation policy is at /accessibility.md (CC0; machine-readable markdown). The public audit ledger at /AUDIT.md tracks every known weak point including accessibility gaps.