Guide · Accessibility widgets
Is an accessibility widget enough?
Short answer: no. An accessibility widget, or "accessibility menu", gives visitors buttons to change the display, but the Israeli regulations require the site's own content to meet the standard. Here's why, with sources.
General information, not legal advice. I wrote this guide from the text of the law and regulations as I checked it on 14 November 2026. Legislation changes. For your own business, ask a lawyer.
What an accessibility widget is
An accessibility widget (also called an overlay) is a script added to a site, usually shown as a floating button. It opens a menu with options such as larger text, contrast changes, highlighted links and stopping animations. Common ones in Israel include accessiBe, UserWay, EqualWeb and Enable (נגיש בקליק). Some also try to fix code problems automatically, for example by adding alt text to images.
Some are free, some charge monthly, and most are easy to install on Wix, WordPress and Shopify. That's why they are so common. The question is what they actually do.
What the regulations require
Regulation 35A(a) says an obligated party must provide accessibility adjustments in its internet service "in accordance with the guidelines set in it, at level AA", meaning the internet accessibility standard. That standard is IS 5568, and its part 1 is identical to WCAG 2.0 apart from a few national changes.
Those guidelines are about the page's content and code: information-bearing images need alt text, form fields need labels, the site must work with a keyboard, headings must be structured, contrast must be sufficient, and more. I read the whole part of the regulations on internet services (regulations 35 to 35F), and it doesn't mention a widget or accessibility menu as a way to meet the requirements.
What a widget can and can't do
What a widget can do
- Let visitors change text size, spacing and colours to suit them.
- Stop animations and motion on the page.
- Sometimes fix a few simple code problems automatically.
What it can't do reliably
- Know what an image shows and why it's there. Only whoever built the page knows if it's a product, a chart or decoration.
- Turn a menu, popup or form that doesn't work with a keyboard into one that works well with a keyboard and a screen reader.
- Add accurate captions to videos, or make PDFs accessible.
- Replace the tools visitors already use. People who use a screen reader or system zoom don't need another menu, and sometimes it gets in their way.
What research and regulators say
- US Federal Trade Commission (FTC), April 2025: the FTC approved a final order requiring accessiBe to pay $1 million. According to the FTC, claims that its accessWidget could make any website WCAG-compliant were "false, misleading, or unsubstantiated". These are the FTC's allegations, in a settlement.
- A study presented at ASSETS 2024 (Makati, Tigwell and Shinohara) with blind and low-vision web users: the most common rating survey respondents gave overlays was "not at all effective" (16 of 34), and some participants stopped using sites that installed an overlay because the sites became less accessible.
- A 2024 master's thesis in the AccessibleEU library, a centre run for the European Commission: in tests with 21 visually impaired participants, overlays gave "only marginal benefits", sometimes hindered use, and participants preferred their own assistive technology.
What to do instead
- Check the site. A free automated check finds some of the code problems in seconds.
- Fix the content and the template. On most sites that means alt text for images, labels for form fields, headings in order (h1, h2, h3), and buttons and links with clear text. On Wix and WordPress much of this is done in the editor, without code.
- Test by hand. Go through the site with the keyboard only, and listen to it with a screen reader: NVDA is free for Windows, and VoiceOver is built into Apple devices. I also wrote what automated checks miss and how to cover it.
- Publish an honest accessibility statement, including what isn't fixed yet and a real contact method. See how to write an accessibility statement.
- If you already have a widget, you don't have to remove it. Some visitors use the text-size or animation controls. Just don't rely on it instead of fixes, and check it doesn't interfere with keyboard navigation or screen readers.
How my checker treats widgets
My checker reads the page's HTML as the server sends it, before a widget can change anything in the browser. That shows what is in the code itself. It also looks for signs of common widgets, including accessiBe, UserWay, EqualWeb, Enable and Nagich, and says if it found one. A widget loaded by JavaScript only after the page loads may not be detected.
Automated checks find only part of accessibility issues. This is not a compliance certificate and not legal advice.
Common questions
Does a widget protect me from a lawsuit?
I found nothing in the Law or the regulations saying that installing a widget meets the duty. Section 19NA(c) (19נא(ג)) of the Law lists cases where a court won't award compensation without proof of damage, such as complying with an accessibility order or contacting the Commission before the lawsuit. Installing a widget isn't on that list. This is not legal advice.
There's a free widget for Wix or WordPress. Should I install it?
You can, as an extra for visitors who want to change the display. But the regulations require the content itself to be accessible, and on Wix and WordPress most fixes are made in the editor: alt text, headings, form labels and contrast.
Should I remove my widget?
Not necessarily. If it doesn't interfere with keyboard navigation and screen readers, it can stay as an extra. What matters is fixing the content and the code.
What should the statement say if I have a widget?
You can mention the accessibility menu, but the statement should list the adjustments made to the content itself and what still isn't accessible (regulation 35E). See how to write an accessibility statement.
Sources
- FTC: FTC Approves Final Order Requiring accessiBe to pay $1 Million, 22 April 2025
- UW CREATE: Accessibility overlays can make websites less accessible (summary of the ASSETS 2024 study)
- AccessibleEU: Impact of web accessibility overlays on usability and user experience for people with permanent visual impairments
- תקנות שוויון זכויות לאנשים עם מוגבלות (התאמות נגישות לשירות), התשע״ג–2013 (Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013), consolidated text, PDF on the National Insurance Institute site
- The same regulations, updated text with Reshumot references (Hebrew Wikisource)
- חוק שוויון זכויות לאנשים עם מוגבלות, התשנ״ח–1998 (Equal Rights for Persons with Disabilities Law, 1998), updated text, Hebrew Wikisource
- ת״י 5568 חלק 1 (IS 5568 part 1, September 2023: website accessibility), PDF on gov.il
