Skip to content

Accessibility settings

Your choices are saved in this browser only, and you can change them at any time.

Text size

Display and reading

OrganicGrow

ACCESSIBILITY

Accessibility statement

We want everyone to be able to use this site, on any device and in any way they browse.

Draft, under legal reviewLast updated:

This text is with our lawyer. The details of the company that sells the service (name, registration number and address) are not set yet, and will appear here before we start selling. The final version will replace this text, and the date here will change.

Our commitment

OrganicGrow serves business owners in the United States and in Israel, in English and in Hebrew. We treat accessibility as part of the product: a page some visitors cannot use is a page that does not work.

This statement covers the public site and the personal area (your account), in both languages.

The standard we work to

We work to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA.

In the United States, WCAG 2.1 AA is the most widely used technical benchmark for website accessibility under the Americans with Disabilities Act (ADA).

In Israel, WCAG 2.1 AA includes everything in Israeli Standard 5568 at level AA, which the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013, require of a website that offers a service.

Until an external audit confirms it, we describe the site as partly conforming: we believe it meets the standard except for the items listed under "What is not finished yet".

What we did

  • Structure: one main area on every page, headings in order, named navigation areas, and a skip-to-content link as the first thing you reach with the keyboard.
  • Keyboard: menus, tabs, accordions, sheets, forms and the film player, its seek bar included, all work with the keyboard alone. The focus outline is always visible, and a focused control is scrolled clear of the buttons fixed to the bottom of the screen.
  • Contrast: we measured every text colour against every background it sits on. Text meets at least 4.5:1, and large text at least 3:1.
  • Images: meaningful images have a text alternative. Decorative images and the moving backgrounds are hidden from screen readers.
  • Forms: every field has a visible label. Errors are written out in words, tied to their field and announced.
  • Locked results: on a scan result, an item that opens with a plan is announced as a locked opportunity, together with what pressing it does.
  • Language and direction: every page declares its language and direction, and English names inside Hebrew text are set left to right so they read in the right order.
  • Motion: animations stop when your device asks for reduced motion, or when you choose "Stop animations" in the accessibility menu. The explainer film never plays sound by itself, has captions in the picture, and its full script is printed under it.
  • Zoom and small screens: the pages work on a 390 pixel wide phone and at 200% zoom, with nothing cut off and no sideways scrolling.
  • Touch targets: buttons and menu items are at least 44 by 44 pixels; text links in lists are at least 24 pixels tall.

How we checked

On November 2, 2026 we checked every public page and the main screens of the personal area (sign-up, scan progress and result, the plan picker, the article editor) in English and in Hebrew, on a 390 pixel phone screen and a 1440 pixel desktop screen, in Chrome. We used the axe-core automated checker, our own contrast measurement, and a keyboard pass through each page.

What is not finished yet

  • No external audit by an accessibility consultant yet. It is planned before the wide launch.
  • We have not yet tested with screen readers (NVDA, JAWS, VoiceOver, TalkBack) on real devices. The code follows their conventions, but only a real test confirms it.
  • English words inside Hebrew text are laid out left to right, but not all of them are marked with their language yet, so a screen reader may read them with a Hebrew voice.
  • The explainer film has music and captions in the picture but no narration yet. When narration is added, it will get a captions track and an updated script.
  • Our articles link to other sites. We cannot answer for the accessibility of sites we do not run.
  • Articles we write for customers are published on the customer's own site, which is the customer's responsibility. We write them with plain headings and lists.

If something does not work for you

Tell us, and we will give you the same information or service another way, for example by email or on a call, as soon as we can.

Accessibility coordinator

Questions, problems and requests about accessibility go to our accessibility coordinator. Leave your details in the contact form and write "Accessibility" in the note. Tell us which page, what you tried to do, and which device, browser and assistive technology you use. We reply within one business day.

Last review

This statement was last reviewed on November 2, 2026. We will update it whenever the site changes in a way that affects accessibility.

Questions about this document? Leave your details