Accessibility Statement

We want everyone to be able to use yali.kids, including people who use a screen reader, a keyboard instead of a mouse or touch, larger text, or high contrast. This statement says what we have done, how we checked it, and what we know is not done yet.

The standard we aim for

Israel’s Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013, point to Israeli Standard 5568, which is based on the international Web Content Accessibility Guidelines (WCAG) 2.0 at level AA. The site aims to meet it, and we also check it against the newer WCAG 2.1 and 2.2 AA criteria.

What the site does

• A structure assistive technology can follow: one main heading per page, headings in order, marked regions for the header, the content and the footer, and a Skip to content link as the first thing the keyboard reaches.
• Everything works with a keyboard: every link and button can be reached with Tab and shows a clear focus outline.
• Readable contrast: all text meets WCAG AA’s contrast requirement against its background.
• Text can be enlarged: the layout uses relative sizes and reflows on narrow screens without scrolling sideways.
• Each page’s language is marked: Hebrew pages are set right-to-left and English pages left-to-right, so a screen reader reads each page in the right language.
• No time limits, no flashing, and no sound or video that plays by itself. Animation is reduced when your device asks for reduced motion.
• It works without JavaScript: every page can be read with scripts turned off.
• Images have text alternatives, and decorative images are hidden from screen readers.

How we checked

On 19 October 2026 we checked every page of the site, in English and Hebrew, with the automated checker axe-core (version 4.14), against WCAG 2.0, 2.1 and 2.2 at levels A and AA. It found two problems: buttons whose text contrast was too low, and summary tables with empty headers. Both were fixed the same day. On 21 October 2026 the site moved to new colors and a single light color scheme, and we ran the check again on every page: it reports none. Where it could not decide, on the text of the consent banner, which floats over the page, we measured the contrast ourselves, and it passes. We also went through each home page using the keyboard alone.

What is not done yet

• No test with a screen reader yet. The site has not yet been tested by a person using VoiceOver, TalkBack or NVDA. Automated checks cannot catch everything a screen-reader user meets, and this is the next check we will run.
• Long legal pages. The privacy policy and the terms of use are long. Each opens with a short summary table, and every section has a heading you can jump to.
• The app. This statement covers the website. The Yali app is built for young children who cannot read yet: every instruction is spoken, and everything a child taps is large. If something in the app is hard for your child or for you to use, please tell us.

Tell us

If something on this site is hard to use, or you need any of it in another form, write to support@yali.kids and tell us which page, what happened, and the browser and device you used. We will answer within 30 days, and sooner if we can.