♿ Accessibility Statement

1. Our Commitment

Timing is committed to making its services and website accessible to the widest possible audience, including people with disabilities, as a matter of equal rights. We treat accessibility as an ongoing effort and continually work to improve it.

1b. Scope of This Statement

This statement covers every digital surface through which we provide the service: • The marketing site: timingapps.com (information, pricing, guides, and the business directory). • The public booking pages: timingapps.com/lp/… (app.timingapps.com/lp/…), where customers book an appointment with a business. • The business web app: app.timingapps.com. • The Timing iOS and Android apps. A note on the apps: regulation 35(d) permits an exemption for a mobile application where an accessible website provides an equivalent, mobile-adapted service. Our web app provides full functionality on a mobile device and we rely on that; we are nonetheless working to make the native apps accessible as well.

2. Conformance Standard

We work in line with the Israeli Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013, and Israeli Standard 5568 for web content accessibility, which is based on the WCAG 2.0 guidelines at level AA. We aim higher than that, at WCAG 2.2 level AA. The booking pages and the marketing site: every public route, and every intermediate state of the booking flow, is tested automatically against WCAG 2.0/2.1/2.2 level AA and passes with no findings. That testing runs in a real browser and covers the four screens behind customer sign-in (details, code verification, deposit and confirmation), the intake forms across every question type and every state they can end in, the attendance and review links, and all 38 pages of the marketing site. It also measures the contrast of text sitting on colour gradients — a case the usual scanners report as "cannot tell" rather than failing. We have also checked keyboard navigation through the flow by hand, and measured the contrast actually rendered. What we have NOT done is commission a full certified audit, so we do not claim full conformance. Automated testing covers only part of the requirements, and screen-reader behaviour can only be judged by hand. The business web app is less far along, but has moved a long way. Text scaling is now supported to 200% - what the standard asks for. We built automated sweeps that run over the whole app and count controls with no accessible name, form fields with no label, tap targets under 24 pixels, and text that overflows when enlarged; the findings were fixed. Text and icon contrast is measured automatically rather than judged by eye. Automated testing still covers only part of the requirements and is no substitute for testing with a screen reader. See section 5, "Known Limitations". We do not claim conformance where it has not yet been achieved.

3. Accessibility Features

• Full keyboard navigation with a visible focus indicator. • A "skip to content" link at the top of the page. • Semantic structure with navigation, main-content, and footer landmarks. • Alternative text for meaningful images. • Full support for Hebrew (RTL) and English (LTR). • Adequate color contrast and resizable text. • A dedicated accessibility button (see section 4).

4. Accessibility Widget

On the marketing site (timingapps.com) a dedicated accessibility button appears in the bottom-left corner of the screen. Opening it reveals a menu that lets you, among other things: increase/decrease text size and spacing, invert colors or apply gray hues, underline links, enable a big cursor and reading guide, use text-to-speech, and disable animations. Your preferences persist between visits.

5. Known Limitations

We prefer to say plainly what is not yet accessible rather than claim blanket conformance: • No certified external audit has been carried out yet. Our testing is automated plus internal manual checking. • The accessibility button available on the marketing site is not shown on the booking pages. • No manual screen-reader pass (VoiceOver/TalkBack) has been carried out by a person. This is the requirement automated testing cannot stand in for, and it is the most significant gap remaining. • Where text sits on a photograph under a translucent scrim, the contrast ratio cannot be computed automatically, because it depends on the photograph itself. Those places are checked by eye only. • In the business app a small number of controls still lack an accessible name, mostly on screens currently under development. • The calendar (appointment board) is a highly interactive third-party component; full keyboard navigation within it is not yet complete. An accessible list of appointments sits alongside it in every calendar view - day, week and month. • Third-party content embedded in the product (for example maps, or the payment provider's checkout page) is outside our full control. We fix defects as they are found and prioritise reports from users. If you encounter a component that is not accessible we would like to hear about it, and we will provide an accessible alternative route to complete that action. See the contact details below.

6. Accessibility Feedback

Encountered an accessibility problem, or have a suggestion? Please contact us and we will address it promptly:

📧 Email: support@timingapps.com

📞 Phone: +972-52-331-6433

🏢 Accessibility contact: Omer Rahmany