Accessibility

We build BetterReply to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. That is the target we design and test against: readable contrast, a visible focus ring on everything you can reach with a keyboard, real labels on form fields, semantic headings, alt text on images that carry meaning, and support for zooming to 200% without losing content.

Honestly: partially conformant, and we would rather say that than claim a certificate we do not hold. We test the marketing site and the main product screens with automated tooling and with a keyboard. We have not completed a full third-party audit, and we have not tested every screen with every screen reader.

Two areas we already know are weaker. The video editor in Studio is a drag-heavy, timeline-based interface, and parts of it currently need a pointer. Some data tables and charts convey information visually that does not yet have a full text equivalent. Both are on the list rather than quietly ignored.

If something blocks you, email support@betterreply.com with “Accessibility” in the subject. Tell us the page and what happened, and include the browser and any assistive technology you use if you know it.

We will reply within 5 business days. If it is a real barrier we will tell you how we plan to fix it and roughly when, and if there is a way to get the same thing done in the meantime we will walk you through it. A person answers this, not a form.

Some parts of BetterReply are rendered by other companies, most visibly the Stripe payment form. We picked providers who take accessibility seriously, but we do not control their markup. If one of them is the barrier, tell us anyway: we will raise it with them and find you another way to get it done.