Accessibility statement

digitalstep.biz is run by DigitalStep, a business owned by Moshe Machlav (registered Israeli sole proprietor). We want everyone, including people with disabilities, to be able to use this site easily and on their own. We keep working to improve its accessibility. This page describes where the site stands today.

Accessibility level and standard

We work to meet the requirements of the Israeli Equal Rights for Persons with Disabilities Law, 5758-1998, and the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013.

The site is built to Israeli Standard IS 5568, which is based on the Web Content Accessibility Guidelines (WCAG) 2.0 at level AA. Our target is WCAG 2.1 level AA.

Based on our own testing, the site is partially conforming. It has not had an external audit yet, and some parts are not fully accessible. These are listed below.

What we have done

The site currently includes the following:

  • Semantic page structure: one main heading per page, and defined regions for the header, main content and footer.
  • Every page declares its language and text direction: Hebrew right-to-left, English left-to-right.
  • You can use the whole site with a keyboard alone. The element in focus has a visible 2px green outline.
  • Each page starts with a link that skips straight to the main content.
  • Code blocks that scroll sideways can also be scrolled with the keyboard.
  • Colour contrast was checked: body text at 14:1, secondary text at 4.7:1 or more, and buttons at 5:1 or more.
  • Images that carry information have text alternatives. Decorative illustrations are marked so screen readers skip them. Diagrams have a written legend, which screen readers read instead of the diagram itself.
  • You can enlarge text to 200% without losing content or functions.
  • Site pages have no text inside images, except the logo. The exceptions in older articles are listed below.
  • The site follows your operating system's reduce-motion setting. There is no autoplaying video and no flashing content.
  • The site works on narrow screens down to 375px wide, without sideways scrolling.
  • Link text says where each link goes.

How we checked the site

In November 2026 we ran an automated scan with axe-core 4.10 against WCAG 2.0 and WCAG 2.1 levels A and AA. The scan covered 13 representative pages in English and Hebrew. It found one issue, which we fixed. A repeat scan found no violations.

We also checked by hand: keyboard navigation, the focus outline, the skip-to-content link, layout at phone width, and right-to-left display in Hebrew.

Please note: automated scans catch only some accessibility issues. We have not yet tested the site with a screen reader, people with disabilities have not tested it yet, and no external accessibility consultant has reviewed it yet.

Known limitations

These are the parts of the site we know are not yet fully accessible:

  • Third-party content: embedded YouTube videos, the newsletter sign-up form (provided by Kit) and the Google Calendar booking page. We do not control these, and their accessibility depends on the providers. If you have trouble using them, email us and we will help another way, for example by booking a meeting or signing you up for the newsletter by email.
  • The interactive Docebo Connect recipe diagram on the recipe pages is a visual flow chart. The details of each step are also available as text in the side panel.
  • Some older guide and journal articles include code samples and screenshots that contain text. If you need any of this content in an accessible format, contact us.
  • Recipe pages are in English only. The rest of the site is also available in Hebrew.

Browsers and assistive technology

The site uses standard HTML and CSS. It is designed to work in current versions of common browsers: Chrome, Edge, Firefox and Safari, on desktop and mobile.

The site is built to work with assistive technology such as screen readers, screen magnifiers and keyboard navigation. So far we have tested only keyboard navigation and text resizing. Screen-reader testing has not been done yet.

What we plan to do next

  • Test the site with the NVDA and VoiceOver screen readers.
  • Re-check the site from time to time, especially when we add new pages or components.
  • Review this statement at least once a year.

Contact us about accessibility

If you run into an accessibility problem or have a suggestion, please tell us. To help us respond quickly, include the page, what went wrong, and the browser or assistive technology you were using.

We aim to reply within 30 business days.

Accessibility coordinator:

Statement updates

This statement was last updated on 8 November 2026.