Skip to the content

Legal

Accessibility statement

The short version sits on top; the binding version follows it. Both are the same rules.

The short version

How we build this site to be usable, and how to tell us when it is not.

What we aim for

This site is built to WCAG 2.1 level AA. We adopted that target regardless of whether an exemption applies to a company of our size, because the alternative is deciding that some of our guests are somebody else’s problem.

Whether we may formally claim conformance is a question for our legal advisers and is not yet answered. The build does not wait for that answer.

What that means in practice

Every page is server-rendered, so it works before any script does. Focus is always visible. Every control can be reached and used from a keyboard, and the whole booking path — choosing, cart, checkout, confirmation, ticket — is tested that way by a person, not only by a tool.

Nothing on this site is communicated by colour alone. Where content changes under you — a line removed from your cart, a total recalculated — it is announced rather than merely redrawn.

Motion is switched off entirely if your system asks for reduced motion.

What we know is imperfect

Automated testing catches a minority of accessibility problems. We run it on every build and we also do a keyboard pass by hand, and we still expect you to find things we have not.

Telling us

If any part of this site is difficult or impossible for you to use, write to us or send a WhatsApp message and say what happened. A person reads it. We would rather hear about it than have you go elsewhere quietly.

Terms version in force today: 0.1-provisional · Questions go to the desk — a person answers.