Skip to main content

Accessibility

Last updated: September 2026

We would rather tell you exactly what works and what does not than claim a standard we have not been audited against. This page is the honest version, and the list of what is missing is the part worth reading.

Where we stand

We build to WCAG 2.2 Level AA. We have not been audited against it by anyone independent, and we do not publish a conformance claim, because we have not earned one yet. What follows is what we have actually checked and what we know is still missing.

What works today

  • Every page starts with a “Skip to main content” link, so keyboard users are not tabbing through the navigation on every page.
  • Keyboard focus is always visible. Every link, button and field has a focus ring — we do not remove outlines without replacing them.
  • Text colour contrast is measured, not eyeballed. Body text meets 4.5:1 against its background, and the ratios for our button and tag colours are pinned by tests that fail if a colour drifts below the threshold.
  • Colour is never the only way something is communicated. A “Soon” tag, a word, or an icon carries the same meaning as the colour does.
  • If your system asks for reduced motion, the animations turn off — not just slow down.
  • Images that carry meaning have alt text. Decorative ones are hidden from screen readers instead of being announced as noise.
  • Signing a contract on the web is done by typing your full name, not by drawing. Nothing in the web signing flow needs a mouse or a steady hand.

What does not work well yet

This list is specific on purpose. These are the things we know about and have not fixed.

  • The mobile app asks you to draw your signature with a finger. There is no typed alternative in the app yet, and if drawing is difficult for you, sign on the web instead — the signature is equally valid.
  • The “Get the app” dialog can be closed with Escape, but it does not yet trap focus, so tabbing past its last control can move you into the page behind it.
  • We have not tested every screen and screen-reader combination. Our coverage is best on the pages you are most likely to read, and thinnest inside the app’s job flows.
  • The interactive phone mockups on the homepage are illustrations. Some of what they show cannot be operated with a keyboard. No real task depends on them — everything they depict is done in the app or elsewhere on this site.
  • The site is in English. Two guides are available in Spanish; the product itself is not translated yet.
  • We have no VPAT or third-party audit report. If you need one for a procurement process, tell us and we will say honestly where we are rather than produce a document to order.

Telling us about a barrier

Email accessibility@fasthands.com, or call (747) 235-9933. It reaches a person, not a queue.

It helps to know the page or screen, what you were trying to do, and what you use — a screen reader and its version, keyboard only, magnification, voice control. If any of that is awkward to describe, send what you can; we would rather have a vague report than none.

We reply within two business days. If it is something we can fix quickly, we will say when it will ship. If it is not, we will tell you that instead of going quiet, and we will offer another way to do the thing you were trying to do.

If a barrier is stopping you from hiring a contractor or completing a job right now, say so and we will do that part with you directly — by phone or email — rather than making you wait for a fix.