Accessibility statement
Statement last updated: 10/02/2026
Cybertis sees accessibility as part of the service: people with disabilities should be able to use the compliance platform, and the public forms it serves, independently, equally and with dignity. This statement describes how accessible the platform is today, how we test it and what is still open.
What this statement covers
The statement applies to the whole Cybertis compliance platform, in Hebrew (right-to-left) and in English:
- The staff application (/app): the workspace of Cybertis consultants and analysts and of client administrators.
- The client portal (/portal): what client employees see, including tasks, documents, reports, questionnaires and notifications.
- The public data-subject request form (/dsar) and its e-mail verification.
- Client trust centers (/trust) and the request flow for gated documents.
- The supply-chain security survey that suppliers open from a personal link.
- Sign-in, two-factor verification and password change.
- The terms of service, the privacy policy and this statement.
Standard and conformance level
This statement is published under the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013. For online services they refer to Israeli Standard IS 5568, which adopts the W3C Web Content Accessibility Guidelines (WCAG) 2.0 at conformance level AA.
Declared conformance: Israeli Standard IS 5568 (WCAG 2.0), level AA
Our automated checks go a step beyond the legal baseline: they test against WCAG 2.1 levels A and AA, which add requirements for mobile devices, zoom and the contrast of interface components.
What the platform offers
- The platform is designed for keyboard use, with a visible focus indicator; a full keyboard verification is still pending.
- A "skip to main content" link on the main application and portal screens, and consistent headings and landmarks for screen-reader navigation.
- Hebrew and English, each in its own reading direction; text in the other language is marked so screen readers pronounce it correctly.
- Layouts are verified at phone widths (390 and 375 pixels) and pinch-to-zoom is never disabled; a check at 200% zoom is planned.
- In the light theme, text and interface colours meet the AA contrast ratios of the standard. In the dark theme the colour tokens meet them as well, and a screen-by-screen check is in progress. Status badges carry a text label as well as a colour.
- Form fields have labels tied to the field, and validation errors are shown in text next to it.
- Notifications and autosave messages use live regions, so screen readers can announce them.
- Animations are reduced when the operating system asks for reduced motion, and a dark theme is available.
How it is tested
Accessibility is checked continuously, not once. The checks are:
- Automated audits with the axe-core engine against WCAG 2.1 A and AA of the ~40 main screens, for their main roles, in Hebrew, on a desktop and a phone screen, on every pull request. The audit is advisory for now; making it blocking is planned.
- Phone-layout measurements at 390 and 375 pixels wide: horizontal scrolling, touch-target size (44×44 pixels), input text size and elements that cover the screen.
- The contrast of the design-system colour pairs (text on its background, status colours) is computed and enforced by automated tests, in the light and the dark theme.
- A keyboard-only pass on the supplier survey and on selected flows; a full keyboard review is planned.
Known limitations
These parts are not yet fully accessible, and we are working on them:
- Testing with screen readers (NVDA, JAWS, VoiceOver) has not yet been performed.
- A keyboard review of every screen has not yet been performed; it is planned.
- The dark theme has not yet been checked screen by screen; some screens may fall below the required contrast there.
- Documents the platform generates (PDF and Word reports, letters and exports) are not yet fully tagged for screen readers. On request we will provide their content in an accessible format.
- Text written by the AI assistants is generated automatically and may have an imperfect structure or mix languages.
- Files uploaded by clients, suppliers or other third parties are not under Cybertis control and may not be accessible.
- The 40 most-used screens are adapted for phones; some less frequently used staff screens are still designed mainly for a desktop.
- Dashboard charts present their data visually. Their key figures also appear as text, but not every chart has a full text alternative yet.
Getting the service another way
If a page or a document is not accessible to you, contact the accessibility coordinator (details below). We will give you the information, or complete the action with you, in another way (by phone, by e-mail or with a consultant), at no extra cost.
Accessibility coordinator
Ran into difficulty, or found something that is not accessible? Tell us: every report helps us fix it.
- Organization: Cybertis
- Accessibility coordinator: Rotem
- Email: rotem@cybertis.co.il
We answer accessibility requests as soon as possible. Please describe the page where you ran into difficulty and how you were browsing (browser, operating system and assistive technology, if any).