LinearPilot

Accessibility Statement

Last updated: August 24, 2026

What we are working toward

We build LinearPilot to meet WCAG 2.2 Level AA. That is a target we design and review against, not a certification we hold. This page says what is already true, what is not yet, and how to tell us when we have got it wrong — so you can judge for yourself instead of taking a badge on trust.

What is already in place

These are behaviours you can check on any page:

  • Every page opens with a link that lets you skip straight to the main content, so a keyboard or screen-reader user does not walk the navigation each time.
  • If your system asks for reduced motion, we stop the motion. Backgrounds and animated illustrations render still rather than looping.
  • Pages are built from real landmarks and heading order, so assistive technology can jump between regions instead of reading top to bottom.
  • Keyboard focus stays visible. You can see where you are without a mouse, and interactive elements are reachable in a sensible order.
  • The product ships in eight languages and announces the language of the page, so your screen reader reads it with the right voice and pronunciation.
  • Colour is defined once as a token set that carries both light and dark themes, so contrast is decided in one place rather than page by page.

Where we fall short today

We would rather name these than have you discover them:

  • LinearPilot has not been audited by an independent third party, and we hold no accessibility certification. Our reviews are our own.
  • We publish no screen-reader and browser support matrix. We have not tested every screen in every combination, and we will not imply that we have.
  • The first HTML we serve begins in English; your language is applied as the page becomes interactive. On a slow connection a screen reader can start reading in the wrong voice.
  • Nothing checks accessibility automatically when we change the code. Our reviews are done by hand, which means they are as uneven as any manual process.

Parts we do not control

Some things you reach from LinearPilot are built by other companies — the Stripe checkout that takes your payment details, and any site we link to. We cannot fix their accessibility and we will not take credit or blame for it. If you hit a barrier there, tell us anyway and we will help you reach the people who can act on it.

Tell us about a barrier

If something here is hard or impossible to use, we want the report. It is the most useful accessibility signal we get, and it is more reliable than our own review.

Include what you can:

  • The address of the page, or where in the product you were
  • What you were trying to do
  • Your assistive technology, browser and operating system

We answer within five business days. If a fix will take longer than that, we will tell you what we are doing and offer a way to get the same thing done in the meantime.

Another format

If you need information from any page here in a different format, ask and we will send it.

Contact

Accessibility questions and reports go to [email protected].