Accessibility statement

We build software for a living, so we hold our own site to the standard we would hand a client: usable with a keyboard, readable by a screen reader, and calm for people who are sensitive to motion.

What we are aiming at

This site is built and maintained toward the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, and toward Israeli Standard 5568, which adopts them. We are not claiming conformance with either: that claim requires a formal audit, and this site has not had one yet. What follows is an honest account of where it actually stands.

What this site does

• Skip to content. The first thing a keyboard reaches on any page is a link that jumps past the navigation to the main content.
• Respects reduced motion. If your system asks for less movement, animations, the scrolling marquee, the drip and the 3D character stop or hold still rather than loop.
• Keyboard navigation. Every link, button and form field is reachable by keyboard and shows a visible focus outline.
• Nothing hidden behind hover. Content that expands on hover on a desktop is shown outright on touch devices, so it is never unreachable.
• Decorative elements are ignored by screen readers. The brand character, background artwork and ornamental shapes are marked as decorative and are not announced.
• Readable without JavaScript. Text that animates into view is still present and legible if scripts do not run.
• Images carry text alternatives, form fields carry labels, and the page language is declared for screen readers.
• Text contrast is measured, not eyeballed. Body text is checked against the AA threshold and the ratios are recorded in the stylesheet next to the colours they belong to.

What is not there yet

• No formal audit. The site has not been reviewed against WCAG 2.1 AA or Israeli Standard 5568 by an accessibility auditor, so we claim conformance with neither. Arranging one is on our list.
• Rich media has not been reviewed. The background video, the 3D character and the animated sequences are decorative and silent — they carry no information you would lose — but they have not been assessed by anyone independent, and we would rather say so than assume.
• The 3D character needs WebGL. Where it cannot run, a plain text stand-in appears instead. It is decorative, so nothing is lost.
• Third-party content. Sites we link to are outside our control and may be less accessible than this one.

Found a problem?

Tell us and we will fix it — accessibility issues go to the top of our list, not into a backlog. Please include the page, what you were trying to do, and the browser or assistive technology you use. If something on this site is blocking you right now, say so and we will get you the information another way while we fix the page.

Last updated: 17 August 2026