← Back to flexgem.io
// Accessibility

Accessibility statement

Last updated: 7 October 2026 · Standard: IS 5568 part 1 (WCAG 2.0) level AA

Our commitment

Flexgem wants every visitor, including people with disabilities, to be able to read this site and reach us through it. This statement describes what we did, how we tested it, what we know is still missing, and how to tell us about a problem. It is published under Regulation 35 of the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013, made under the Equal Rights for Persons with Disabilities Law, 5758-1998.

Standard and level

The site was built to Israeli Standard SI 5568 part 1, which adopts the Web Content Accessibility Guidelines (WCAG) 2.0, at level AA. We also checked it against the success criteria added in WCAG 2.1 level AA, such as contrast of controls and reflow on small screens.

What we did

  • Structure. Real headings, landmarks (header, main content, footer) and a "Skip to content" link. The page language is declared; the Hebrew site is a separate set of pages marked as Hebrew and laid out right-to-left, and the English site is marked as English.
  • Keyboard. Everything works without a mouse. Each control shows a visible focus ring. The four research blocks are buttons that announce whether they are expanded; the contact and cookie-settings dialogs keep focus inside, close with Escape, and return focus to the button that opened them.
  • Contrast. All text has a contrast ratio of at least 4.5:1 against its background; control borders and focus rings at least 3:1. We measured every colour pair used on the site, and the two gradient-coloured labels were darkened slightly from the design so that every point of the gradient passes.
  • Text size and reflow. Text can be enlarged to 200 % in the browser without loss of content, and the layout reflows to narrow screens without horizontal scrolling.
  • Motion. The only animation is the illustration at the top of the page: lines converging on a point, with small lights travelling along them and a pulsing ring. It loops continuously but is purely decorative, is hidden from assistive technology, can be paused with the "Pause motion" control in the footer, and is removed entirely when your device asks for reduced motion. Nothing flashes, nothing is timed, and no sound plays.
  • Forms. Every field has a visible label. Required fields are enforced by the browser with a clear message, an optional field is marked as optional, the phone field explains the accepted characters, and error states are announced. There is no picture puzzle to solve: bot protection is Cloudflare Turnstile, which checks automatically and which Cloudflare states conforms to WCAG 2.2 level AAA.
  • Images. The illustration at the top of the page is decorative and hidden from assistive technology. Decorative icons and marks are hidden likewise.
  • No accessibility overlay. We deliberately do not add an "accessibility toolbar" widget. We fix the site itself and rely on the settings you already have in your browser and operating system.

How we tested

  • The focus order and the accessibility tree (names, roles, states) were inspected in Google Chrome on Windows 11 at desktop width: every control is a native link, button or form field, no custom tab order is used, the research blocks expose their expanded state, and the two dialogs are native dialog elements whose focus trapping, Escape handling and focus return the browser provides. A walk-through with a physical keyboard is on the launch checklist (see "Known limitations").
  • The phone-width layout was checked in a 390-pixel-wide frame; 200 % zoom was checked against the stylesheet's reflow rules; a visual pass on a real phone is on the launch checklist, together with the screen-reader pass below.
  • Automated measurement of the contrast ratio of every colour combination.
  • A walk-through with the NVDA screen reader is on our launch checklist and is listed below as a known limitation until it is done and this statement is updated.

Known limitations

  • The bot check inside the contact form is served by Cloudflare in a frame. Its accessibility is maintained by Cloudflare; we cannot change it. If it blocks you, write to us at the address below and we will reply by email.
  • The walk-through with a physical keyboard and the screen-reader verification with NVDA have not yet been completed (see "How we tested"); this statement will be updated when they are.
  • No exemption from the regulations has been requested or granted.

Accessibility arrangements at our premises

Flexgem provides its services online and does not operate premises that are open to the public. Meetings take place by arrangement; tell us what you need and we will accommodate it.

Tell us about a problem

If something on this site is hard to use, or you need information in another format, contact us and we will help:

We aim to answer within five business days. Accessibility contact person: Ben.