Accessibility statement
This site is built to meet Israeli Standard 5568 Part 1 (2023) at level AA, and alongside it WCAG 2.2 at level AA for an international audience. There is a built-in accessibility menu written in the site's own code, full keyboard navigation, and alternative text on every image. If something does not work for you, write in and it will be fixed.
The commitment
The site is built to meet Israeli Standard 5568 Part 1 (2023) at level AA. That standard is based on WCAG 2.0 with Israeli adaptations, and it applies under the Equal Rights for Persons with Disabilities Law, 5758-1998, and the service accessibility regulations made under it. The guidance published by the Commission for Equal Rights of Persons with Disabilities is followed as well.
Because the catalog is also read outside Israel, the pages are built against WCAG 2.2 at level AA at the same time. That is the current version of the international guidelines. Both sets of rules are used together, and wherever they differ the stricter one wins.
The goal is straightforward: make the site usable, independently and comfortably, by people with disabilities.
What has been built in
These adjustments are part of the site:
- Semantic structure, an ordered heading hierarchy, and a skip link to the main content.
- Full keyboard operation, with a clear and visible focus indicator.
- Alternative text on images, and a written description of the effect next to every command.
- Correct isolation of Latin command names inside Hebrew text, so they do not reverse on screen or when read aloud.
- Color contrast, responsive layout, and reduced motion that follows your operating system setting.
- Status messages announced to screen readers, for example when a command has been copied to the clipboard.
- An accessibility menu offering larger text, high contrast, grayscale, underlined links, reduced motion, and a reset.
The accessibility menu is our own code
The accessibility menu is written in the site's own code. It is not a third party overlay widget. Overlays inject outside code into the page, often conflict with screen readers, and are no substitute for accessibility built into the page structure itself.
Whatever you choose in the menu is saved in your browser only. It is never sent to anyone, and it clears when you press Reset or clear site data.
Testing
Accessibility is tested on an ongoing basis during development: keyboard navigation, page structure and headings, color contrast, and automated checking tools.
It is worth stating this precisely. Automated tools catch only some accessibility problems, and not every page and not every component has been fully tested in every browser and with every assistive technology. This statement describes continuing work, not a finished result and not an external certification.
Reporting a problem
If you run into difficulty, or find content that is not accessible, contact the accessibility coordinator, Roye Cristal Libhaber, at royecr@gmail.com.
To make it quicker to fix, please include the page address, your device and browser, and the assistive technology you were using, if any. Reports are looked into and answered within a reasonable time.
You can also ask for an accessible alternative to a specific piece of content, and the request will be considered.
A few other things worth knowing
This is a digital service only. There is no physical location where visitors are received, so there is no building or in-person service accessibility statement.
Some of the images were made with AI tools and contain a lot of visual detail. Every image sits next to the command name and a written description of the effect, so you can understand what a command does without seeing the picture.
Despite the effort, individual accessibility problems may still exist. Reporting one is the fastest way to get it fixed.
Last updated: 11 September 2026