Accessibility

Accessibility

Last reviewed 11 August 2026

Our target

We build to WCAG 2.2 level AA. That covers keyboard access, focus visibility, contrast, motion preferences and screen reader semantics across the public site, the traveller dashboard and the designer console.

What is in place today

  • Every interactive control is reachable and operable by keyboard, with a visible focus ring
  • Minimum 44 by 44 pixel tap targets on touch screens
  • Semantic landmarks and labelled icon-only controls
  • Dark and light themes both tested for text contrast
  • Accordions and expandable itineraries work with JavaScript disabled

Known gaps

The quote builder tables in the designer console are dense and still being reworked for screen reader order. Trip videos do not yet carry captions.

Accessible trip planning

Tell your designer what you need and it goes on the trip file: step-free rooms, accessible transfers, dietary needs, quiet pacing, medical storage.

Still have a question?
A senior designer replies in about 47 minutes on weekdays.
Tell us about a barrier