Accessibility | Respondyr Skip to main content
Accessibility

Accessibility at Respondyr

We want Respondyr to work for people using a screen reader, a keyboard on its own, or magnification. This page says what we are aiming for, what we check, and how to reach a person if something stops you.

What we are aiming for

Our target is WCAG 2.1 Level AA. We currently hold the public pages to it: this site, the blog, the legal pages, our landing pages, and the sign-in and sign-up pages on app.respondyr.com.

We claim partial conformance, not full conformance. We would rather understate that than round up.

What we have tested, and how often

Automated accessibility tests run in our build pipeline on every change to those pages. They use axe-core against the WCAG 2.1 A and AA rule sets, and a change that introduces even one violation fails the build.

Automated testing is a floor, not a finish line. It can confirm that a heading is a real heading, that a field is tied to its label, and that text clears the contrast minimum. It cannot tell you whether the page still makes sense read out in order.

The structure assistive technology depends on, meaning real headings, landmarks, labels tied to their fields, and alt text, is part of what those checks cover, so it is verified on every change rather than at the end of a project.

We have deliberately not installed an accessibility overlay widget. Those products promise a one-line fix, they are widely rejected by the disability community, and they have been the subject of accessibility complaints themselves. Fixing the pages is the only thing that actually helps.

If something blocks you, tell us

Email support@respondyr.com and tell us what happened.

It helps if you tell us the page you were on, what you were trying to do, and what got in the way. If you use assistive technology, naming it lets us reproduce the problem instead of guessing at it.

For questions about data and privacy rather than accessibility, use privacy@respondyr.com.

What we fixed most recently

Dated, so you can see what changed and when.

25 July 2026

  • Added a skip-to-content link and a main landmark to every public page.
  • Tied every form field to a label that assistive technology can read.
  • Raised light mode text to clear the 4.5 to 1 contrast minimum.
  • Gave every link, button, and form control a visible focus outline that meets contrast against its background.
  • Put automated WCAG 2.1 A and AA checks into the build for respondyr.com, the /leads landing page, and the sign-in and sign-up pages on app.respondyr.com.

Last reviewed 25 July 2026. Respondyr, Montrose, Colorado.