Skip to main content
mailpitcher
FeaturesPricingBlogAboutLog inJoin the waitlist
  • Features→
  • Pricing→
  • Blog→
  • About→
  • Connectors→
  • Help center→
  • Free tools→
  • Contact→
  • Log in→
Join the waitlist
Terms of ServicePrivacy PolicyAcceptable UseData Processing AddendumAccessibility

Accessibility statement

Last reviewed 14 October 2026

We want everyone to be able to use Mailpitcher, including people who use a keyboard instead of a mouse, a screen reader, zoom or high-contrast settings. This statement covers this website (mailpitcher.com) and the Mailpitcher web app.

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We are not there everywhere yet, so we describe the website and the app as partially conformant: most of it meets the standard, and the exceptions we know about are listed below.

What we have done

  • Everything can be reached and used with a keyboard. Menus, tabs and option groups answer the arrow keys, dialogs keep focus inside and give it back when they close, and every control shows where the focus is.
  • Each page on this site starts with a "Skip to main content" link.
  • Text meets the 4.5:1 contrast ratio on this site, and in the app in light and dark with each of its built-in colour schemes.
  • Form fields have labels, and errors say what to fix next to the field they belong to.
  • Animation stops when your device asks for reduced motion, and the moving logo row on the home page has a Pause button.
  • The app's own keyboard shortcuts (J, K, C, R and others) work only in the mail list. They never fire while you type, or inside menus and dialogs.

Known limitations

  • Small selection checkboxes in the inbox. The checkbox on each conversation row is smaller than the 24 by 24 pixel target WCAG 2.2 asks for. You can also select the open conversation with the X key, or everything at once with Select above the list.
  • Emails from other people. We show incoming emails as their senders wrote them. If a sender leaves out image descriptions or uses colours that are hard to read, we can't fix that for them.
  • The project board's drag and drop. Moving a prospect by dragging needs a mouse or touch. With a keyboard, open the prospect and pick its stage instead: it does the same thing.
  • Screen reader testing. We test with automated checks and a keyboard-only walkthrough on every main screen. We have not yet done a full review with each major screen reader, so you may find rough edges there. Please tell us.
  • Custom colours. If you pick your own colours in Settings, the app adjusts text colours to stay readable, but we can't check every combination you might choose.
  • Third-party parts. The security check on our forms (Cloudflare Turnstile) and the Google, Microsoft and other provider pages our setup guides send you to are outside our control.

How we test

We run automated axe-core checks against the WCAG 2.2 A and AA rules on the pages of this site and on each screen of the app, in light and dark. We also walk through the site and the app using only the keyboard. We repeat both before larger releases and update this page when the results change.

Tell us about a barrier

If something on this site or in the app is hard or impossible for you to use, email hello@mailpitcher.com or use the contact form. Tell us the page or screen, what you were trying to do, and the browser and assistive technology you use if you can. We read every message and aim to reply within a few working days. If you need something from us in another format, ask and we will do what we can.

mailpitcher© 2026 Mailpitcher

Product

FeaturesPricingConnectorsFree tools

Resources

Help centerBlog

Company

AboutContact

Legal

TermsPrivacyAcceptable useDPAAccessibilityCookie settings

Cookies for analytics?

We'd like to use Google Analytics cookies to see which pages people read, and one cookie of our own that remembers where you first came from (like a search engine or a link), so we know which channels work. Nothing is loaded from Google or stored unless you accept. Details.