Accessibility statement

Built to WCAG 2.2 level AA

This site is built to meet the Web Content Accessibility Guidelines (WCAG, the international rules for accessible websites) version 2.2, level AA. WCAG 2.2 builds on WCAG 2.0, so this target also covers Israeli Standard SI 5568 (ת"י 5568), which is based on WCAG 2.0 level AA (SI 5568 part 1, September 2023, PDF in Hebrew).

That’s the target and a description of the work done. It isn’t a certificate from an outside auditor.

In Israel, accessibility statements are governed by regulation 35ה of the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013. The Hebrew version is written for that requirement and follows the guidance of Israel’s Commission for Equal Rights of Persons with Disabilities (in Hebrew).

What was done so the site works for more people

• Real structure. Headings, lists, page regions (header, main content, footer) and real buttons, so assistive technology can follow the page.
• Keyboard. Every link, button and form field can be reached and used with a keyboard. The focused element gets a clearly visible outline.
• Skip links. “Skip to content” and “Accessibility statement” at the top of every page. They appear when you press Tab.
• Contrast. Text and controls are designed for sufficient contrast in both the light and the dark theme. The button in the header switches themes; without a choice, the site follows your device setting.
• Text alternatives. Images have text descriptions. Decorative graphics are hidden from assistive technology.
• No video or audio. So no captions or transcripts are needed.
• Reduced motion. If your device asks for reduced motion, animations are off and you see a static version with the same information.
• Language and direction. Each page declares its language and text direction, and the language switch links declare their language. Hebrew pages run right to left.
• Numbers in Hebrew text. Numbers, prices, code, event names and web addresses are isolated as left-to-right text, so they don’t flip inside Hebrew sentences.
• Forms. Every field has a visible label. Error messages say what to fix and are linked to their field.
• Calculator results. The calculator result and the self-check verdict are announced to screen readers through live regions (page areas that read out changes), without moving your focus.
• Two ways to this page. The skip link at the top of every page and the link in every footer.

Automated tools miss problems, so your report counts

Checks done on October 9, 2026: an automated Lighthouse accessibility audit (mobile) of every page on the site, and a keyboard pass on the home page (tab order, visible focus, skip links, calculator tabs with the arrow keys).

Screen readers: not yet tested with a screen reader. If you use one and something doesn’t work, please tell me.

Automated tests catch only part of the problems. That’s why your report matters.

What doesn’t work perfectly yet

• The animated diagram on the home page that follows one order to Meta and Google is decorative and hidden from screen readers. Everything it shows is written out in full in the steps next to it.
• WhatsApp is an outside service, and its accessibility is outside my control. You can always email instead.
• Sources in the footnotes link to other organizations’ websites. Their accessibility is up to them.

No office to visit, so no physical barriers

The work is done remotely, in writing, over WhatsApp and email. There are no premises open to customers. [FILL: confirm]

Something doesn’t work for you? Tell me, and I’ll fix it

To help me fix it fast, please include:

• the page address;
• what you tried to do, and what happened instead;
• your device and browser, and the assistive technology you use, if any.

Response time: [FILL: response time]

If something on the site blocks you completely, you can still get the free check without it. Send your store URL by email or WhatsApp.