Accessibility Statement

We treat web accessibility as inseparable from professional and service quality, and we aim to give every visitor a browsing experience that is as comfortable and independent as reasonably possible.

Webicon is committed to equal access and to improving the accessibility of this website for people with disabilities, in line with the Israeli Equal Rights for Persons with Disabilities Law (1998) and related accessibility regulations, and using WCAG 2.1 Level AA as a professional target.

This page describes the practical implementation of our public marketing site (React SPA) as of the date shown at the top. It is not legal advice.

The site is on an ongoing path of alignment with WCAG 2.1 Level AA. We invest substantial effort in implementing accessibility requirements as an integral part of development, and we work continuously to identify and improve areas that need further adaptation.

The table below summarizes the main accessibility measures implemented on this site as of the date of the latest update.

Language and direction: document lang and dir are set in HTML and updated when switching language.

Structure: main, nav, and footer regions; sensible heading levels on pages.

Forms: labels associated with fields (id/htmlFor) on contact, consultation popup, and job application, including the CV file control.

Keyboard and focus: visible focus styles on many controls; a skip link to main content appears at the start of the tab order; mobile navigation uses a Radix Sheet with focus management and Escape to close; the menu button exposes aria-expanded and aria-controls.

Motion: carousel autoplay and entrance animations respect the user’s “reduce motion” system preference where implemented.

Images: alt text on most static images. On blog cards, featured images sometimes use the post title as alt — in that case a screen reader may announce the same string twice (heading then alt). We are moving toward empty alt (alt="") for purely decorative images, or a short description of what appears in the image when it adds information; this also aligns with good practice for image discovery in search.

Names for controls: aria-label on several icon-only actions.

Dialogs: titled consultation dialog; horizontal overflow in the dialog content is constrained.

Personalization widget (Tabnav): an optional widget from widget.tabnav.com lets users adjust personal display preferences (e.g. font size, contrast). It does not replace accessible structure or content on the site, and is not intended to compete with our components for keyboard focus.

Third-party services: features delivered by third parties (e.g. Google Analytics, Cloudflare Turnstile, Google Fonts) are not fully under our control for accessibility.

Tabnav personalization widget: loaded from a third party (widget.tabnav.com) and offered only as a complementary aid alongside accessibility work in our own code and content; it is not a substitute for accessible structure or copy.

Visual content: the project carousel uses generic alt text for device frames, and we continue to refine image descriptions in articles and portfolio items. If you encounter visual content that is hard to understand or poorly described, contact us and we will provide the information in an alternative accessible format where feasible.

We aim to maintain strong, readable colour contrast across the site, including light and dark theme modes, and we run periodic checks to keep themes readable. If specific text is hard to read because of a colour combination, please let us know through an accessibility enquiry.

During development we tested keyboard navigation and carried out partial compatibility checks with screen readers (e.g. NVDA and VoiceOver). We still recommend that users who rely on these technologies use modern, up-to-date browsers for the best experience.

Accessibility coordinator: Daria Rosen, Webicon team. Accessibility-related requests are handled directly by the coordinator. Write to contact@webicon.co.il or use the Contact page. We aim to respond with an initial reply within up to 7 business days.

We continue to improve accessibility over time. Some areas or content may not yet be fully accessible or may change with updates.

This statement is based on code review and documentation; it does not replace a full professional accessibility audit.