Skip to content

Accessibility statement

Last updated: May 25, 2026

CompletionKit is built to be usable by everyone who needs it. We aim for the hosted product, our marketing pages, and our docs to conform to WCAG 2.1 Level AA, the international baseline for web accessibility.

What we do

  • Every page declares a language, exposes a Skip-to-content link, and has a single <main> landmark so keyboard and screen-reader users can navigate quickly.
  • Form inputs have associated labels, sensible autocomplete hints, and a visible focus ring. Required fields are marked as such.
  • Interactive components rely on native semantics first. Where we add ARIA, we keep it consistent with the underlying behaviour.
  • Dynamic updates such as flash messages live in a persistent ARIA live region so assistive tech reliably announces them.
  • We respect prefers-reduced-motion: animations and reveal transitions wind down when the system setting is on.
  • We do not block zoom or pinch-to-zoom on any page.

What we know is still rough

  • Some text styled with our --ck-dim design token sits just below the AA contrast threshold on the dark background. A token-level fix is queued in the engine and will land in a forthcoming version.
  • The authenticated product surfaces (prompts, datasets, metrics, runs) are part of the open-source completion-kit engine. They are getting their own accessibility pass; tracked in the engine's issue tracker.
  • We do not yet run an automated accessibility audit on every PR. That step is being added now.

How to report an issue

Email accessibility@completionkit.com with:

  • The page or feature, including a URL if you can.
  • What you were trying to do, what happened, and what you expected to happen.
  • Your assistive technology and browser, if relevant.

We aim to acknowledge accessibility reports within 3 business days and to share a plan within 10. We treat regressions that block a user as production bugs, not backlog items.

Standards

This statement is informed by WCAG 2.1 Level AA and follows the spirit of the W3C accessibility statement guidance. We do not currently claim formal third-party certification.

We'd like to set Google Analytics cookies to measure aggregate, IP-anonymized traffic. We will not run them without your say-so. See our privacy policy for the full cookie list.