Skip to content
Mailcycle
Get started
Legal

Accessibility

Last reviewed 17 September 2026. This statement covers mailcycle.email and the web app at app.mailcycle.email.

1. What we aim for

We aim to meet WCAG 2.2 Level AA.

2. Where we are

Partially conformant. Every public page of this website, and the parts of the app you reach before signing in, pass automated testing against WCAG 2.2 A and AA with no violations. Automated tools catch only some accessibility problems, and no part of Mailcycle has yet been tested by a person using a screen reader, a switch device or voice control.

We have not commissioned an external audit. Section 5 lists what we know is untested or imperfect.

3. How it is tested

  • Every page of this website and the signed-out app screens are checked with axe-core against the WCAG 2.2 A and AA rules, in a real browser, on each release.
  • Colour and contrast are checked in both the light and dark themes.
  • Keyboard operation is checked by hand on the website: tab order, visible focus, and reaching anything that scrolls.
  • The app is built with React Native, so screens carry roles, labels and state that both the browser and the mobile screen readers read.

4. What is in place

  • Two ways to pair a device. Scanning a QR code needs a camera and steady aim; typing an eight-digit code needs neither, and reaches the same result. No part of Mailcycle can only be done by scanning.
  • The recovery phrase boxes are numbered to a screen reader, not only on screen, so the order is announced.
  • No time limit on pairing. A pairing code does not expire while it is being used.
  • Motion respects your system setting. With reduced motion turned on, animation and smooth scrolling stop.
  • Light and dark themes, both meeting contrast thresholds, following your system unless you choose.
  • Text scales with your browser or device setting, and the layout reflows down to a phone-sized window without a horizontal scroll.
  • Nothing depends on colour alone to convey status: device and payment states carry words as well.

5. Known limitations

  • The signed-in app has had less testing than the website. The dashboard, the mail reader and the settings screens are built from the same components as the tested screens, but they have not been through the same automated pass, and none of them has been tested with a screen reader.
  • Creating an account or signing in takes about 40 seconds while the key is derived on your device. There is a progress indication, and nothing times out, but it is a long wait.
  • Scanning a QR code is not usable without sight. The eight-digit code is offered beside it.
  • No testing with assistive technology yet, and no external audit. Both are planned.
  • The mobile apps are not published, so this statement does not cover them.

6. Mail from other people

Mailcycle shows you mail other people wrote. A message built as a single image, or with unlabelled links, may not be accessible, and we cannot change what was sent. We strip remote content, render a small and predictable subset of HTML, and keep the plain-text alternative available when the sender included one.

7. Telling us

If something here does not work for you, write to hello@mailcycle.email. Tell us the page or screen, what you were trying to do, and the browser, device or assistive technology you use. A person reads it.

We treat accessibility reports as faults. If we cannot fix something quickly, we will tell you and suggest what you can do in the meantime.

This statement is reviewed when the site or the app changes in a way that affects it, and the date at the top is the last time that happened. Our other policies are in the legal library.