Accessibility Statement

Last updated: 2026-08-03

Marginflow should be usable by people who navigate by keyboard, use a screen reader, enlarge text, or rely on high contrast. This page states plainly where we are, including what we have not yet done.

Standard we work to

We target WCAG 2.1 Level AA. We have not completed a formal third-party audit, so we do not claim conformance. Where we say something works, it is because we checked it in the running application.

What is in place

  • Every page declares its language, and that declaration follows the language you have selected — so a screen reader pronounces Korean content with a Korean voice rather than an English one.
  • A "Skip to content" link is the first thing you reach by keyboard on every page, so you do not have to tab through the navigation each time.
  • Pages use real landmarks (banner, navigation, main, contentinfo) and a heading structure, so screen reader users can jump between regions.
  • Interactive controls have accessible names, including icon-only buttons. Form fields are associated with labels rather than relying on placeholder text alone.
  • Dialogs, menus, tabs and other composite widgets are built on Radix UI primitives, which implement keyboard interaction and focus trapping.
  • Status messages after an action are announced through a live region rather than only appearing visually.
  • The interface honours your operating system's light or dark preference, and text reflows on zoom and on small screens.

Known gaps

These are real limitations, listed so you can judge whether Marginflow works for you before you rely on it:

  • Charts. The profit, margin and expense charts convey their information visually and are not yet exposed as text to assistive technology. Every view that contains a chart also offers an Export button producing the same figures as CSV, and the totals above each chart are plain text.
  • Colour contrast. We have not measured every text and background pairing across both themes. Secondary and helper text is the most likely to fall short.
  • Screen reader testing. We have not yet run a structured pass with NVDA, JAWS or VoiceOver. Our checks so far have been code-level and keyboard-level.
  • Some report sections use styled text where a heading would serve navigation better.
  • Shopify's own screens. Installation and billing happen on Shopify's pages, which we do not control.

If something blocks you, tell us

This matters more to us than the list above. If any part of Marginflow is unusable with your setup, email support@marginflow.uk with the page and what happened. It reaches the person who builds the product, not a ticket queue.

We aim to reply within 5 business days and to tell you either when a fix will ship or how to get the same result another way in the meantime. If we cannot fix something quickly, we will say so rather than leave it open.

Keeping this current

We review this page whenever we change the interface materially, and we update the gaps list as items are closed. It describes the version of Marginflow live on the date above.