Accessibility statement

Our position, stated honestly

Directive (EU) 2019/882 — the European Accessibility Act — has applied to e-commerce services since 28 June 2025. Poland implemented it in the Act of 26 April 2024 on ensuring compliance with accessibility requirements for certain products and services by economic operators.

The Act exempts microenterprises that provide services: fewer than 10 employees, and either turnover or a balance sheet total not exceeding EUR 2 million. We currently meet that test, so the Act’s service requirements do not bind us.

We are publishing this statement anyway, and holding ourselves to what follows, for two reasons. Our products are used all day by accountants, customs brokers and finance teams, and a tool someone cannot operate is a tool that fails at its job regardless of who is exempt. And the exemption is a function of our size, which we intend to outgrow; building the habit now is cheaper than retrofitting later.

This is a statement of fact about a live product, so it describes what is true today rather than what we hope will be true.

What we aim at

WCAG 2.2 Level AA, which is the standard the harmonised European specification (EN 301 549) points to. We treat it as the target, not as a certification we claim.

What currently works

• Keyboard operation. Interactive controls are reachable and operable by keyboard, and the focus order follows the visual order.
• Semantic structure. Pages use real headings in order, real lists, real buttons and real links, so a screen reader announces structure rather than a wall of div.
• Text alternatives. Images that carry meaning have alternative text. Decorative visuals — the animated logo, the background effects, the custom cursor — are hidden from assistive technology rather than announced as noise.
• Reduced motion is respected. This site is deliberately animated. Every animation, including the opening preloader, the smooth scrolling, the reveal transitions and the custom cursor, is disabled when your system asks for reduced motion. That is a real preference, checked in code, not a token gesture.
• Text scaling and zoom. Layouts use relative units and reflow rather than break when text is enlarged or the page is zoomed.
• No cookie wall. You never have to interact with a consent banner to read a page, and refusing takes exactly one keyboard-reachable button — see the cookie policy.
• Colour contrast on body text and controls is checked against the AA thresholds.

What we know is not there yet

Stating this plainly is the point of the exercise.

• Some decorative and motion-heavy surfaces have not been tested end to end with a screen reader. The marketing site’s animated sections in particular are known-good in structure and untested in practice with NVDA, JAWS and VoiceOver.
• Colour contrast in the low-emphasis text tiers — muted captions and metadata on the dark background — is close to the AA threshold in places and may fall short in some contexts.
• Dense data tables inside the products (match results, declaration lines) rely on visual layout more than they should. Row and column relationships are not yet fully exposed to assistive technology.
• We have not carried out a formal third-party accessibility audit, and we have not published a conformity assessment. We do not claim WCAG 2.2 AA conformance; we claim it is what we are working towards.
• PDF and document output generated by the products is not yet tagged for accessibility.

Alternative ways to get things done

If something on this list blocks you, these are not consolation prizes — they work, and we will do them:

• Write to [email protected] and a person will answer. That inbox is the same one sales and support use, so it is watched.
• Call +48 690 164 776.
• If a screen or a document is unusable for you, tell us and we will provide the same information or complete the same task another way — a plain-text export, a different format, or a person doing it with you.

We do not put accessibility requests in a separate, slower queue.

Tell us when we get it wrong

Report an accessibility barrier to [email protected]. Tell us the page or screen, what you were trying to do, and what technology you were using if you know it.

We will acknowledge within 5 business days and tell you either how to get the task done in the meantime or when we expect to fix it. If our answer is inadequate, say so — and under the Polish implementing Act you can also raise the matter with the competent supervisory authority, whose details we will provide on request.

Feedback that changes the product

Where a report reveals a barrier we can fix, we fix it and say so on this page. Where we cannot fix it soon, it goes on the list above rather than quietly nowhere. This statement is reviewed at least annually, and whenever we ship a significant interface change.