Accessibility statement

What we do

These apply across the website, including the pricing, documentation and resources pages, and to the GoChatterBot chat you can open in the corner of every page.

• Keyboard navigation

  Every link, button and menu works from the keyboard. The Features menu opens with Enter or Space, the arrow keys move through it and Escape closes it. The mobile menu and the documentation menu keep focus inside while they are open, and Escape closes them and takes you back to the button you used.

• Skip link and visible focus

  The first Tab on every page shows a “Skip to main content” link that moves focus straight to the page content. Links and buttons show a clear outline while they have keyboard focus.

• Headings and landmarks

  Each page has one main heading and uses header, navigation, main and footer landmarks, so screen reader users can jump between sections. Breadcrumbs and the in-page contents in our documentation are labelled navigation.

• Text alternatives

  Photos have descriptive alt text. Decorative images and icons, and the small illustrated chat cards over photos, are hidden from screen readers so they don’t add noise.

• Color contrast

  Body text, links and buttons are well above the 4.5:1 contrast ratio for normal text: our main text is about 14.6:1 and our indigo links and buttons about 6.3:1. Some smaller grey labels are not there yet (see below).

• Reduced motion

  If you turn on “reduce motion” in your device settings, the site switches off its reveal and floating animations, the photo parallax and the menu transitions.

• Forms and error messages

  On the contact and sign-up forms every field has a visible label. If something needs fixing, the message is announced to screen readers and linked to its field, and focus moves to the first field that needs attention.

• The chat widget

  The chat button is a real button with a name screen readers read out. The chat window opens and closes from the keyboard (Escape closes it), focus moves into it and back to the button when you close it, the question box has a label, and each new answer is announced to screen readers. It follows the reduce-motion setting too.

Known limitations

We would rather tell you than have you find out. These are the issues we know about today:

• Some smaller grey text, such as the “/mo” after prices, dates on articles and password hints, is below the 4.5:1 contrast ratio. The “Accept” button on the cookie notice is just under it.
• Form fields show keyboard focus with a soft glow rather than an outline, which can be hard to see, especially with Windows high-contrast themes.
• Error messages on the sign-in and password-reset pages appear after the page reloads, but they are not announced to screen readers or linked to the field they are about.
• The animated chat example at the top of the home page is read out by screen readers as a conversation, and its message bubbles only respond to a mouse.
• Some decorative animations keep looping and have no pause button unless “reduce motion” is turned on.
• In the documentation, pressing the “/” key jumps to the search box, and this shortcut can’t be turned off.
• On larger screens the chat window stays open beside the page rather than taking over the screen, so keyboard focus is not held inside it (on phones it is).
• The contact and sign-up forms use Cloudflare Turnstile to stop spam. It is a third-party check, so its accessibility is outside our control. If it stops you, email us and we’ll help.
• Chat answers are written by AI from our published pages. They can occasionally be incomplete, so each one links to the page it came from.

Tell us about a problem

If something on this site doesn’t work for you, please let us know. It helps to include the page address, what you were trying to do, and the browser and any assistive technology you use.

A person reads every accessibility report. We aim to reply within a few business days, and if we can’t fix something quickly, we’ll help you get the information or finish the task another way.