Accessibility

Last reviewed 1 September 2026

TextCatch is built and run by a small team, and we want it to work for every contractor who needs it — including people who use a screen reader, navigate by keyboard only, rely on high contrast or magnification, or use voice control. This page says plainly what we build to, what we have actually checked, what we know is not right yet, and how to reach a person if something on our site or in our app gets in your way.

The standard we build to

We target WCAG 2.1 Level AA — the Web Content Accessibility Guidelines published by the W3C — across both textcatch.withapexai.com and the customer app at app.textcatch.withapexai.com. That is the benchmark most commonly applied to commercial websites in the United States, and it is the one we measure ourselves against.

We want to be straight with you rather than impressive: we do not claim full conformance. A claim like that is easy to print and hard to earn, and we would rather tell you where we actually stand. We test, we fix what we find, and we list the open items below.

What we have checked

Both properties are audited with automated tooling and by hand — keyboard-only walkthroughs of the real sign-in and setup screens, colour contrast measured against the pixels the browser actually paints rather than against the palette on paper, and a review of the browser's own accessibility tree to confirm that every control reports a real name and role to assistive technology. The most recent pass covered:

• Every page reachable without signing in, plus the main admin and customer screens behind sign-in.
• Light and dark colour schemes, since the app follows your system setting.
• Desktop, phone-width, and a 320 px viewport, to confirm the page reflows without forcing you to scroll sideways.

Things that pass today and that we intend to keep passing: text contrast on the marketing site and across the app's screens, visible keyboard focus on interactive controls, alternative text on images, a skip-to-content link and page landmarks, form fields with real labels attached to them, and headings in a sensible order.

Known issues we are working on

As of the date above, these are the accessibility problems we know about and have not finished fixing:

• Input borders in the app are too faint. The outline around text fields, dropdowns and checkboxes does not meet the 3:1 contrast that WCAG 1.4.11 asks for against the background behind it. Fields are still labelled, still reachable by keyboard, and still show a clear focus ring when selected — but the resting outline is lighter than it should be. Fixing it changes how every form in the product looks, so we are making that change deliberately rather than quickly.
• We have not had an independent accessibility audit by a third party, and we have not tested every screen reader and browser combination in real-world use. Our testing so far is our own.

Fixed in the most recent pass, listed here so you can see this page is maintained rather than decorative: form fields in several admin screens that had a visible label but did not report it to a screen reader; a status badge that measured just under the required contrast; a keyboard focus stop with no visible outline; and the missing page landmarks and skip links that made keyboard navigation slower than it needed to be.

We list these because a page that admits nothing is not worth reading. If you hit something that is not on this list, we would genuinely like to know — see below.

Third-party parts of the experience

Some steps use services we do not control and cannot fix directly: consultation booking runs through Cal.com, and card payments run through Stripe. If either of those blocks you, contact us and we will complete the step with you another way. You will not be turned away because a third-party screen did not work for you.

Tell us if something blocks you

If you already have an account, raise it as a support ticket from inside your dashboard — that's the fastest way to reach us and puts it in writing. If you don't have an account yet, book a call with us and tell us what blocked you. Either way, tell us what page you were on, what you were trying to do, and what you use to browse (screen reader, keyboard only, magnification, voice control) if you are comfortable sharing it.

We aim to reply within five business days. If we cannot fix the underlying problem quickly, we will tell you honestly how long it will take and give you a way to get the same thing done in the meantime — a person will help you complete it directly.

How we keep this current

We re-run the accessibility checks above when we ship meaningful changes to either property, and we review this page at least every six months. When we fix something on the known-issues list, it comes off the list and the review date changes.

This page describes real, current behaviour — the issues listed above were found by testing the live site and app, not copied from a template — and it is a statement of our commitment and practice, not a legal representation of conformance. It is not legal advice.