Skip to main content
C
ConvertKit

Accessibility Statement

Last updated: October 2026

Our commitment

ConvertKit wants everyone to be able to use our free tools. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, and we treat accessibility as a product requirement, not an afterthought.

What we have done

  • Text and UI colors checked for WCAG AA contrast (4.5:1 body text)
  • Every control reachable and operable by keyboard, with visible focus
  • All meaningful images carry alternative text; decorative icons are hidden from screen readers
  • Form fields are programmatically labelled, with clear error messages announced to assistive tech
  • Semantic headings, landmarks, and a page language for screen-reader navigation
  • Animation respects the operating system’s reduced-motion setting
  • Layouts reflow and remain usable at 200% zoom and on small screens
  • Automated accessibility checks (axe) in the end-to-end suite, plus manual keyboard checks on key flows

Known limitations

  • Advertisements served by Google AdSense are controlled by advertisers; we cannot guarantee every ad creative meets WCAG, and we do not ask you to interact with ads.
  • Preview panes render your documents and PDFs; inaccessible content in your source file stays inaccessible in the preview.
  • Some very dense tool panels (batch queues with many files) are still being reviewed for full screen-reader announcement of progress updates.

Need help or hit a barrier?

If any part of ConvertKit is hard to use, tell us — we would rather fix it than have you struggle. Reach us through the contact form and describe the page, what happened, and which browser or assistive technology you use. We aim to respond within a few business days.

Standards we follow

WCAG 2.2 Level AA · Section 508 principles · EN 301 549 expectations for public-facing websites. This statement is reviewed whenever we ship major changes to the tools.