Accessibility Statement

Last updated: September 21, 2026

Monarch is used by people sending follow-up after a conversation, and read by the people who receive it. This statement says what standard we are working towards, what we have actually measured, what we know is not right yet, and how to reach a person when something stops you.

Our target

We are working towards the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We do not claim to meet that standard today. This page is our own assessment: no independent accessibility auditor has reviewed Monarch, and nothing here is a certification.

What this statement covers

It covers the public pages on flymonarch.ai, and the pages on app.flymonarch.ai that can be reached without signing in: sign-in, sign-up, password reset, invitation acceptance, unsubscribe, and the published legal documents.

It does not cover the signed-in Monarch application, the one-pagers and PDF documents Monarch produces, or the email Monarch sends on a customer's behalf. We have not assessed those, so we make no claim about them here rather than one we cannot support.

How we measured

On September 21, 2026 we ran the axe-core 4.13.0 rule engine in Chromium against production builds of both applications: 25 pages, each at a 1280 by 900 desktop window and a 390 by 844 phone window, for 50 page checks in total. The rules applied were the WCAG 2.0 and WCAG 2.1 Level A and Level AA sets. We also applied the WCAG 2.2 Level AA rules, which reported nothing further. No element failed any rule.

The pass before it, on September 20, 2026, did find something. Nine pieces of small grey text across five pages sat on a near-white background at a contrast ratio between 3.47 and 4.35 to 1, where WCAG success criterion 1.4.3 asks for 4.5 to 1: the contact labels on our contact and security pages, the note beneath the demo request form, the note beneath the signup form, and the annual saving badge on the sign-up page in the app. All nine have been corrected. We have left the finding on this page rather than removing it, because a page that only ever shows a clean result gives you no way to judge how hard we looked.

What we found and have not yet fixed

Contrast we could not check automatically. Much of both sites is drawn on a gradient, and an automated tool cannot compute a contrast ratio against a gradient. At the desktop window it returned "needs review" for 34 elements on the public site and 475 on the app host. Those are not known failures. They are simply not machine-checked, and we have not yet reviewed them by hand.

An ambiguous description on the home page. The animated illustration on the home page carries its text description on an element that assistive technology is not required to announce, so a screen reader may read it or may pass over it.

Everything an automated tool cannot see. A rule engine reaches only part of WCAG. We have not run a screen reader audit, a keyboard-only walkthrough, or any session with people who use assistive technology, so we cannot yet tell you whether Monarch works that way. That work is not scheduled, and we would rather say so than let silence imply it is done.

Tell us what is blocking you

Email support@flymonarch.ai with the address of the page and what happened. We aim to reply within five business days. If something here stops you from doing business with us, tell us and we will find another way to get it done.

We revise this page when the findings above change. The date at the top is when it was last reviewed.