Accessibility statement

Translated: 12 November 2026 · Hebrew version updated: 8 November 2026

Yaron Meiri, Adv. & CPA works to make the site accessible to the whole public, including people with disabilities. The law, regulations and standard on which this statement is based are listed in the Sources section at the end of the page.

The statement covers every page of the site, in Hebrew, English, Arabic and French. This English text is a translation of the Hebrew statement, and the Hebrew text governs.

The standard and the conformance level

Regulation 35A of the Regulations requires internet services to be made accessible under Israeli Standard SI 5568, at level AA. The current edition of SI 5568 Part 1 (“Web content accessibility guidelines: accessibility of websites”) is from September 2023. It is based on the W3C’s WCAG guidelines, with national changes and additions, and replaces the May 2021 edition. Accessibility of digital documents, such as PDF files, is dealt with in Part 2 of the standard.

Conformance level: the site meets the requirements of SI 5568 Part 1 (September 2023) at level AA partially. The known exceptions are listed in the Known limitations section.

Accessibility adjustments made on the site

• Semantic structure (headings, navigation and content regions, lists and tables) and WAI-ARIA attributes, intended to allow the use of screen readers and other assistive technologies.
• Full navigation by keyboard alone, including a “skip to main content” link (in some guides: “skip to content”).
• Clear, visible focus indicators on every interactive element.
• Color contrast at level AA (a minimum contrast ratio of 4.5:1 for normal text).
• Consistent navigation menu: the items appear in the same order on every page of the site in the same language, except one landing page for paid advertising.
• Form fields are labeled with labels linked to the fields. A form error message is read out, the field in error is marked, and focus moves to it.
• Text alternatives (alt) for images. Decorative icons in menus, links and buttons are hidden from screen readers.
• A hierarchical heading structure, except in the references section of the service pages, where the items of the collapsible list are at the same heading level as the section heading.
• The language of every page is set in the code, and so is the writing direction (RTL/LTR), in Hebrew, English, Arabic and French.
• Text can be enlarged up to 200% without loss of content. On short screens, for example when the display is zoomed, the top bar and the contact bar are not fixed to the screen. The exceptions are listed in the “Known limitations” section.
• Data tables on the pages in the sitemap are marked up with header cells (for columns, and in some tables also for rows), and have a caption that screen readers read out.
• Links that open in a new tab, and links to PDF files, are marked as such for screen readers.
• The accessibility menu opens and closes from the keyboard too, including with the Escape key. When it opens, focus moves into the menu and stays there; when it closes, focus returns to the button that opened it. The state of each button in the menu (on or off) is exposed to screen readers.
• The navigation menu on phones: when it opens, focus moves into the menu and stays in it and in the top bar, and the page content behind it is hidden from screen readers until the menu closes. The Escape key closes it, and focus returns to the menu button.

The accessibility menu

Every page has an accessibility button (“נגישות” on Hebrew pages, “Accessibility” on English pages, “إتاحة” on Arabic pages and “Accessibilité” on French pages; the menu is shown in the language of the page) that opens a menu of display settings, including larger and smaller text, spacing, a readable font, highlighted links, stopped animations and contrast modes. The menu is an optional aid: the site is built to be accessible without it, and you can use your browser’s and operating system’s accessibility settings instead. The settings you choose are stored only in your browser (localStorage) and are not sent anywhere. On phones and narrow screens, the button is hidden while the inquiry form is on screen or one of its fields has focus, so that it does not cover the form fields; it comes back when you scroll past the form, and it is not hidden while the menu is open.

Accessibility checks

Log of the site’s accessibility checks

Date	What was checked and what was found
11 Nov 2026	Check of the site’s French pages: axe-core 4.14.0, against the WCAG 2.0, 2.1 and 2.2 rules at levels A and AA, 53 French pages (home, contact, service pages, calculators, 20 guides, information hubs and law pages, frequently asked questions, glossary, tools, about, the privacy policy, the terms of use, this statement and the error page), at 390 and 1366 pixels wide: 0 violations. Also checked with the keyboard, at the same widths, and found to work correctly: switching languages (in the top bar and in the navigation menu on phones), the inquiry form, the skip link, and the accessibility menu in French: it opens and closes from the keyboard, focus stays inside it, and all its labels are in French.
11 Nov 2026	Check of the site’s English and Arabic pages: axe-core 4.14, against the WCAG 2.0, 2.1 and 2.2 rules at levels A and AA, 36 English pages and 36 Arabic pages (home, service pages, guides, information hubs and law pages, frequently asked questions, glossary, tools, contact, about, the privacy policy, the terms of use, this statement and the error page), at 390 and 1366 pixels wide. Found in the first run and fixed: the language switcher and some links whose accessible name did not include the visible text (WCAG 2.5.3), and a small touch target on the Arabic home page (WCAG 2.5.8). The repeat run: 0 violations. Switching languages with the keyboard and correct right-to-left and left-to-right display were also checked.
08 Nov 2026	Check after the site update: axe-core 4.14.0, against the WCAG 2.0, 2.1 and 2.2 rules at levels A and AA, 23 representative pages (home, service pages, contact, about, guides, English pages, the privacy policy, the terms of use, this statement and the error page), at 390 and 1280 pixels wide: 0 violations. The references section of the service pages, which became a collapsible list, was checked in particular: each item has a button inside a heading that tells a screen reader whether the item is open. The Enter and Space keys open and close it, focus is marked, and a direct link to an item opens it.
26 Oct 2026	Keyboard checks and checks in Chromium’s accessibility tree: the navigation menu on phones on every page of the site (390 pixels) and in tablet mode. Found and fixed: with the menu open, the Tab key moved to the page content behind it. Also fixed: English labels for the accessibility menu on English pages, and language marking of English names and source titles on Hebrew pages. axe-core: 0 violations, also with the menu open.
26 Oct 2026	Automated check with axe-core 4.14.0 against the WCAG 2.0, 2.1 and 2.2 rules at levels A and AA on every page of the site, at 390 and 1280 pixels wide, and scripted checks: text contrast on a gradient background, keyboard navigation and focus marking, language of parts of the text, text enlarged to 200%, text spacing, 320 pixels wide and high-contrast mode. Found and fixed: the accessible name of the call button in the bottom bar; the contrast of the update line at the top of the privacy policy; horizontal scrolling on one decision page at 320 pixels; answers cut off in the frequently asked questions when text was enlarged, on two pages; English links marked as Hebrew; bottom-bar links that received focus while the bar was hidden; the state of the inquiry-channel buttons; arrows in the links of the “about the author” box. 22 tables are now shown on phones as one card per row.
04 Oct 2026	Automated check with axe-core against the WCAG 2.0, 2.1 and 2.2 rules at levels A and AA (including target size), on every page in the sitemap and the error page, at 390 and 1440 pixels wide, and also in the form’s error and confirmation states, in the navigation menu on phones and with the accessibility menu open: no violations found. A focused check with the keyboard, with zoom at 200% and 400% and at 320 pixels wide: no loss of content found. The frequently-asked-question buttons on the pages on canceling a subscription were found not to tell screen readers whether the answer was open; the defect was fixed in that update.
01 Oct 2026	A repeat check after the site update: automated check with axe-core 4.13.0, against the WCAG 2.0, 2.1 and 2.2 rules at levels A and AA, of every page in the sitemap, at 390 and 1440 pixels wide. No violations found. In addition, text enlarged to 200% was checked on every Hebrew page in the sitemap, at 390 and 1280 pixels wide, and no loss of content was found. The exceptions are listed in the “Known limitations” section.
01 Oct 2026	Focused checks in the browser, with test scripts: keyboard navigation and focus marking, the skip link, forms and error messages, text enlarged to 200%, zoom up to 400%, high-contrast mode (forced colors), the navigation menu on phones and the accessibility menu. Defects were found, among them a different order of the top menu items between page types, loss of content at 200% text size on some pages, and the state of buttons in the accessibility menu not being exposed to screen readers. The defects were dealt with in the site update of 1 October 2026; what was not dealt with is listed in the “Known limitations” section.
01 Oct 2026	Automated check with axe-core 4.13.0, against the WCAG 2.0, 2.1 and 2.2 rules at levels A and AA, of every page in the sitemap and a sample of 60 archive pages, at 390 and 1440 pixels wide. No violations of WCAG rules found. Lighthouse gave an accessibility score of 100 in all 60 runs, on 10 representative pages, on phone and desktop.
29 Sep 2026	Automated check with axe-core, against the WCAG 2.0 and 2.1 rules at levels A and AA, of every page in the sitemap, in phone and desktop views. No violations found.

The checks were run on behalf of the firm with axe-core, Lighthouse and test scripts in the Chromium browser. No check has yet been made by an accessibility tester using assistive technology (a screen reader).

An automated check finds only some accessibility problems, so it does not replace a manual check.

Known limitations

• Screen readers: a full manual check with a screen reader (for example NVDA or VoiceOver) has not yet been carried out.
• The article archive: the site has older articles that are not shown in search engines. They were included in the automated check, but not in a manual check.
• PDF files: three decisions of the Chairman of the Central Elections Committee for the 26th Knesset are also available as PDF files. The decisions were prepared by the Elections Committee and not by the firm (see regulation 35B of the Regulations). The files have a text layer, tagging, a language setting and a document title, but they have not been checked against SI 5568 Part 2. The main points of each decision appear as text on its page on the site, and you can ask for the information in another accessible way.
• External services: WhatsApp, Google Maps and Waze, and documents on other sites that the site links to (for example PDF files of the Knesset and of government ministries), are not under the firm’s control.
• Wide tables: on phones most wide tables are shown as one card per row, with the column name above each value. A few tables are still wider than the screen and scroll sideways inside a frame. They can also be scrolled with the keyboard.

Accessible service: contact channels and adjustments on request

• You can get in touch in writing, without a voice call: by WhatsApp message to +972-50-431-3155, by email or with the inquiry form on the site.
• You can call +972-50-431-3155 during office hours: Sunday to Thursday, 9:00 to 18:00.
• The first conversation can take place by phone or in writing on WhatsApp.
• If you need another adjustment to the service, for example in the way information or documents are given to you, or in the arrangements for a meeting, say so when you get in touch, and I will arrange the adjustment with you in advance.

Physical accessibility of the office

The office operates in a shared workspace at 2 HaSdera HaAkademit St., Kiryat Ono. The office is accessible to people with disabilities.

Need an adjustment for a meeting? Say so when you arrange it, and I will arrange it with you in advance. The conversation can also take place by phone or in writing on WhatsApp. Further details of the accessibility arrangements at the premises are given on request.

Reporting an accessibility problem

Found an accessibility problem on the site, or have a suggestion for improvement? Use the details in the “Accessibility contact” section below. So that I can deal with it quickly, give the address of the page, what you tried to do and what did not work, and, if you used assistive technology (for example a screen reader), which one. You can also make a demand for correction under regulation 35A(d)(1) of the Regulations. Under that regulation, a reported defect must be corrected within a reasonable time, and no later than 60 days after the notice is received.

I will get back to you within one business day of receiving your inquiry. Yaron Meiri, Adv. & CPA undertakes to correct reported accessibility problems within 30 working days. Until a problem is corrected, I will find another way with you to get the information or the service, for example by phone, on WhatsApp or by email. The site is checked periodically (at least once a quarter), and its accessibility is updated as the site and the standards change.

Accessibility contact

Sources

• Equal Rights for Persons with Disabilities Law, 5758-1998 (in Hebrew).
• Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013 (in Hebrew): regulations 34, 35 to 35F and 91. The statement is published under regulations 34 and 35E.
• Israeli Standard SI 5568 Part 1 (September 2023), “Web content accessibility guidelines: accessibility of websites”, Standards Institution of Israel.

Updates to this statement

The date this statement was last updated is shown at the top of the page. The accessibility statement is reviewed and updated periodically, as the site and the requirements of the standard change.