Accessibility Statement

The site is built to meet Israeli Standard IS 5568, which adopts WCAG 2.0 level AA, under the Equal Rights for Persons with Disabilities (Accessibility Adjustments to Services) Regulations, 2013. The site is operated from Israel, so that is the framework it works to.

This statement describes what has actually been done and what has not. The site has not yet been audited by a certified accessibility surveyor, so we do not claim full conformance. We would rather say so plainly than display an approval that was never carried out.

The following checks run automatically across all 287 pages of the site on every change, and what they found was fixed:

• Document language — every page declares its language (lang) and text direction, so a screen reader pronounces the content in the right language. Correct on every page.
• Keyboard navigation — a "skip to main content" link is now the first focusable element on every page. Before this, a keyboard user had to traverse the entire navigation on every page.
• Form fields — every field now has an accessible name tied to it. The first pass fixed 44 fields whose visible text was not associated with the field; this one found a further 21 that relied on a placeholder alone — text that disappears the moment you start typing, and does not count as a name — and fixed those too.
• Images — every image on the site has alternative text.
• Semantic structure — the site uses landmark elements (main, nav, header, footer) and a heading hierarchy, so it can be navigated by region and by heading.
• Zoom and screen size — the layout responds to screen width and text enlargement without losing content or forcing horizontal scrolling.
• Icons — the site's icons are drawn from a ligature font, which meant a screen reader read the icon's name ("rocket_launch") aloud as part of the text. 8,309 icons are now hidden from the screen reader, and the 65 controls whose only content was an icon were given a readable name.
• Contrast — measured computationally for every combination of text colour, opacity and background in use on the site. All text meets at least 4.5:1 against the darkest and the lightest surface it can sit on. Around 19,000 colour declarations were changed as a result.
• Keyboard focus — every interactive element has a clearly visible focus indicator — a dark ring measuring at least 15:1 against every surface the site uses, and on a saturated button it is separated by a white halo that measures 7.2:1 against that button, so it stays distinguishable there too. This replaces the browser default, which is close to invisible.
• Mobile menu — when closed, the menu is now fully removed from the keyboard tab order; previously its links stayed reachable by Tab while invisible. The button reports whether it is open, and Escape closes the menu and returns focus to it.
• Reduced motion — if you have asked your operating system for fewer animations, the site's transitions are switched off.
• Accessibility menu — every page carries an accessibility button in the lower-right corner, opening a menu for text size (up to 160%, including the smallest labels on the site), link emphasis, stopping animations, and higher contrast. Your choices are stored on your device and carry across pages. It is ours rather than a third-party overlay: it changes the site's own styling and does not interfere with a screen reader or any other assistive software you already use. The button itself can also be hidden, from that same menu. It stays reachable two ways regardless: this page shows it even when hidden, and Alt+Shift+A brings it back from any page on the site.

An accessibility statement with no limitations in it is usually a statement nobody tested. These are the ones we know about:

• Third-party content — embedded video, advertising and other external components are not under our control, and their accessibility is determined by their provider.
• The contrast measurement is computed, not photographed — it derives the colour from the source, so it does not cover text painted with a gradient (329 instances, all of them large headings) and it does not measure the page as a browser actually renders it.
• An automated check is not a human one — these checks find what can be measured in the structure of a page. They cannot tell you whether a link's wording is clear, whether the reading order makes sense, or whether a task can be completed end to end with a screen reader. The site has not yet been tested by someone using assistive technology.
• Code and diagrams — code blocks and technical diagrams can be hard to follow in a screen reader. If you hit one, write to us and we will add a text description.

We fix what we find as we find it, and update this statement accordingly.

A report of an accessibility problem is handled ahead of anything else. It is the most useful message this site receives, because it points at something no automated check can find.

To let us act quickly, include the page address, what you were trying to do, and which assistive technology you were using, if any.