Accessibility Statement

Last updated: September 29, 2026

Edrivon wants everyone to be able to use this website, including people who browse with a screen reader or keyboard, need larger text or stronger contrast, or are affected by motion. This statement explains the standard we work to, what we have done, what we know still needs attention, and how to reach us if anything gets in your way.

We treat accessibility as part of building a good website, not as an add-on. It applies equally to the English, Arabic and Hebrew versions of this site, including the right-to-left layout of the Arabic and Hebrew pages.

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium (W3C). For visitors in Israel, this also covers Israeli Standard IS 5568, which is based on WCAG and is the standard referred to by the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013.

Our most recent review, completed on September 29, 2026, found no remaining failures of the WCAG 2.2 Level A and AA success criteria that automated testing can detect, on any published page in any of the three languages. Issues found during that review, such as low-contrast labels and incorrect list markup, were fixed before this statement was published.

Automated tools cannot check everything, and we have not yet completed testing with screen readers. Until that testing is done we describe this site as partially conformant with WCAG 2.2 Level AA, which means some content may not yet fully meet the standard.

  • Accessibility menu. A button in the bottom-left corner of every page opens a menu where you can enlarge text in four steps, switch on high contrast, highlight links, stop animations, and reset everything. Your choices are remembered in your own browser only.
  • Keyboard access. Links, menus, forms and the accessibility menu can all be used with a keyboard, with a clearly visible focus indicator. A “Skip to content” link lets you bypass the navigation.
  • Clear structure. Pages use headings, lists and landmarks, so assistive technology can move through them.
  • Text alternatives. Meaningful images have text descriptions; decorative images are hidden from screen readers.
  • Readable colours. Text meets the WCAG AA contrast requirements.
  • Reduced motion. Animations stop when your device is set to reduce motion, or when you choose “Stop animations” in the accessibility menu.
  • Language and direction. Every page declares its language, and Arabic and Hebrew pages are laid out right to left.
  • Adapts to your screen. The layout works on phones, tablets and desktops, and with browser zoom.

We tested every published page in English, Arabic and Hebrew with the axe-core accessibility engine (version 4.13) in Google Chrome, against the WCAG 2.0, 2.1 and 2.2 Level A and AA rules. We also checked by hand that the navigation and the accessibility menu work with a keyboard alone, and that every option in the accessibility menu works in all three languages, on desktop and on phone-sized screens.

  • Project screenshots. Our case studies show full-page screenshots of websites we built. The text inside a screenshot is part of the image, so it cannot be read aloud or enlarged as text. Each screenshot has a text description, and each case study links to the live website.
  • External websites. Links to client websites and other third-party services lead to sites we do not control, and their accessibility may differ from ours.
  • Screen-reader testing. As noted above, testing with screen readers is not yet complete. We will update this statement when it is.

If you find a problem that is not listed here, please tell us.

This site is designed for current versions of Chrome, Edge, Firefox and Safari on desktop and mobile. It is built with standard HTML so that it can be used with screen readers such as NVDA, JAWS, VoiceOver and TalkBack, and with other assistive technologies.

If you have difficulty using any part of this site, or need information in another format, please contact our accessibility coordinator:

It helps us to know the address of the page, what you were trying to do, and, if you use one, which browser and assistive technology you use. We aim to reply within five business days.

We review this statement at least once a year and whenever we make significant changes to the site. The date at the top of this page shows when it was last updated.