Accessibility Statement

We work to make the site accessible to all users, including people with disabilities, and to enable independent, comfortable use of all the professional content published on it.

The site is built to aim for conformance with WCAG 2.1 level AA, in line with the Israeli Standard 5568 and the accessibility regulations under the Equal Rights for Persons with Disabilities Law.

The measures below were reviewed by our development team against the WCAG 2.1 AA guidelines. An external certified accessibility audit has not yet been performed, so we do not present an auditor's approval or certificate number.

• Semantic structure: a single H1 per page, a consistent heading hierarchy, and landmark regions (header, nav, main, footer).
• Full keyboard navigation, including dropdown menus, accordions and forms, with a visible focus indicator.
• A skip-to-content link at the start of every page.
• Color contrast ratios adapted for regular and large text against the site's dark background.
• Forms with linked labels, textual error messages and an aria-live region for status updates.
• Alt text for meaningful images; decorative illustrations hidden from screen readers.
• Full support for RTL Hebrew layout and LTR layout on other-language pages.
• Respecting the prefers-reduced-motion setting and reducing animation accordingly.
• Responsive layout that holds up at up to 200% text zoom without loss of content or horizontal scrolling.
• Article and FAQ content is rendered server-side and accessible to screen readers even without JavaScript.

Despite our efforts, some components may not be fully accessible — mainly complex diagrams whose visual information is summarized in accompanying text, and content in non-Hebrew languages that has been machine-translated and may contain imprecise wording. We continue to address these gaps on an ongoing basis.

The site is tested on current versions of Chrome, Edge, Firefox and Safari, on desktop and mobile. Use of older browsers or older versions of assistive technology may affect the user experience.

Found a component that isn't accessible? We'd like to know. A request submitted via the contact page will be handled promptly, and we will respond with details of the fix or an accessible alternative for obtaining the information.

Accessibility requests are handled by the person responsible on our team, via the contact form. If an accessible alternative for obtaining information from the site is required, we will provide it through a channel convenient for you.