Skip to content
Mailcycle
Get started
Legal

Accessibility

Last reviewed 1 October 2026. This statement covers mailcycle.email, the developer documentation at docs.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, every page of the developer documentation, and every screen of the app, signed out and signed in, passes automated testing against WCAG 2.2 A and AA with no violations, in both themes and at both a phone and a desktop width.

Automated tools catch only some accessibility problems. No part of Mailcycle has yet been tested by a person using a screen reader, a switch device or voice control. Section 5 lists what we know is untested or imperfect.

3. How it is tested

  • Every page of this website, every page of the documentation and every screen of the app is checked with axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rules, in a real browser, on each release. The signed-in screens are checked signed in, against a real account.
  • Each page is checked twice in each theme and twice again at a phone width and a desktop width, because contrast and layout differ between them.
  • 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.
  • Every screen has a name, in the browser tab and in the page history, and a heading structure you can navigate by rather than a flat run of text.
  • A skip link at the top of the app steps over the navigation, and the sidebar, the screen and the tab bar are marked as regions a screen reader can jump between.
  • Nothing needs a drag. Swiping a message to reveal Trash also works with a long press, and with the keyboard, which opens the row as it reaches the button.
  • The keyboard is always visible. Whatever is focused carries a ring drawn in two colours, so it stays visible on a pale card and a dark one.
  • Every control is at least 24 by 24. Small icons, checkboxes and copy buttons sit in a target that size even where the icon is drawn smaller.
  • The tablet apps rotate. On a tablet nothing is locked to portrait, so one fixed in a landscape mount still works. On a phone the apps stay upright.

5. Known limitations

  • The mail reader has had less testing than the rest. Reading a message and writing one are checked by the same rules as everything else, but a mailbox with real mail in it has more shapes than an empty one, and we have not been through all of them.
  • 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.
  • 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 support@mailcycle.email. Tell us the page or screen, what you were trying to do, and the browser, device or assistive technology you use.

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.