Accessibility

Where we are

GateHog is a booking tool people use from a cab, often in bad light and in a hurry. The same things that make it usable then — real text, big targets, plain words, no motion you did not ask for — are what make it usable with a screen reader or at a larger text size. We treat them as the same job.

This page says what works today, on both the website and the iOS and Android apps. It also says what does not, because that is the half you can act on.

What works today

Screen readers

Every control is reachable and announces what it is and what it does — search, the yard list, the map pins, the term and spot-size choices, sign-in, the code field, and each step of checkout. Map pins read as the yard and its monthly rate rather than as an unlabelled marker. Checked with VoiceOver's own accessibility tree on iOS, screen by screen, and against the rendered page on the web.

Knowing what you have chosen

Billing term, spot size and the current tab announce as selected rather than relying on a colour change, so the thing you are about to be charged for is something you can confirm without seeing it.

Reduced motion

Turn on Reduce Motion (iOS), Remove animations (Android) or the equivalent browser setting, and the app and site stop animating. Content that would have faded or slid in simply appears — nothing is hidden as a side effect of the setting.

Contrast

Text and its background are checked against WCAG AA, and the check runs in our test suite rather than being a one-off review, so a colour change that breaks it fails the build.

Not colour alone

Status is always written as well as coloured — a chip says VERIFIED or DUE, it is not only green or amber.

Keyboard

The website is operable by keyboard, with a skip-to-content link as the first stop and a visible focus indicator on the controls you tab to.

Text size and zoom

The website does not block pinch-zoom and supports zoom to 500%. Body text has a minimum size in the apps, enforced by a test.

One-time codes

Sign-in is a texted code with no password. Your phone or browser can fill that code for you, so you do not have to leave the app, memorise six digits and come back.

Not there yet

Stated plainly, because knowing in advance is worth more than a promise:

Very large text in the apps

At the largest accessibility text sizes the Find screen becomes hard to use — the heading takes up the panel and the yard list is pushed out of reach. Ordinary large text is fine; the accessibility sizes are not, and we do not claim them. This is the next thing we are fixing.

Dark mode

The apps have a fixed appearance and do not follow your system light or dark setting.

Voice Control

The labels it relies on are in place and it will very likely work, but we have not tested it end to end, so we do not list it as supported.

The card step

Payment is handled inside Stripe's own secure form. We do not control its accessibility, and its behaviour is Stripe's to describe.

Yard photos

Photos are described by yard and position — "Tacoma, WA — photo 2 of 5" — not by what is in the picture. Useful for orientation, not a description of the site.

What we measure against

WCAG 2.2 Level AA is the target. We are not claiming full conformance: parts of the product have been measured against it and parts have not, and saying otherwise would be a claim we cannot back. The list above is what has actually been checked.

Checks that can be automated run in our test suite, so an accessibility fix cannot quietly regress later — including the contrast of every colour pair, a minimum body text size, and a rule that every animation honours Reduce Motion.

Tell us about a barrier

If something here stopped you, we want the specific thing rather than a general report — which screen, what you were using, and what happened. That is enough to reproduce it, and we would rather fix it than be told we are compliant.

We aim to reply within two business days. If a barrier is stopping you completing a booking, say so and we will take the booking over the phone in the meantime.