Accessibility

What is in place

• Semantic HTML throughout, with one h1 per page and a logical heading order.
• A skip link to the main content as the first focusable element.
• Visible focus indicators on every interactive element, never removed.
• Full keyboard operation, including the search autocomplete (an ARIA 1.2 combobox that supports arrow keys, Enter and Escape, and does not act on keys pressed while an input method is composing text).
• Save buttons on hotel cards are real buttons beside the card link, not nested inside it, and their outcome (“Saved”, “Trip is full”) is announced to screen readers.
• Text contrast of at least 4.5:1 against its background in both the light and the dark colour scheme, which follows your system setting. We run an automated axe-core check over the home, search, city, country, hotel, trip, brand, collection, contact and not-found pages at desktop and phone widths, in both colour schemes; it currently reports no violations. Automated checks catch only part of the problem, so this is a floor, not a claim of full conformance.
• On touch screens, buttons, form controls, the menu, breadcrumb and footer links and text-style buttons are at least 44px tall.
• Status conveyed by text as well as colour — a confirmed fact says “Confirmed” and one we only rate likely says “Likely”, not just green or amber.
• Reduced-motion support: animation and smooth scrolling are disabled when the system requests it.
• Form fields with real labels, and errors announced in text rather than colour alone.
• Pages that read without JavaScript: the content is rendered on the server, search falls back to a normal form submission, and the header links show inline instead of behind the menu button. Filtering a city, country or brand list, saving hotels to a trip and the confirmation forms do need it.

Known gaps

• Wide data tables (the hotel page’s detail tables and the trip comparison) scroll horizontally on small screens. Each scroll container is keyboard-reachable and named, and the trip comparison keeps its row labels in view, but a wide table is still a difficult experience on a phone.
• Traveller-submitted photos will rely on submitters for alt text, which we cannot guarantee is descriptive. Moderation reviews it, but this is a real limitation.

Tell us

If something here does not work with your assistive technology, please tell us — including what you were using. Accessibility bugs go to the front of the queue.