Skip to main content
WebPlus

Accessibility Statement

Last updated: August 9, 2026

WebPlus takes making this site accessible to all visitors, including people with disabilities, seriously. This page describes what has actually been implemented, how it was tested, and what is still in progress.

Standards we target

The site is built with the intent of meeting Israeli Standard 5568 for website accessibility, which is based on the WCAG 2.1 Level AA guidelines from the W3C. That is our target level — we are not claiming full certified compliance or an official accreditation, only a working process aimed at meeting it.

What has actually been implemented

  • Full keyboard navigation across every component, including the mobile menu, buttons, forms and accordions.
  • Visible focus states on every interactive element.
  • Semantic HTML — headings, lists, forms and navigation are built from the correct tags, not generic divs.
  • Correct heading hierarchy — one h1 per page, no skipped levels.
  • A skip-to-content link at the start of every page.
  • Full form labelling, with each field linked to its error message via aria-invalid and aria-describedby.
  • Alt text on meaningful images; decorative images are marked as such.
  • Colour contrast checked against the AA contrast ratios.
  • Respects the operating system’s “reduce motion” setting, plus a manual on-site option.
  • Full Hebrew and Arabic right-to-left (RTL) support, including correct direction for icons, forms and phone numbers.
  • Accessible mobile menu, language switcher and FAQ — built with native HTML elements (details/summary) that support keyboard and screen-reader use without custom code.
  • A first-party accessibility widget (available on every page): text size, high contrast, and reduced motion — see the accessibility icon in the header.

How this was tested

Testing included a manual keyboard-only pass across every page, a screen-reader check of the form and navigation flows, and automated testing (axe) run against every page in every language.

Known limitations

  • The verification widget on the contact form is a third-party component; its accessibility depends on that provider and isn’t fully within our control.
  • Our accessibility widget is an addition on top of accessible code — it does not replace accessible markup, it complements it.
  • This is an ongoing process. If you encounter an accessibility barrier on this site, we would like to know and fix it.

Report an accessibility issue

Found a problem? Message us on WhatsApp or email, both listed in the site footer, and we will address it promptly.