Accessibility Statement

1. Our commitment

HaROS is a platform that manages corporate retail operations from the warehouse to the store, from order to shipping. Among the teams using this platform there are people with different visual, hearing, motor or cognitive abilities — so we see accessibility not as a feature added afterwards but as part of the design process.

When designing both this website and the HaROS product interface, we take the Web Content Accessibility Guidelines (WCAG) as a reference, and review basic principles such as keyboard navigation, readable contrast and semantic structure in every new component.

2. Target standard

In our accessibility work we adopt the WCAG 2.2 AA level as a target. This is not a conformance statement or certification — it is a goal that guides our design and development decisions.

As of now we have not undergone an independent accessibility audit and we do not claim full conformance with WCAG 2.2 AA. The "Measures applied" and "Known limitations" sections below honestly summarize where we stand today against this target.

3. Measures applied

The concrete measures we currently apply on the website and in the product interface:

Keyboard navigation

Links, buttons and form fields on the pages are designed so that they can be used with the keyboard alone; there is no dependence on a single interaction path that requires a mouse or touch screen.

Focus visibility

When navigating with the keyboard, which element is selected is always indicated by a visible focus ring. On this page too we apply this behavior with the :focus-visible style — you can try it by pressing the Tab key.

Color contrast

Text and background colors are chosen to target a contrast ratio of at least 4.5:1 for body text. The brand blue is used only for links and emphasis, in shades that preserve sufficient contrast.

Text alternatives

Meaningful alternative text is added to images that carry information; purely decorative images are hidden from screen readers so that they do not create unnecessary noise.

Reduced motion preference

For users who have the "reduce motion" preference turned on in their operating system, animations and automatically rotating visuals are disabled or minimized. The rotation animation in the footer illustration on this page also turns off according to this preference.

Resizable text

When text is enlarged with browser zoom, it remains readable without breaking the layout; content is not cut off or overlapped.

Semantic HTML

Pages are built with the right HTML elements such as heading hierarchy (h1–h3), lists, buttons and links; this allows screen readers to announce the page structure correctly.

4. Known limitations

We see accessibility as continuous work and we know that as of today we have gaps in some areas:

• Some complex data visualizations in the HaROS product (for example warehouse heat maps, stock flow diagrams) may not offer screen reader users a fully equivalent experience to visual users.
• Some interactive demo components on the site (for example the WMS/OMS/PIM animations) were designed assuming mouse or touch interaction; keyboard and screen reader support does not yet cover all interaction steps.
• The accessibility quality of some third-party integration screens depends on that integration's own interface and so may remain outside our direct control.

These items are on our improvement list. If you notice a new limitation, reaching us through the feedback channel below helps us prioritize this list correctly.

5. Use with assistive technologies

We design HaROS and this site to be usable with screen readers working with current browsers, keyboard navigation, voice control tools, and browser zoom/font enlargement features. We do not make an official compatibility commitment with a particular screen reader brand or version; our aim is to offer an experience compatible with the general working principles of commonly used assistive technologies (focus management, semantic structure, text alternatives).

If you encounter unexpected behavior with a particular assistive technology, letting us know which tool and browser you use helps us reproduce the problem correctly.

6. Feedback and support

If you encounter an accessibility barrier on this website or in the HaROS product, we would like to hear about it. Stating the page or screen you encountered, the device/browser you use and, if any, the assistive technology helps us understand the problem faster.

You can reach us through the contact section.

7. Review and improvement process

We treat accessibility not as a one-off checklist but as continuous work. As new components are added we review them for keyboard navigation, contrast and semantic structure, and we update our priorities according to the feedback we receive. This page will be updated over time to reflect where that process has got to.