Website accessibility is not only a legal requirement. It lets about 20% of the population use your site. Here is everything you need to know.

In Israel, about 20% of the population live with some form of disability, whether visual, hearing, motor, or cognitive. A site that is not adapted for them shuts those users out, and it also puts the business on the wrong side of the law. The Equal Rights for People with Disabilities Regulations (Service Accessibility Adjustments) from 2017 require most businesses in Israel to make their websites accessible. But beyond the law, accessibility is also a business opportunity that opens the door to 1.7 million additional potential customers. In this article we explain the requirements, how to meet them, and how much it costs.
The Equal Rights for People with Disabilities Regulations adopt the international WCAG 2.1 standard at AA level. In practice, that means:
The law applies to:
The bottom line is that if your business is more than a single freelancer working from home, you are likely required to comply. Non-compliance can lead to civil lawsuits, statutory damages with no proof of harm (up to 50,000 NIS per claim), and administrative fines.

1. Semantic HTML structure: proper use of headings (h1, h2…), nav, main, article. Screen readers rely on this structure.
2. ARIA labels: hidden labels that tell screen readers what each element does. For example, a button with only a search icon needs aria-label="search".
3. Logical tab order: when a user presses Tab, the order must be logical (top to bottom, right to left in Hebrew).
4. Colors: verify contrast with tools like WebAIM Contrast Checker. A small color tweak can solve the entire problem.
5. Accessibility widget: a floating button that lets the user enlarge text, switch contrast, enable a readable mode. EqualWeb, UserWay, and AccessiBe are the popular solutions in Israel.
Many businesses think adding a widget solves the problem. That is a mistake. A widget does play a part in the solution, since it gives the user adjustment options. But if the site's underlying code is not accessible, the widget will not help.
Example: a widget can enlarge text. But if an important image on the site has no alt text, even the most advanced widget will not read it. So the correct order: first fix the underlying HTML, then add a widget.

An accessible site gets a higher SEO score on Google (Google prefers sites with semantic HTML and alt text). Better user experience for everyone. And of course, there are the 1.7 million potential customers that others simply cannot serve.
Summary: Accessibility is an investment, not another expense. It protects you legally, opens markets, and improves SEO. At Simple Web we build every site to meet WCAG 2.1 AA from the start. Shall we talk?

January 15, 2025

May 5, 2026