Skip to main content
flytuki
Subscribe

Accessibility statement

Last updated: 1 October 2026.

Our commitment

Tuki Fly should be usable by everyone, including people who use a screen reader, a keyboard only, magnification, or who need strong contrast. We treat accessibility as part of building the site, not as a fix we add later.

We aim to meet Israeli Standard IS 5568, which is based on WCAG 2.0 level AA, as required by the Equal Rights for Persons with Disabilities (Accessibility Adjustments for a Service) Regulations, 5773-2013.

What we have done

  • Semantic HTML: real headings, lists, tables and landmarks, so a screen reader can

announce the structure.

  • Full keyboard operation, with a visible focus outline and a skip link to the main

content.

  • Hebrew is served as a right-to-left page and English as left-to-right, with no

mirrored or reversed text, and prices, dates and addresses stay readable in both.

  • Text contrast that meets AA, and no information conveyed by colour alone.
  • The price history chart is also published as a data table, so the same information is

available without seeing the graph.

  • Data tables have captions and header cells, and every table says what it contains.
  • Text can be enlarged in the browser and the layout works at small widths, without a

horizontal scroll.

  • Form fields have real labels, and hints are linked to their field.
  • No automatic motion, no sound, no pop-ups and no content that flashes.

Known limits

  • The site is a work in progress and has not yet been through a full external

accessibility audit. We will update this statement after that audit.

  • Links to airlines, booking sites and official ticket sellers lead to systems we do not

control, so we cannot promise those pages are accessible.

  • Content that comes from third-party providers, such as an event title, arrives as they

wrote it.

Found a problem? Tell us

If something on the site blocks you, please write to us and say which page it was, what you were trying to do and what happened. Include the technology you use, if that helps.

  • Email: accessibility@eventflights.example
  • Accessibility coordinator: to be appointed before launch, with name and phone number

published here.

We will reply as soon as we can, and we treat an accessibility report as a bug with priority, not as a feature request.