Last reviewed: 26 October 2026

This statement covers the Zitlin booking engine: the pages guests use to search dates, choose a room, enter their details and request a booking directly with a hotel (addresses under /pub/engine/), and the hotel directory under /pub/hotels/. It is published to meet the information requirements of the European Accessibility Act (Directive (EU) 2019/882), as transposed in each EU member state.

The hotel staff apps (Android, iOS, macOS, Windows and app.zitlin.com) are business software and outside the scope of this statement.

What the service does

The booking engine lets a guest book a room directly with a hotel, without an online travel agency in between. A booking takes four steps:

Dates: choose check-in and check-out dates and the number of guests.
Select room: see the available room types with their total price, including taxes.
Your details: enter your name, email, phone and address.
Payment or review: see a summary of the booking and, if the hotel asks for an advance, pay it by scanning a QR code, using the payment details shown, or a payment link. Then request the booking.

The hotel confirms the booking by email. Nothing is charged by Zitlin.

Standard we aim for

We aim for WCAG 2.1 level AA, the level the harmonised European standard EN 301 549 requires for web content.

Compliance status

The booking engine is partially conformant with WCAG 2.1 AA. We assessed it ourselves; it has not yet been independently audited.

What is in place:

Every page works without JavaScript, and the whole flow can be completed with a keyboard alone.
Every form field has a visible label and the correct autocomplete purpose, so browsers and assistive technology can fill it in.
When a form has errors, a summary at the top lists each one with a link to its field, receives focus, and is announced by screen readers. Each field's error is linked to the field itself.
The progress indicator tells screen readers which step you are on and which are complete.
Text and form controls meet the AA contrast minimums, and keyboard focus is always visible.
Your room is held for 30 minutes. Five minutes before the hold ends you are warned and can extend it as many times as you need.
Animation is switched off when your device asks for reduced motion.
Payment details have labelled copy buttons, and the QR code can be saved as an image, so a guest booking on their phone can scan it from their payment app's gallery.
Fonts and styles are served from Zitlin's own servers, not from third parties.

Known limitations

Content supplied by hotels. Photo descriptions, room names and policy text are written by each hotel. Some hotel photos may not have a meaningful text description.
Payment apps. QR codes and payment links open banking or payment apps (for example UPI apps or PayPal) that Zitlin does not control. The payment details (UPI ID or bank account, amount and reference) are shown as text next to the QR code, so paying never depends on scanning it.
Bot check. The guest details step may show a Cloudflare Turnstile check. It usually completes without any interaction; if it does not work for you, contact the hotel directly using the phone number or email shown at the bottom of every page.
Language. The booking engine is currently available in English only.
Restaurant menu and invoice pages linked from some hotels' pages have not yet been through this review.

Feedback and contact

If you meet a barrier on any booking page, or need the information in a different format, email [email protected] with the page address and what went wrong. We aim to reply within 5 working days. You can always book by contacting the hotel directly instead; their phone number and email are at the bottom of every booking page.

Enforcement

If you are not satisfied with our response, you can contact the authority responsible for the European Accessibility Act in your country. In Ireland, that is the Competition and Consumer Protection Commission (CCPC), ccpc.ie.