Web accessibility to the Israeli standard (IS 5568)
Accessibility isn't just a legal duty — it's customers you're losing. I make websites AA-conformant in the code itself, and provide a full accessibility statement.
A fast, clear quote
Sound familiar?
- You got a warning letter or heard about a business being sued — and have no idea if your site complies.
- Someone installed an 'accessibility widget' and told you that's enough.
- You have no accessibility statement, or one copied from another site.
What you get
Full accessibility audit
Manual + automated audit against WCAG 2.1 AA — including keyboard-only and real screen-reader testing (NVDA / VoiceOver), not just an automated scanner.
Real remediation in code
Correct semantics, keyboard navigation, contrast, forms, ARIA, media alternatives — fixed in the site's own code, on any platform: WordPress, Shopify, or custom.
A written accessibility statement
A statement in the format the regulation requires — conformance level, known exceptions, and accessibility-coordinator details — written for your site, not copied.
Document & video accessibility
PDFs, Word documents and downloadable forms are part of your public service — and they must be accessible too. I remediate existing documents and add captions and transcripts to video content.
Ongoing conformance (optional)
A live site keeps changing. A periodic retainer keeps new content accessible and the statement current.
Why isn't a widget enough?
A floating widget doesn't change your site's code — it drapes a layer on top. A screen reader still gets stuck on an unlabeled form, and keyboard navigation still breaks on an inaccessible menu. Accessibility lawsuits have been filed against sites with widgets installed. Real accessibility happens in code — and that's exactly what I do.
Israel's accessibility duty — in plain language
Israel's Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) regulations apply to any business, company, non-profit or public body operating a website that provides service or information to the public. Regulation 35 points to Israeli Standard 5568, which adopts the WCAG guidelines — and level AA is the legally required conformance level.
The regulations do include exemptions — a small-business exemption based on annual turnover, and an 'undue burden' exemption for exceptional cases — but even an exempt business must publish an accessibility statement and offer an alternative accessible service channel. The statement must be reachable within one click from every page. In practice: almost no Israeli business website is truly 'exempt' — and a short call will establish exactly what applies to you.
What happens when you don't
The law allows lawsuits with statutory compensation — no proof of damage needed. Thousands of accessibility claims have been filed against Israeli SMBs in recent years, and most settle for far more than proper remediation would have cost.
I'm not here to scare you — I'm here so this never reaches you. Proper remediation with a current statement is the best protection there is.
The three exemption tracks — and the fine print
The regulations recognize three exemption tracks. An economic exemption — for businesses under a low annual-turnover threshold (as defined in the regulations): no approval needed, but the exemption must be declared in a published accessibility statement. A technological exemption — for legacy sites or closed systems that genuinely cannot be fully remediated: requires a signed opinion from a licensed accessibility expert, and is valid for a limited period only. An 'undue burden' exemption — where remediation cost is unreasonable: requires a reasoned application to the Equal Rights Commission.
And the fine print: no exemption erases the duty entirely. Even an exempt business needs a published statement declaring the exemption, plus an alternative accessible service channel — and technological exemptions expire and need renewal. Before relying on an exemption, verify it truly applies and that the current thresholds haven't changed — exactly what my free initial check covers.
A floating widget does not make a site accessible
'We installed an accessibility plugin' is the most common — and dangerous — mistake in the Israeli market. The widget doesn't fix forms, doesn't fix keyboard navigation, doesn't write alt text, and doesn't make PDFs accessible. It also doesn't confer IS 5568 conformance.
This site has a display-preferences panel too, by the way — but it's a convenience on top of a code-accessible site, not a substitute for one.
Good accessibility is also better SEO
A screen reader 'reads' your site exactly the way Google's crawler does: through the code. Correct heading hierarchy, alt text on images, labelled forms and semantic navigation — every real accessibility fix simultaneously improves how Google understands and ranks the site. In-code remediation is a double investment: legal conformance and organic SEO in one.
This very site is AA-conformant
Try it yourself: navigate this entire site with a keyboard only (Tab, Enter, Esc). Every component is accessible, every image has an alternative, and our accessibility statement is written in exactly the format I deliver to clients.
Related work
Kineret
Case studyWorked with Kineret College to design a sleek, responsive website that effectively highlights their academic programs and campus life. The site features a user-friendly interface and bilingual content to cater to a wide audience.
kineret.co.il
Partnered with ShinShinim JAFI to create a dynamic, bilingual website that highlights their youth programs and global initiatives. The site features an intuitive design, ensuring seamless navigation and accessibility for diverse audiences.
shinshinjafisrael.co.il
How it works (no surprises)
Intro call
A fast, clear quote
Development with regular updates
Launch & support
Frequently asked questions
Nearly every business or organization serving the public in Israel — including online stores, clinics, restaurants and service providers. Very small businesses have partial exemptions, but even they generally need an accessibility statement.
IS 5568 is the Israeli standard for web-content accessibility. It adopts the international WCAG guidelines at level AA — so in practice, a site conforming to WCAG 2.x AA meets the Israeli requirement.
Probably not. A floating widget doesn't fix the code — forms, keyboard navigation and alt text remain broken. Lawsuits have been filed against sites with widgets installed. A free initial check will tell you where you really stand.
Depends on the site's size and state. A typical brochure site — usually one to two weeks from approval. A large store or complex system — longer. After the initial check you'll get a precise estimate and a clear quote.
A page detailing your conformance level, the adaptations made, known exceptions, and your accessibility coordinator's details. The regulation requires it — and it's the first thing a lawyer checks before sending a warning letter.
Not at all. Most of my remediation work is on sites I didn't build — WordPress, Elementor, Shopify, Wix and custom code. I work in other people's code without judgment.
In three cases: a business under the regulations' annual-turnover threshold (automatic), a legacy site that genuinely can't be remediated (requires a licensed expert's opinion, time-limited), or an 'undue burden' approved by the Commission. In all cases the statement duty and an alternative accessible channel remain — an exemption is not 'nothing to do'.
If they're part of your public service (menus, forms, price lists, explainer videos) — yes. Usually it's better to convert documents to accessible web pages; when a PDF is unavoidable, the file itself gets remediated. Videos get captions and transcripts.
First — don't ignore it. Send it to me on WhatsApp and within one business day you'll get a status picture: what's accurate, what needs immediate fixing, and what it'll cost. Consult a lawyer in parallel — I handle the technical side.
You've got a project? I've got a keyboard.
I reply within one business day. A clear quote after a short intro call.