Accessibility Statement
Effective All versions
At a glance
- The site is built to Israeli Standard 5568 Part 1 at level AA, which is based on WCAG 2.0. In practice we aim for WCAG 2.2 AA.
- It was tested with an automated scan and by hand with a keyboard, enlarged text and a narrow screen, in Hebrew and English.
- Found a problem? Write to support@abracodeabra.org and we'll fix it.
Contents
We want everyone to be able to use the AbraCodeAbra website and read our apps' documents comfortably. This statement describes the accessibility of abracodeabra.org and all of its subdomains. It is given under regulations 35A and 35E of the Israeli Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013.
Conformance level
The site is built to Israeli Standard 5568 Part 1 (2023 edition) at level AA. The standard is based on WCAG 2.0, with a few Israeli modifications. In practice we aim for WCAG 2.2 level AA, which is stricter.
What we've done
- Structure: every page is built from semantic headings and landmarks (header, main content, navigation and footer) in order, and every section has a heading.
- Accessibility button: the top bar of every page has a button that leads to this statement.
- Keyboard navigation: you can use the site with a keyboard alone, and the keyboard focus is always clearly visible. Every page starts with a "Skip to content" link.
- Language and direction: every page declares its language and text direction. English phrases inside Hebrew text are marked separately.
- Text: you can enlarge it up to 200% without losing content. The site follows the text size set on your device (Dynamic Type on iOS and font size on Android).
- Contrast: colour contrast is at least 4.5:1 for normal text, in both light and dark mode.
- Motion: there is no flashing content, and no video or animation that starts by itself. If you've asked your device to reduce motion, the site shows none.
- No JavaScript: the site uses no JavaScript and no pop-ups, so it works even in limited browsers and inside apps.
- Small screens: the site fits a 320-pixel-wide screen without horizontal scrolling.
- Images: meaningful images have text alternatives. Decorative images are hidden from screen readers.
What was tested, and how
The last test was on 7 October 2026, on every page of the site, in Hebrew and English:
- Automated scan with axe-core in Chrome, in light and dark mode, at widths of 320, 375 and 1280 pixels.
- The browser's accessibility tree: this is the information a screen reader gets from the page. We checked that every link and image has a name, that every page has one main heading and a correct heading order, and that the page's regions are marked.
- Manual testing: keyboard-only navigation, visible keyboard focus, display at 320 pixels wide, and measured contrast of text placed over an image.
Not tested yet: we have not yet listened through the whole site with a screen reader (such as VoiceOver or NVDA). The site is built from semantic HTML with no scripts and its accessibility tree is sound, so we expect it to work well with screen readers. If you run into difficulty, please tell us.
Known limitations
To the best of our knowledge, as of the date of this statement, no part of the site is inaccessible. Testing doesn't catch everything, and if you find a problem we'll deal with it.
What this statement covers
- The website: this statement covers the website and the documents published on it.
- The apps: if you run into an accessibility problem in one of our apps, write to us at the same address.
- In-person service: we have no office or premises open to the public, so there are no physical accessibility arrangements. All service is provided through the website, the apps and email.
Reporting a problem or requesting an adjustment
If you run into an accessibility problem, or need a document in another format, write to us:
- Email: support@abracodeabra.org
- Accessibility contact: Oz Yahav
This is also the address for a notice that an accessibility adjustment is missing, a request for an adjustment, or a demand for a fix under regulation 35A(d)(1).
To help us help you faster, please include the page address, what you were trying to do, and which browser and assistive technology you used.
- Reply: we'll do our best to reply within 5 business days.
- In the meantime: until the problem is fixed, we'll give you the information another way that works for you, as soon as possible.
- Accessible-format documents: we'll send them within three weeks of your request.
- Fix: a confirmed problem will be fixed as soon as possible, and within 60 days of your notice at most.
Date of this statement
This statement was last updated on the date shown at the top of the page.
Questions?
You can write to us about anything related to this document.
support@abracodeabra.org