Skip to content
HARDEX
Back to home

Accessibility statement

Last checked: October 12, 2026

We want everyone to be able to use Hardex, including people with disabilities. This statement says what we did, what we checked, what we could not check yet, and how to ask for help.

1The standard we aim for

Hardex is a service to the public. We aim to meet Israeli Standard 5568 (the Israeli version of the Web Content Accessibility Guidelines) at level AA, the level the Equal Rights for Persons with Disabilities (Accessibility Adjustments for Service) Regulations, 5773-2013, rely on. We follow it as good practice, whether or not the Regulations require it of a business of our size. Where it was practical we also followed newer criteria from WCAG 2.2, such as minimum sizes for touch targets and focus that is never hidden. This is the level we aim for. It is not a certificate.

2What we did

  • Pages use real headings, lists, links, buttons and tables, so screen readers can move through them. A “skip to content” link is the first thing on every page.
  • Everything can be done with a keyboard alone, with a visible focus outline. Dialogs keep the focus inside until they are closed and give it back afterwards, and when you move to another part of the dashboard the focus goes to its content.
  • Text has at least AA contrast against the dark background, and the edges of fields and boxes are easy to see. Text can be enlarged to 200% without losing content or function.
  • Hebrew pages are set right to left throughout, and the language of each page is declared. Text that stays in English inside a page in another language, such as the fix prompts, is marked as English, so screen readers choose the right voice.
  • Form fields have visible labels, errors are written next to the field and announced, and colour is never the only signal: every severity is also named in words.
  • Changes are announced: a prompt that was copied, a PDF report being prepared, and which problem is now shown.
  • The report is saved as a tagged PDF, with a title and a language.
  • The pages work on phones, down to 320 px wide.
  • Animations follow your device's reduced-motion setting, and the accessibility menu can stop them on any device. The one exception is the radar, which keeps turning unless you pause it with the button next to it or choose “Stop animations” in the menu; your choice is remembered.
  • An accessibility menu, in the header of every page, lets you make the page larger (up to 150%), switch to high contrast, underline links, use a plainer font and stop animations. Your choices are saved on your device. These settings help, but the pages are built to be usable without them, and your browser's own zoom and your device's settings work too.

3How we checked

We ran automated accessibility checks (axe) on every page and on every state of the dashboard in English and Hebrew, at phone and desktop sizes. We measured text contrast against the pixels that are really behind it, and went through the product with a keyboard. Automated checks find many problems but not all of them.

We have not yet had an independent accessibility audit, and we have not tested with screen readers or other assistive technology.

4Known limitations

  • The title, explanation and technical details of each finding are shown in the language of the page, English or Hebrew. Two things stay in English, and are marked as English for screen readers: the fix prompts, which are written for AI builders, and the technical details of some findings that are free-form reports, such as a code-review message. A scan saved before this was added shows its findings in English.
  • The numbered dots on the radar are small and close together when a scan has many problems. The same actions are in the table next to it, whose buttons are large enough.
  • The AryonX main website, at aryonx.ai, has its own accessibility statement.

5Asking for help or reporting a problem

If you meet a barrier, or you need something from Hardex in another format, write to us at the address below. Please tell us which page it was, what you were trying to do and, if you can, the device and assistive technology you use. We read every message and will tell you what we can do.

AryonX is run by its founder, who handles accessibility requests. No separate accessibility coordinator has been appointed.

6Keeping this up to date

We check accessibility again when the product changes, and update this statement and its date.

7Questions or requests

Write to us at support@aryonx.ai. We read every message.

ARYONX (AryonX.ai), Israel