Accessibility statement

Last updated: September 12, 2026 · tofyapp.com · ranioph@gmail.com

We treat accessibility as part of the product rather than an add-on. Tofy is an app for children and their parents, and we want every parent to be able to read about it, understand what it does, and get in touch with us — whatever their disability, whatever assistive technology they use, and however they drive their computer.

The standard we aim for

This site is built to meet Israeli Standard IS 5568, "Web content accessibility guidelines", at conformance level AA, which is based on the W3C's WCAG 2.0 guidelines at level AA. We have also applied level AA requirements from WCAG 2.1 — today's common practice in the United States — including those covering narrow screens (reflow), the contrast of graphical elements, and text spacing.

This statement is published in the spirit of Israel's Equal Rights for Persons with Disabilities (Accessibility Adjustments to Service) Regulations, 5773–2013, under the Equal Rights for Persons with Disabilities Law, 5758–1998.

What we did

• Full keyboard navigation. Every link, button and field can be reached with the Tab key alone, and each one shows a clear, high-contrast focus indicator.
• A "skip to main content" link at the start of every page, so the menu can be skipped.
• Semantic structure. Headings run in a correct hierarchical order, navigation regions are marked as landmarks, and every menu has an explicit accessible name.
• Colour contrast. The site's background and text colours were reworked so that normal text meets a contrast ratio of at least 4.5:1 against the gradient background everywhere it appears.
• Forms. The launch-updates sign-up form has visible labels, and validation errors appear as text — with a warning icon rather than colour alone — and are announced to screen readers.
• Reduced motion. If your system asks for reduced motion, the site honours it and the sparkles and animations stop. The home page also has a button to stop the motion and the video by hand.
• Images. Every meaningful image has alternative text; emoji and illustrations that are purely decorative are hidden from screen readers so they don't clutter the reading.
• Content without JavaScript. Page content is shown in full even when scripts are blocked or fail to run.
• Language marking on passages written in the other language, so screen readers pronounce them correctly.

Known limitations

We would rather say this plainly. As of the date of this statement, these are the things we have not solved:

• App screenshots are images. Each one has a short description, but the text inside the screenshot itself is not available as selectable, resizable text.
• The demo video on the home page has no soundtrack, so it has no captions. It has a text description and a pause button, but no audio description of everything happening on screen.
• Third-party pages — such as the app's page on Apple's App Store, where the download button leads — are outside our control, and their accessibility is their operators' responsibility.
• Fonts. The site serves its own fonts from tofyapp.com — no request leaves for a font service. If a font file fails to load, text falls back to the device's default font: readability is preserved, but the appearance changes.
• Testing. We manually checked keyboard navigation, heading structure, contrast, and behaviour with scripts disabled. We have not yet completed comprehensive testing across all common screen readers or with users with disabilities, and that work continues.
• New pages. Pages and components are added from time to time, and one may go live before its accessibility review is finished. If you find one, please tell us.

This statement covers the tofyapp.com website only. The accessibility of the Tofy app itself is not part of this statement.

This site has no accessibility overlay

We have not installed an accessibility toolbar, widget or overlay, and we do not intend to. Such tools do not make a site accessible: they sit on top of markup that is wrong instead of fixing it, they sometimes interfere with the assistive technology a visitor has already installed and tuned to their own preferences, and they force third-party code onto everyone who opens the site. We fixed the accessibility in the site's own code instead — which is where it is actually measured.

Contacting us about accessibility

If you run into an accessibility problem on this site, or there is something you cannot operate, please tell us. Let us know what you were trying to do, on which page, and which browser or assistive technology you were using. We will look into it and get back to you.

More information

Privacy Policy · Terms of Use · Support