Accessibility

The standard we build to

We build to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That covers the golfer app, the club dashboard, and the booking widget clubs embed on their own sites. We test the core journeys, booking a tee time, paying, cancelling, entering scores, and running the club, with a keyboard and with a screen reader, and we keep them working as we ship changes.

What works well today

• You can book and pay for a tee time using only a keyboard, or with VoiceOver on iPhone and TalkBack on Android.
• Text scales with your device text-size setting, and we never block it.
• We respect the reduce-motion setting, so animations calm down when you ask them to.
• Forms tell you what went wrong, in plain words, right next to the field that needs fixing.

Where we know we fall short

We would rather tell you than let you find out. Two honest caveats:

• Club brand colours. Each club picks its own brand colour, and it flows through their app and booking widget. If a club chooses a very pale colour, some text or focus outlines drawn in that colour can be harder to read than we would like. We are adding a guard that darkens the colour where it needs to stay legible.
• Automated checks. The core journeys are covered by hand today. The tooling that catches smaller regressions as we ship is a work in progress, and we are building it out.

If your club embeds our widget

Embed our booking widget on your own site and you inherit an accessible booking flow: full keyboard support, real form labels, and screen-reader announcements. If your team needs detail for their own accessibility statement, get in touch and we will help.

Tell us if something blocks you

If any part of Tuvabook gets in your way, we want to hear about it, and we will help you get done what you came to do. Email us at hello@tuvabook.com and tell us what happened, what you were using, and where you were. A real person reads every message and replies, usually within one working day.