Add to Chrome
Accessibility

Accessibility Statement

Finding a good hotel price should be easy for everyone, including people who use a screen reader, a keyboard or a magnifier. This statement covers our website, hotel-ninja.com. It does not cover the Hotel Ninja Chrome extension.

The short version

  • This statement covers the hotel-ninja.com website only, not the Chrome extension.
  • Our target is WCAG 2.1 level AA, the international web accessibility standard.
  • That covers Israeli Standard IS 5568 and the European standard EN 301 549.
  • You can move through every page with a keyboard, with a clear focus outline.
  • Text colors meet the WCAG contrast ratio of at least 4.5:1.
  • We don’t use an accessibility overlay widget. We fix the site itself.
  • Found a problem? Tell our accessibility contact, Talia Klein Perez.
Last updated:

Our Commitment

We want everyone to be able to use hotel-ninja.com, whatever device, browser or assistive technology they use. Accessibility is part of how we design and build every page, not something we bolt on at the end.

Hotel Ninja is an online service. We have no physical premises open to the public.

What This Statement Covers

This statement covers the Hotel Ninja website at hotel-ninja.com: its pages, guides and contact form.

It does not cover the Hotel Ninja Chrome extension (the popup that shows prices while you browse booking sites). The extension has not been reviewed against these standards, and we make no accessibility claims about it. If you have trouble using the extension with a screen reader, a keyboard or other assistive technology, please tell us. Your feedback helps us decide what to improve.

Standards We Follow

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. Meeting this level also covers:

  • Israel: Israeli Standard IS 5568, required by the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013. IS 5568 is based on WCAG 2.0 level AA, and WCAG 2.1 AA includes every one of its requirements.
  • European Union: European standard EN 301 549, which the European Accessibility Act relies on and which uses WCAG 2.1 level AA for websites.

Conformance status (website): partially conformant. Most of the website meets WCAG 2.1 AA, and we are fixing the gaps listed under “Known Limitations” below.

What We’ve Done

  • A “Skip to content” link at the top of every page, so keyboard users can jump past the menu
  • Full keyboard navigation, with a visible focus outline on links, buttons and form fields
  • Text and background colors with a contrast ratio of at least 4.5:1, and at least 3:1 for form field borders and focus outlines
  • A clear heading structure (one main heading per page) and page landmarks for screen readers
  • Text alternatives for meaningful images, and decorative images hidden from screen readers
  • Labels on every form field in the contact form, with no time limits
  • Layouts that adapt to small screens and to browser zoom up to 200% without losing content
  • Moving content, like the scrolling price ticker, stops when your device is set to reduce motion
  • Breadcrumbs on every page, so you always know where you are
  • No accessibility overlay or plug-in widget. These tools don’t make a site compliant and often get in the way of screen reader users.

We check the site with automated contrast and code checks, and manually with a keyboard.

Known Limitations

  • The Chrome extension: not covered by this statement and not reviewed for accessibility (see “What This Statement Covers”).
  • Older guides: some images in older guides may not have full text descriptions yet. We are updating them.
  • Third-party content: the Chrome Web Store, booking sites and Google reCAPTCHA are run by other companies, and we can’t control their accessibility.

Accessibility Contact

If something on our website or in the extension is hard to use, or you need information in a different format, please tell us. We’d really like to fix it.

It helps if you tell us the page address, what you were trying to do, and the browser and assistive technology you use.

Spotted something we missed? We want to hear about it.

Contact us