Accessibility

Accessibility statement

Our target is WCAG 2.2 AA. This page says honestly what's in place, what we know is not there yet, and how to reach us when something doesn't work for you — an accurate list beats a silent badge.

In place today

  • Keyboard operability across the marketing pages and every editor menu and dialog, with visible focus and Escape-to-close behaviour that also returns focus to whatever triggered it.
  • Labelled form controls throughout the invoice editor, including icon-only buttons carrying accessible names.
  • Contrast-checked colour tokens in both light and dark themes for status and warning surfaces, including small-text badges over their own tinted backgrounds — not just the base accent colours, which read fine at large sizes but can fail as small text.
  • Reduced-motion preferences respected — animations and highlights switch to static styles.
  • Responsive layouts down to small phones (375px) without horizontal scrolling, with the same actions available at every size.
  • Semantic headings and a real page heading on every route.

Known gaps

  • A formal, page-by-page WCAG 2.2 AA audit has not been completed yet — the statement above reflects engineering practice, not certification. The audit is planned work.
  • Generated PDFs contain real selectable text but are not tagged PDF/UA documents; screen-reader navigation inside the downloaded PDF is limited.
  • Screen-reader flows through the full invoice-creation journey have had only basic verification so far.
  • Opening a dialog doesn't move focus into it or trap Tab inside it while open — Escape and the close button work, but a keyboard user can still Tab to page content behind an open panel.
  • The homepage's interactive brand-colour preview offers five accent choices; the small initials tile stays high-contrast for some of them but not all when a non-default colour is selected — it's a decorative preview, not the product's real invoice output, but we're naming it rather than leaving it silent.

Tell us what's broken

If something on this site doesn't work with your equipment or setup, we want to know: [email protected]. Describe what you were trying to do and what happened; real reports move directly into the work queue.

This statement was last reviewed on 20 July 2026.