Accessibility Statement
How we make the Rahlio website and apps usable by everyone: the standard we work to, what we have done, how we checked it, what is not yet fully accessible, and how to reach our accessibility coordinator.
Last updated:
Operator details
- Trading name
- Rahlio
- Legal name
- Rahlio, Inc.
- File number
- 10824133
- Contact
- support@rahlio.com
Rahlio is operated by Rahlio, Inc. (Delaware file no. 10824133)
On this page
1. Our commitment
1.1. We believe everyone should be able to plan and book travel independently. We work to make the Rahlio website and apps accessible to people with disabilities, in accordance with the Equal Rights for Persons with Disabilities Law, 5758-1998, and the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013.
2. What this statement covers
2.1. This statement covers the website www.rahlio.com in English, Hebrew and Arabic — searching, hotel and flight pages, the checkout, finding and cancelling a booking, the account pages and these documents — and the Rahlio apps for iOS and Android. Rahlio serves its customers online, by email and by messaging; it does not receive the public at premises of its own.
3. The standard we work to
3.1. The website is built to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. That is the level the European standard EN 301 549 sets under the European Accessibility Act, which applies to booking services sold to travellers in the European Union, the level the US Department of Justice refers to under the Americans with Disabilities Act, and at least the level of the national standards that adopt WCAG 2.0 AA. The apps for iOS and Android are built to the same criteria.
4. Adjustments we have made
4.1. Among other things:
- The website and apps are available in Hebrew and Arabic, written right to left, and in English. Each page declares its language and reading direction, and a guest review shown in the language it was written in is marked as that language, so a screen reader reads it correctly.
- The website can be used with the keyboard alone. Every page with a header starts with a "Skip to content" link, the checkout included, and wherever the keyboard is, a clear outline shows it — in lists of suggestions too.
- Pages have one main heading, headings in order, and marked regions for the header, navigation, main content and footer.
- The destination and airport fields work as standard search lists: the arrow keys move through the suggestions, Enter chooses one and Escape closes the list.
- The date calendar can be used with the arrow keys, Page Up and Page Down (months) and Home and End (weeks). Each day is read out with its date and, where shown, its price.
- Windows that open over the page — the calendar, the guest picker, the photo viewer, the seat map, the confirmation windows and the concierge — move the keyboard into them, close with Escape, and return it to where it was.
- Text is at least 4.5 times as dark (or light) as its background, large text and controls at least 3 times; text written over photographs sits on a shade that keeps that contrast whatever the picture.
- Every form field has a visible label. When something is missing or wrong, the message says what was found, sits beside the field, is read out by screen readers, and the keyboard is taken to the message or to the first field to correct.
- Changes made by the page itself — results arriving, a price being updated, an error — are announced to screen readers without moving them from where they are.
- Meaningful images have a text alternative (a hotel photograph is named after the hotel); decorative ones are hidden from screen readers. Buttons that show only an icon have a name.
- The layout adapts to any screen without sideways scrolling, from a 320-pixel-wide phone to a large display, and text can be enlarged to 200% without loss of content.
- Buttons and links are at least 24 by 24 pixels, and most are 44 pixels or more on phones.
- The system setting to reduce motion is respected: animations, smooth scrolling and gliding maps are switched off.
- A result list fills in place, without replacing the page, and a loading indicator appears only when a wait is noticeable.
5. The apps
5.1. The apps follow the phone’s own accessibility settings. Text follows the size chosen on the phone, and the search screens and lists are checked at enlarged text in English, Hebrew and Arabic on narrow phones. Buttons and icons carry names for VoiceOver and TalkBack, every screen keeps a back button in the same place, and right-to-left languages are laid out as full mirrors.
6. How we checked
6.1. The main pages of the website — home, the search and its calendar and guest picker, the hotel and flight lists, a hotel page, the checkout, finding and cancelling a booking, the account, contact, a guide and these documents — are checked automatically with axe-core against the WCAG 2.0 and 2.1 level A and AA criteria, in English and Hebrew at phone and desktop widths. The check is part of the website’s automated tests, so a change that brings a serious problem back makes them fail.
6.2. We have also used every one of those pages with the keyboard alone, and checked the contrast of text over photographs by measuring the rendered page. The checks run in Chrome (desktop, and phone screen sizes).
6.3. We have not yet completed testing with screen readers on real devices — VoiceOver on iPhone and Mac, TalkBack on Android and NVDA on Windows — or with people who use them. That is our next step, and we welcome reports in the meantime.
7. Known limitations
7.1. Despite our efforts, some parts are not yet fully accessible:
- Hotel descriptions and photographs come from our Suppliers and the hotels. Some photographs have no description of their own, and some descriptions are available only in English.
- The card fields of the payment form are provided by the Supplier’s payment service in a secure frame inside our page, so their accessibility depends on that provider. If you have difficulty paying, contact us and we will help you complete the booking.
- Maps come from Google or OpenStreetMap and are an aid only: the same hotels are listed as text beside the map, and each hotel’s address and details are given as text on its page.
- Prices and seats are held only as long as the Supplier holds them — a flight fare for about 30 minutes — and that time cannot be extended. If you need more time, contact us and we will help you book.
- The PDF attached to a booking confirmation may not be fully accessible. The same information is available as an accessible web page through the link in the confirmation email.
7.2. We are working to remove these limitations.
8. Contact our accessibility coordinator
8.1. If you meet an accessibility barrier, or need information or a document in an accessible format, contact our accessibility coordinator by email at support@rahlio.com with the subject "Accessibility". You can also message us on WhatsApp, at the number on our contact page. Please tell us the page and what happened.
8.2. We reply to every accessibility request within 5 business days. A barrier reported to us is fixed as soon as possible, and we tell you when it has been; until then, we give you another way to receive the same service.
8.3. If a barrier prevents you from completing a booking on the website or in the app, contact us and we will help you complete it by email or WhatsApp, at the same price.
9. Date of this statement
9.1. This statement was first prepared on 24 September 2026 and last updated on 15 October 2026. It is reviewed whenever the website or the apps change significantly.