Get started

Accessibility statement

Last updated: November 9, 2026

Our commitment

We want everyone to be able to use Aivting, including people who use a screen reader, a keyboard instead of a mouse, magnification, or reduced motion. We treat accessibility as part of how we build every page, not a final check.

Standard we follow

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. Israeli Standard (IS) 5568, which the Israeli Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013 refer to, is based on WCAG at level AA, and WCAG 2.2 AA includes all the success criteria of the earlier WCAG 2.0 and 2.1 AA.

What's accessible

On the pages we checked (listed under "How we tested"):

  • Every page can be used with a keyboard alone, with a visible focus indicator. A "Skip to content" link is the first stop on each page, and the menus close with Escape.
  • Text and important interface elements, including the answer marks on our charts, meet WCAG AA color contrast.
  • Pages use headings, landmarks and labels, which help screen readers and other assistive technology find their way around.
  • Form fields have visible labels, and errors are explained in text, not by color alone.
  • Images that carry meaning have text alternatives.
  • The animated product demo respects your device's "reduce motion" setting: nothing plays on its own, and selecting a step shows it as a still picture. The information it shows is also available as text on the page.
  • The pages work on small screens, when zoomed to 200%, and with larger text spacing.
  • We do not use an accessibility overlay widget; accessibility is built into the code.

How we tested

We checked the website on 4 November 2026 in Google Chrome at desktop (1440 px) and phone (390 px) widths. We used an automated tool (axe-core 4.14, WCAG 2.2 AA rules), keyboard-only navigation, a 320 px narrow-screen check, a 200% zoom check, a text-spacing check and a reduced-motion check. The pages checked were the homepage, pricing, the blog index, one blog article, privacy, terms, this statement, sign-in and sign-up. On 9 November 2026 we also checked the cookie banner and the Cookie settings window with an automated tool (axe-core, WCAG 2.2 AA rules) at 360 px and 1280 px widths, and with keyboard-only navigation.

We have not yet tested with a screen reader.

Known limitations

  • On the pages listed above, we are not aware of any accessibility barriers. If you find one, please tell us.
  • We have not yet checked the other website pages (features, about, contact, the other blog articles, the help center and the docs). They use the same building blocks as the pages we checked.
  • Our homepage and its product demo changed after our check on 4 November 2026, and we have not checked the new version yet.

The Aivting app

This statement also covers the Aivting app (the signed-in dashboard) and the read-only pages behind share links. We checked them on 4 November 2026 in Google Chrome at desktop (1440 px) and phone (390 px) widths: the projects list, a project's home page with its chart, the answers pages, gap analysis, project settings, account settings, billing, usage, the report, a single answer and a shared project page.

  • The same automated tool (axe-core, WCAG 2.2 AA rules) found no issues on these pages after our fixes.
  • Every control can be reached with a keyboard, focus is always visible, and a "Skip to content" link is the first stop.
  • Each chart can be read day by day with the arrow keys, and the same figures are available as a table ("Show as a table").
  • Chart lines differ by shape as well as by color, so you don't need to tell colors apart to follow them.
  • The guided tour opens as a dialog that keeps keyboard focus inside it and closes with Escape.

What we haven't tested in the app yet: the Action items tab (added after our check), a screen reader, 200% zoom, text spacing, reduced motion, and the accessibility of downloaded PDF reports and CSV files.

Contact for accessibility issues

If you have trouble using any part of Aivting, or have a suggestion, please contact our accessibility coordinator:

  • Accessibility coordinator: Wisam Katesh
  • Email: hello@aivting.com
  • Post: Aivting, Btzier 50, Karmiel, Israel

Please tell us the page address and what happened. We aim to reply within 5 business days and, if we can, we will give you the information in another way while we fix the problem.