Accessibility statement

We work hard to provide a great experience for everyone who uses the things we make. That includes people with disabilities.

Generally we follow WCAG 2.1 as a baseline standard for accessibility. There's a big difference, however, between making it possible to use a website or product, and making it actually easy to use.

If you can technically navigate an app with a screenreader but it takes hours to complete even basic tasks, how accessible is that really? (Answer: It's not). That's why we put a lot of energy into making it simple to use our products, no matter how you interact with them.

Here is a brief overview of some of the steps we take to make our offerings useful for everyone:

  • Make sure that color contrast is adequate for all text, use larger text sizes for copy, do not interfer with zooming/magnification
  • Avoid color as the only indicator of status (e.g. error messages)
  • Provide a consistent and easy experience for keyboard users and screen readers via skip links, hotkeys, semantic HTML, ARIA attributes, labeling, and careful focus management, among other measures.
  • Honor "prefers reduced motion" settings
  • Include accessibility standards as part of our standard QA testing process

Web application accessibility is complex (that's part of why it's usually pretty bad), so we never consider the job "finished."

If you notice a usability issue on our website or in any of our products, please let us know! Even if a problem is small or just an annoyance we want to hear about it.

We can't guarantee we'll be able to implement every request or smooth over all sources of friction, but we take your feedback seriously. Most of the improvements we make and features we add come directly from user requests.

Bug reports and suggestions should be sent to

Ready to get started?

Create a free account