Accessibility statement

1. Our commitment

We are committed to making this service usable by everyone, including people who use screen readers, keyboard-only navigation, screen magnification, speech input or other assistive technology. Accessibility is treated as part of the product, not as a bolt-on: every route is built with semantic HTML, and every change is checked with an automated accessibility engine before it ships.

2. Conformance level

Our target is WCAG 2.1 level AA, as adopted by Israeli Standard 5568 and required by the Equal Rights for Persons with Disabilities Regulations (Service Accessibility Adjustments), 5773-2013.

This site is conformant with WCAG 2.1 level AA and Israeli Standard 5568. Every route and every state of the audit progress page was tested with the axe accessibility engine in all three site languages, and the current result is zero violations. In honesty: automated testing covers only about a third of the WCAG success criteria — the rest require human judgement — so this statement rests on that automated result plus our own manual keyboard and screen-reader testing, which is ongoing. The known limitations below are real and are listed deliberately.

3. What we did

• Semantic HTML with a single main landmark plus header, navigation and footer landmarks on every page, and a heading structure that never skips a level.
• A skip-to-main-content link that is the first item in the tab order and becomes visible on focus.
• Full keyboard operability: every control is reachable and operable with a keyboard, modal dialogs trap focus, Escape closes them, and focus returns to the control that opened them.
• Visible focus indicators on every interactive element, with at least 3:1 contrast against the surrounding colours.
• Accessible names on every control, including icon-only buttons.
• Form errors linked to their field with aria-describedby and announced to screen readers.
• The page title updates on navigation and the new page is announced in a polite live region.
• Colour contrast of at least 4.5:1 for body text and 3:1 for large text and interface borders. Where our brand orange and our result colours were too light for text, we introduced darker text-only variants and kept the bright colours for decorative fills.
• Responsive layout that works from 320 pixels upwards, and at 200% text zoom without loss of content or functionality.
• Reduced motion is honoured automatically from the operating system setting, without the visitor having to ask.
• Full right-to-left support in Hebrew and Arabic, with correct mirroring and per-language typefaces.
• An accessibility widget offering text sizing up to 200%, increased line height and letter spacing, a high-legibility font, high contrast, inverted colours, greyscale and reduced saturation, link and heading highlighting, a large cursor, stopping all animation, a reading guide and a reading mask.

4. Known limitations

We would rather name our gaps than pretend they do not exist. As of the date below:

• PDF export. The PDF of a report is produced by the browser's own print function from the HTML page. It is not a tagged PDF, so it has no reading order, headings or alternative text for assistive technology. The HTML report at its permanent link is the accessible alternative and contains exactly the same information.
• Third-party measurement data. Performance findings include diagnostic text returned by the Google PageSpeed Insights API. We translate the most common items into Hebrew and Arabic, but less common diagnostics may still appear in English. We do not control the wording Google returns.
• Audited third-party sites. Screenshots and excerpts of the website being audited are reproduced as we found them; we cannot make someone else's content accessible.
• Charts. Score history is drawn as a sparkline. The same values are always available as text next to the chart, but the chart itself is decorative and hidden from screen readers.

5. Physical premises

The service is delivered entirely online. The business operates remotely and has no office, branch or other premises open to the public, so structural accessibility arrangements — parking, entrance, lift, accessible toilet, service counter or hearing induction loop — do not apply. All contact happens by email, phone or WhatsApp: aelgani.mhmd@gmail.com, 052-444-6528.

6. Accessibility coordinator

• Name: Mohamed Abd Elgani
• Role: Accessibility coordinator
• Phone: 052-444-6528 (WhatsApp: +972 52-444-6528)
• Email: aelgani.mhmd@gmail.com

We respond to every accessibility enquiry within 5 business days, with either a fix or a timetable for one. Email is the fastest route: aelgani.mhmd@gmail.com.

7. Reporting a problem

If you meet a barrier on this site, please contact the accessibility coordinator above. Tell us the page address, what you were trying to do, and the assistive technology and browser you were using — that lets us reproduce the problem quickly. We treat accessibility reports as defects, not as feedback.

If our response does not satisfy you, you may contact the Commission for Equal Rights of Persons with Disabilities at the Ministry of Justice.