Accessibility statement

Our commitment

We want this site to be usable by everyone — including people using a screen reader, a keyboard only, enlarged text, or a small screen. We treat accessibility as part of the site’s quality, not as something bolted on at the end.

Accessibility work does not finish at launch. New pages and new content are checked from this angle too, and hearing from someone who ran into a problem is the most useful information we can get.

We do not claim here to meet a standard, or to hold an accessibility certification or approval. An approved statement will be published only after a professional review.

How the site is built to be used

Pages are built from real text rather than pictures of text, so it can be enlarged, copied, and read out by a screen reader.

Headings follow a hierarchy, so a screen reader user can jump between parts of a page instead of reading it from the top each time. Images that carry meaning have a text description; images that are purely decorative are not announced.

The site works in Hebrew right-to-left and in English left-to-right, with the writing direction and page language declared on every page — so a screen reader pronounces the content in the right language and direction.

Text is sized in units that let the browser enlarge it without content being cut off, and the layout is intended to work on a narrow screen and on a phone. Wide content such as a table scrolls within itself rather than pushing the page sideways.

Keyboard access

The site can be operated with a keyboard alone: Tab moves to the next element, Shift+Tab goes back, Enter or Space activates a link or button, and Escape closes a menu or dialog that has opened.

The element that has focus is marked visibly, and the tab order follows the reading order of the page rather than jumping between parts of it.

Each page has a skip link at the top that goes straight to the main content, so you do not have to travel through the whole navigation on every page.

We do not trap focus: dialogs and menus are built to be operable from the keyboard from.

Reporting a problem

If you hit a page, a form or a file you cannot use, please tell us. Reports like that are not a nuisance — they are how this gets better.

To let us act quickly, it helps to say: which page it happened on, what you were trying to do, and what you are using — the name of your screen reader, your browser, or that you are working from the keyboard only.

Reports reach our accessibility coordinator, whose details appear on this page. You can also use any of the other contact channels on the site and it will be passed on.

We will look into it promptly and get back to you. If a fix will take time, we will offer another way to get the information or the service in the meantime.

Known limitations

This statement describes what the site is intended to provide. Before it is published as final, the pages need to be tested in practice, and the results will be recorded here — including anything found that has not yet been fixed.

Content produced with external tools, such as PDF files or videos, may not be fully accessible. If you come across such content, we will provide the information another way on request.

Content displayed on the site from a third-party service is not entirely under our control, so its accessibility may differ from the rest of the site.

This statement covers the public website. The application behind the sign-in is a professional working environment and its accessibility is assessed separately; findings about it will not be reported on this page.

Last updated and who to contact

The date this statement was last updated, the date of the professional review, and the accessibility coordinator’s details are shown on this page.

The statement will be updated after a material change to the site, after each review, and after handling a report that pointed to a broader problem.

While the update date and the coordinator’s details are missing, this statement is incomplete and must not be published as final.