How we make the site usable — and what remains.Accessibility.
Updated: September 14, 2026
In short: you can read the site, navigate it and contact us with a mouse, a keyboard or touch. What we tested is described here as it measured, and what we have not tested is here too.
The commitment
We aim to meet the WCAG 2.1 guidelines at level AA, on which the Israeli standard (SI 5568) is also based. The site's code includes two tests anyone can run. The first runs axe-core (WCAG 2.0/2.1 A and AA) on 21 pages in both languages and checks, at seven screen sizes — including 320 and 640 pixels wide, which is what a browser zoomed to 400% and 200% actually lays out — that nothing scrolls sideways, no heading is clipped and every page has one main heading, and repeats the check under reduced motion. The second opens the mobile menu and walks it by keyboard. Last run: September 14, 2026. Aiming is not the same as conforming: an automated check finds some of the problems, not all of them.
What works now
- The language and direction are declared on every page, so screen readers read in the right voice.
- Semantic structure: one main heading per page, subheadings in order, labeled navigation regions, alternative text for images and labels for the films.
- Keyboard: links and buttons are native elements reachable with Tab, with a visible focus mark. The automated test walks the mobile menu by keyboard; the site's other keyboard paths are not covered by an automated test.
- Reduced motion: if your system is set to "reduce motion", the home page gives up the smooth scrolling and the transitions, the sentences land whole, and the work films neither play on their own nor download. A film you will not be shown is not fetched.
- A skip-to-content link is the first keyboard stop on every page, and everything that takes focus shows a visible focus mark.
- Contrast: axe's contrast check runs on all 21 pages in both languages, and the last run (September 14, 2026) found no violation.
- The text scales with the screen and with browser zoom: the test runs at 320, 390, 640, 768, 884, 1280 and 1440 pixels wide, with no sideways scrolling and no clipped heading. The main buttons and the menu items are at least 44 pixels tall; links inside running text are the height of their line, like any other text.
- The mobile menu is a modal dialog: it covers the whole viewport, focus is trapped inside it, Escape closes it and returns focus to the button that opened it, choosing a destination moves focus into the new page's content, and the page behind it is frozen and marked inert. The test opens it — rather than only checking it is closed — at 320, 375, 390, 430, 768 and 884 pixels, in both languages, on eight kinds of page.
- The film on a work page is played by a real button whose name changes with the state (play or pause), not by a silent click on an image.
Known limitations
- We have not tested the site with a real screen reader (NVDA, JAWS, VoiceOver). The semantic structure was checked with automated tools, which is not the same thing.
- On a wide screen the home page is a scroll-driven scene with 3D. It requires WebGL and a reasonable computer, and without "reduce motion" there is a lot of motion in it. The scene loads only when all three conditions hold together: at least 1100 pixels wide, at least 700 pixels tall, and an aspect ratio of at least 6/5 (src/App.tsx). Anything else — a landscape tablet or a short window included — gets the ordinary document, without the scene.
- One film on the site — the Exodify product film on the Hebrew case page — has Hebrew narration with captions burned in. It does not yet have separate captions that can be turned off or read aloud. The English case page does not show it, because no English version exists.
- The other films on the site have no speech. They show work rather than tell it, so they have no transcript.
- The site has not yet been audited for accessibility by a certified external party. Our checks are internal.
Hit a barrier?
Write to us: support@reptillix.com. Tell us which page, what you tried to do and in which browser or assistive technology, and we will fix it. We’ll get back to you as soon as we can.
About this statement
This statement was written on September 14, 2026 and describes the site as it is on that day. It will be updated with every substantial change to the site.