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 were run across all 285 pages of the site, 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. Previously 44 fields had visible text that was not associated with the field, and a screen reader announced them as unnamed boxes.
• 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.
• Contrast — the site uses a dark palette chosen for sustained reading.

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.
• Contrast has not been measured exhaustively — the palette was chosen for readability, but the contrast ratio of every individual component has not been systematically measured.
• Older pages — the site was built over time, and earlier pages may still carry problems the checks run so far did not catch.
• 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.