Accessibility Statement

What we build against

The site was built against WCAG 2.2 at level AA as the working standard. That is the bar we set for ourselves while building it.

We chose to build accessibility into the site rather than install an external accessibility widget. A widget adds a layer on top of a site without repairing what is underneath it, so there is none here.

What was done

Semantic structure: headings in order, navigation and content regions marked up, and a skip link to the content at the top of every page. The whole site can be operated with a keyboard alone, and anything that takes focus shows a visible focus indicator.

Text-to-background contrast is checked automatically on every build against the level AA threshold. The form uses bound labels, error messages tied to the field they belong to, and marking that does not rely on colour alone. Pages are built in Hebrew and English with the correct writing direction for each, and all content is present with JavaScript switched off.

Known limitations and what is not yet tested

The checks described above are the ones a machine can run, and they do not replace a person. A full manual pass with a screen reader has not been carried out yet, so there may be places that read aloud less clearly than they look.

No assessment by a service-accessibility specialist has been carried out and the site carries no standards mark. Nothing here claims the site meets any particular requirement, only what was done to it.

What is outside our control

The site links out to other websites, including the product sites and external services. Their accessibility is decided there, not here.

Found an accessibility problem?

Tell us and we will fix it. A short description of what happened, which page it was on, and what you were using helps us reproduce it quickly.

Email graphid@gmail.com, or use the WhatsApp number on the contact page. We answer within two business days.