Accessibility statement
We treat accessibility as part of the product rather than an addition to it. This page sets out what has been done, against which standard, what is not accessible yet, and how to report a problem.
The standard this site is built against
The site is built to IS 5568, which adopts the WCAG 2.0 guidelines at conformance level AA.
Conformance with a standard is not the same as certification. Certification is issued by a licensed service-accessibility consultant.
- Site operator
- An individual. The site is not operated by a company or a registered business.
- Last reviewed
- 2026-10-26
- Who carried out the accessibility review
- A licensed service-accessibility consultant is not required to approve a website under regulation 35.
What has been done
- The whole search and comparison journey can be completed with the keyboard alone, with a visible focus indicator on every control.
- An automated contrast test that fails if any text colour drops below a 4.5:1 ratio.
- axe-core run on every kind of page on the site, in Hebrew and English, including dialogs and states that only appear after an action, against WCAG 2.0/2.1/2.2 at levels A and AA.
- A control that receives focus is never hidden under the page header, including when moving backwards with Shift+Tab.
- Text stays readable and uncut when line, letter and word spacing are increased.
- Every page has its own title in the browser tab, including search results.
- The focus ring stands out from whatever is behind it (at least 3:1), on the dark ground and on the white cards that sit on it.
- What the first VoiceOver pass found is fixed: each discount on the home page has a heading and says how it is used, a sentence above the results says how many plans were found and in what order, and a link skips past the filters to the plans. A search with something missing says what, at the field, and moves the focus there.
- What the browser hands a screen reader along the search is checked automatically: choosing a destination and the number of plans found are announced, every plan has its own heading, and the buttons repeated on every plan say which plan they belong to. This checks the code; it is not listening with a screen reader.
- Usable at 320 pixels wide and at 200% text size, with no horizontal scrolling.
- Touch targets of at least 44 pixels on the main interactive controls.
- Modals built on the native <dialog> element, so focus trapping, Escape and background inertness come from the browser.
- The system preference for reduced motion is honoured.
- Semantic heading structure, an accessible name on every control, and text alternatives for non-text content.
What is not accessible yet
- The site has been tested with a screen reader only once so far: a first pass by the site's operator with VoiceOver on a Mac, in October 2026. It has not been tested with NVDA or JAWS or by people who use a screen reader every day, and in particular the reading of Hebrew text interleaved with numbers and English terms has not been checked in depth.
- The site has not been reviewed by a licensed accessibility consultant and has not been tested with disabled users.
- The site is under development, and parts of it are still changing.
Reporting an accessibility problem
Found something that is not accessible? We want to know — that report is the one that helps us fix it.
- Accessibility coordinator
- An accessibility coordinator is required of an organisation employing 25 people or more.
Last updated: 2026-10-26