Is the Kav widget accessible under Israeli Standard 5568 and WCAG?
The widget and Studio are built to WCAG 2.2 AA and IS 5568, checked by an automated gate in CI — here is what that gate covers and what it can't prove.
Yes — the widget is built to WCAG 2.2 level AA and Israeli Standard 5568, and so is the Studio your team works in. Below is how that's checked, and where an automated check stops.
How it's checked
An automated accessibility gate runs in CI. It loads the built widget and the built Studio in a real browser and audits them against WCAG 2.2 AA with axe-core — in Hebrew, right-to-left, because that's where a hard-coded layout mistake shows up. It doesn't stop at pages a URL can reach: it also opens dialogs, menus and search boxes and audits them in their open state.
Why WCAG 2.2 AA covers IS 5568
Israeli Standard 5568 adopts WCAG 2.0 level AA and adds administrative requirements. WCAG 2.2 AA includes everything in WCAG 2.0 AA, so meeting 2.2 AA covers the standard's technical baseline as well.
What an automated check can't prove
We say this plainly because an accessibility claim should be precise:
- An automated tool finds roughly a third of WCAG issues. It's very good at catching regressions — a contrast ratio, a control that lost its accessible name, a skipped heading level — and blind to things that need judgement, like whether focus order makes sense.
- A clean automated run is therefore not a formal conformance certificate.
- The standard's administrative requirements — an accessibility statement, a named accessibility coordinator — can't be checked by a machine.
If you need a formal accessibility audit report for procurement, ask us directly and we'll tell you exactly what exists.
What using the widget looks like
- Keyboard only: Tab reaches the open button, Enter opens it, focus stays inside the panel, Esc closes it and focus returns to the button it came from. There's no keyboard trap at any point in the conversation.
- Screen readers: the open button has a clear name, the panel is announced as a dialog, and a new answer is announced once through a live region — not re-read on every focus move, and never silently dropped.
- Right-to-left and left-to-right are equals: the interface flips direction with the language.
- More time when it's needed: every attempt limit and step deadline offers an extension. A hard deadline with no extension is a WCAG timing failure, and Kav doesn't ship one.