Accessibility

Last updated · September 23, 2026

AxionLabs wants Turnexify to work for everyone who sells time and everyone who books it. This statement says what that means in practice, where we know we fall short, and how to tell us when you find something we missed.

What we aim for

The Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, across this site, the dashboard that businesses use, and every public booking page we host. That is the standard we build against and test against, not a standard we claim to have finished meeting.

What is done

Colour contrast is measured, not guessed. Every text colour on this site clears 4.5:1 against its background, and two of the brand’s own colours were darkened to get there.
Everything works from a keyboard. Menus open on focus, close on Escape, and the focus ring is visible on every control.
Motion respects the operating system. With “reduce motion” on, animations are turned off rather than slowed.
Forms use native controls with real labels, so screen readers and password managers understand them. Errors are written next to the field they belong to.
Decorative drawings are hidden from assistive technology, and the ones that carry meaning have a text description.
Text scales. Nothing is locked to a pixel size, and the layout holds at 200% zoom.
Every page is available in English and Spanish, including the booking flow and the emails it sends.

Where we know we fall short

The map on a business’s contact page is drawn by a third-party library and is not fully operable by keyboard. The address beside it is text, and a link opens the same place in your own map application.
Card payments happen on pages and card fields hosted by Stripe or Square, whichever the business uses. We chose both partly for their accessibility work, but those pages and fields are theirs and we cannot change them.
Photographs uploaded by a business carry the descriptions the business wrote. We prompt for one and cannot guarantee its quality.
The blog is new, and we have not yet tested every post with a screen reader.

How we test

Automated checks run on every change. Beyond that we test by hand with a keyboard alone, with VoiceOver on macOS and iOS, and with the browser zoomed to 200%. When a business reports a problem, we add its case to that list.

Tell us what we missed

If any part of Turnexify is hard or impossible for you to use, write to hello@turnexify.com or use the contact page and pick “Something else”. Say what you were trying to do, what happened, and what you were using. A person reads every message, and we reply within one business day.