Accessibility Statement
How FlyTLV is built to be usable by everyone — the standard we work to, what is implemented, what is not yet good enough, and how to reach a person who can fix it.
1. Our Commitment to Accessibility
FlyTLV exists so that the price of a flight is not decided by how much time you can spend hunting for it, and a person's disability, assistive technology or choice of device should never be the reason they pay more. We therefore treat accessibility as a functional requirement of the product rather than a compliance exercise: it is considered when interface components are designed, checked when they are changed, and corrected when a barrier is reported. This statement sets out, in plain language and without overstatement, the standard we work to, what we have implemented, what we know is not yet good enough, and exactly how to reach a human being if something on this site stands between you and the information you came for.
2. Scope of This Statement
This statement applies to the FlyTLV website and installable web app served from flytlv.app, in both its English and its Hebrew version, and covers the public pages, the signed-in dashboard, the deal, package and saved-item surfaces, the interactive route map, the alert and notification screens, and the emails and in-app notifications we send. FlyTLV is an online-only service operated by aerocraft.dev from Tel Aviv, Israel; we do not operate offices, counters, branches or any other premises open to the public, so the physical and place-of-service accessibility provisions of the Israeli accessibility regulations do not apply to us. This statement does not cover airline websites, online travel agencies, search engines, payment pages or any other third-party destination reached through a link or booking hand-off from FlyTLV, which are addressed in clause 12.
3. Conformance Status
Our target is Level AA of the Web Content Accessibility Guidelines (WCAG) 2.2 published by the World Wide Web Consortium (W3C), which incorporates and extends WCAG 2.1 and WCAG 2.0 at the same level. In the W3C's own terminology, FlyTLV is currently partially conformant with WCAG 2.2 Level AA: most of the site meets the standard, but some parts, identified in clause 11, do not yet fully meet it. We deliberately do not claim full conformance. No independent third-party accessibility audit has been commissioned to date, and we take the view that a conformance claim with no published evaluation behind it is worth very little; the assessment behind this statement is our own and is described in clause 10.
4. Legal and Regulatory Framework
In Israel we work to Israeli Standard 5568 (IS 5568) for the accessibility of web content, which adopts the WCAG guidelines at Level AA and is given effect by the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013, made under the Equal Rights for Persons with Disabilities Law, 5758-1998. In the European Union we take account of the European Accessibility Act, Directive (EU) 2019/882, whose national implementing measures have applied since 28 June 2025, and of the harmonised European standard EN 301 549, which itself references WCAG at Level AA. For visitors in the United States, WCAG Level AA is the benchmark most commonly applied under the Americans with Disabilities Act and Section 508 of the Rehabilitation Act. FlyTLV is a micro-enterprise: we fall within the exemption the European Accessibility Act grants to businesses of our size, and we are below the threshold at which the Israeli Regulations require a business to appoint a dedicated accessibility coordinator. We apply these requirements voluntarily regardless, because being exempt from a rule is not a reason to build a product people cannot use. WCAG is the common denominator across all of these regimes, which is why it is the standard we measure ourselves against.
5. Accessibility Features Built Into the Interface
Implemented across the site: semantic HTML landmarks — header, main and footer — with a single logical heading order per page; every interactive control reachable and operable by keyboard alone, with a visible focus indicator, whether the browser's own focus ring or our focus styling on the site's button and tab components; dialogs and overlays, including flight details, package details, trend charts and the onboarding tour, that close on the Escape key as well as by pointer, through one shared implementation so that no overlay behaves differently from another; ARIA labelling on icon-only controls, and live regions that announce loading and result states which update without a page reload; colour palettes checked for contrast in both the light and the dark theme, with information never conveyed by colour alone; text that resizes without loss of content or function, with browser and pinch zoom deliberately left enabled up to five times rather than suppressed by a restrictive viewport declaration; a site-wide implementation of the operating system's reduce-motion preference, which stops the animated fare ticker, the scrolling marquee and every decorative transition; alternative text on informational images; and form fields with associated labels and inline, text-based validation messages.
6. Hebrew, Right-to-Left and Language Support
The site is genuinely bilingual rather than partially translated. Every page, its navigation, its metadata and its machine-readable structured data exist in English and in Hebrew, the document language is declared per page so that screen readers pronounce the content with the right voice, and the Hebrew version renders as a real right-to-left document whose direction is set at the document level rather than as mirrored English. Hebrew is served in a typeface drawn with Hebrew glyphs rather than falling back to whichever sans-serif the visitor's operating system happens to supply, so Hebrew text is legible at the same sizes as English. Dates, numbers and prices are formatted using the conventions of the active language, and country names are taken from the browser's own internationalisation data instead of a hand-maintained list that would go stale. Flight data itself — airline names, city names and three-letter IATA airport codes — stays in Latin script in both languages, matching the convention used by Israeli travel sites and by the airlines' own booking systems, so that what a screen reader reads out matches what is printed on the ticket.
7. The On-Page Accessibility Toolbar
FlyTLV loads an open-source accessibility toolbar, reachable from its own button on every page, which lets you adapt the site to your needs without changing your system settings: scaling text and spacing, switching to a high-contrast, inverted or desaturated colour scheme, applying a more readable or dyslexia-friendly typeface, highlighting links and headings, enlarging the cursor, showing a reading guide, suppressing animation, and listing the page's structure for navigation. Its interface follows the language of the page you are on. We want to be clear about what this toolbar is and is not: it is a convenience layered on top of the site's own accessibility, not a replacement for it. An overlay cannot repair markup that is inaccessible underneath it, we do not treat its presence as evidence of conformance with any standard, and nothing in clause 5 depends on it — the site is built to work with the toolbar switched off and with third-party scripts blocked.
8. Assistive Technology and Browser Compatibility
FlyTLV is built to work with current versions of the major browsers — Chrome, Edge, Firefox and Safari, on desktop and on mobile — and with the assistive technologies commonly used with them, including NVDA and JAWS on Windows, VoiceOver on macOS and iOS, TalkBack on Android, browser zoom and reader modes, operating-system high-contrast and larger-text settings, and speech-input and switch-access tools that depend on standard keyboard and focus behaviour. We do not claim formal certification against every combination of browser, operating system and assistive technology, and we do not test against browsers no longer supported by their own vendors. If a particular combination is failing you, telling us exactly which one, under clause 14, is the fastest route to a fix.
9. Technical Specifications
Accessibility of FlyTLV relies on HTML, WAI-ARIA, CSS and JavaScript, and on the accessibility features of your browser and assistive technology. FlyTLV is a JavaScript application: pages are rendered on our server and then made interactive in the browser, so the content of static pages — this statement, the privacy policy, the terms, the articles and the airport and airline reference pages — is present in the page source and readable with JavaScript disabled, while the signed-in dashboard, live search, filtering, alerts and the route map require JavaScript in order to function. We do not publish policies, notices or any other required information as a PDF or as an image of text; HTML is the accessible format and it is the only one we use.
10. How We Assess Accessibility
This statement is based on a self-evaluation carried out by the team that builds the site, combining automated checks — browser accessibility inspectors, and lint rules that fail the build on missing image alternatives and invalid ARIA — with manual testing: operating each surface using the keyboard alone, verifying focus order and focus visibility, checking contrast values in both themes against the WCAG thresholds, exercising the site zoomed and with reduced motion enabled, and reviewing every new interface component against the standard before it ships. Accessibility defects reported by visitors are handled as bugs, not as feature requests. No independent external audit has been commissioned to date; if and when one is, we will say so here and publish its date and scope.
11. Known Limitations
We would rather list these than let you find them. (a) The interactive route map is a third-party mapping library drawing geographic data onto a canvas; its controls are reachable, but the map as a whole is a poor experience with a screen reader, and the same routes and prices are available as text in the deals and packages lists. (b) The price-trend charts are visual by nature: the underlying figures appear as text in the flight and package details, but the charts themselves do not yet carry a full textual equivalent. (c) Parts of the Hebrew layout still position elements with physical left and right rules rather than logical start and end rules, so a small number of dropdown menus and side panels anchor to the wrong edge in right-to-left mode; this is a known and tracked migration. (d) The site does not yet offer a skip-to-content link, so a keyboard user passes through the header links on each page before reaching the main content. (e) Result lists load further pages as you scroll, which can be disorienting with a screen reader; the filters and the sort control are the reliable way to narrow a long list instead. (f) The Google Sign-In button is rendered by Google inside a frame whose markup we do not control. (g) Flight, airline and city data is collected automatically from external sources and occasionally contains a truncated, mis-cased or duplicated name that reads awkwardly aloud. Each of these is being worked on; where a fix depends on a third party we say so, rather than promise a date we do not control.
12. Third-Party Content and Onward Links
FlyTLV does not sell tickets. When you choose a deal we hand you over to an external booking site, most often Google Flights, and from there to an airline or an online travel agency. Those destinations, together with the analytics, tag-management and affiliate or advertising scripts that help fund the service, are operated by third parties whose code, markup and accessibility practices are outside our control, and we can make no representation or warranty about their conformance with any standard. We do not claim their accessibility as our own, and equally we do not disclaim responsibility for our side of the hand-off: the pages, links and information we present before you leave FlyTLV are ours and are covered by this statement. If a third party we link to presents you with a barrier, please tell us anyway — we can raise it with them, and where we have a choice of provider, accessibility is part of how we choose.
13. Alternative Means of Access
If any part of FlyTLV is inaccessible to you, you do not have to work around it on your own. Tell us what you were trying to do and we will provide the same information in another form — for example the full details of a specific deal, route or package, or the content of any policy page, supplied as plain readable text. This assistance is free, we will not ask you to prove anything about your disability, and we will not require you to install software, create an account or use a particular device in order to receive it.
14. Feedback and Reporting a Barrier
We welcome feedback on the accessibility of FlyTLV, and a report of something that does not work is more useful to us than a compliment. Please use the contact form on this website: it is our official and only channel, it reaches us directly, and we deliberately do not publish an email address anywhere on the site so that the mailbox behind that form stays usable by real people rather than buried under automated mail. It helps a great deal if you can include the address of the page, what you were trying to do, what happened instead, and the browser, device and assistive technology you were using. We aim to acknowledge accessibility reports within a few business days and to come back to you with either a fix or a plan and a realistic timeframe. Reports are handled directly by the people who operate and build the service; as noted in clause 4 we are below the size at which a dedicated accessibility coordinator must be appointed, which in practice means there is no queue between you and the person who can change the code.
15. Enforcement and Escalation
If you are not satisfied with our response you may escalate, and doing so does not affect any other legal right or remedy available to you. In Israel, complaints about the accessibility of a service may be brought to the Commission for Equal Rights of Persons with Disabilities at the Ministry of Justice, and the Equal Rights for Persons with Disabilities Law provides for civil remedies. In the European Union, the European Accessibility Act is enforced by a designated authority in each Member State and you may complain to the authority in your country of residence; equivalent routes exist in the United Kingdom under its equality legislation and in the United States under the Americans with Disabilities Act. We would still ask you to come to us first, under clause 14 — not to delay you, but because in almost every case we can change the code faster than any process can compel us to.
16. Review and Updates of This Statement
This statement is reviewed at least once a year, and again whenever a significant change is made to the interface, whenever a limitation listed in clause 11 is resolved, and whenever a new one is identified. The date below records the last review rather than merely the last edit: a review that finds nothing to change still moves it. The statement is published in English and in Hebrew and both versions are maintained together from a single source, so that neither language lags behind the other; if a discrepancy is ever found between them it is a defect, we would like to hear about it under clause 14, and in the meantime your rights under clauses 13 and 14 apply identically in both languages.
This statement was last reviewed on 07-08-2026.