Trust CenterEmail privacy team

Legal / Accessibility

Accessibility statement

How accessible ASAI Labs Auditing System is today, what we are still fixing and how to tell us about a barrier.

Last reviewed
6 October 2026
Target
WCAG 2.2 Level AA
Status
Partially conformant
This statement is preliminary and pending human accessibility review and legal review. It does not claim full conformance.

About this statement

This statement is preliminary. It is a self-assessment prepared by ASAI Labs and it has not yet been reviewed by an independent accessibility specialist or by legal counsel. It will be updated after that human accessibility review and legal review are complete.

ASAI Labs wants the Exponata Auditing System to be usable by everyone, including people who use screen readers, screen magnifiers, voice control, keyboard-only navigation, switch devices or high zoom levels.

This statement was last reviewed on 6 October 2026 (2026-10-06).

Conformance target and status

We are working towards the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG 2.2 Level AA includes every WCAG 2.1 Level AA success criterion, which is the web requirement referenced by the European harmonised standard EN 301 549 and used in the context of the European Accessibility Act (Directive (EU) 2019/882). Whether and how the European Accessibility Act applies to this service is subject to legal review.

Current status: partially conformant. Some parts of the service do not yet fully conform to WCAG 2.2 Level AA. The known limitations are listed below. We do not claim full conformance.

A detailed Accessibility Conformance Report following the VPAT 2.5 International edition is being prepared. It is a draft and will be published after human accessibility review and legal review.

Scope

This statement covers:

  • The Exponata dashboard web application used by organization administrators.
  • The public protocol upload flow used by store staff on phones (/upload-protocol/... links).
  • This trust center at trust.asailabs.com.
  • The public API documentation site. The documentation site has not been audited yet and is not covered by the current evaluation.

The service relies on HTML, CSS, JavaScript and WAI-ARIA. It is designed to work with current versions of common desktop and mobile browsers and their assistive technologies.

Known limitations

  • Screen reader verification is pending. The service has not yet been tested by people using NVDA, JAWS, VoiceOver or TalkBack. Automated and keyboard testing cannot find every barrier.
  • Brand colour contrast. Some brand-coloured text and links in the dashboard, and accent colours chosen by an organization in its branding settings, may not reach the 4.5:1 contrast ratio. Remediation is in progress.
  • Data visualisations and maps. Charts, the contribution heatmap and the store map are being given text and table alternatives. Until that work is complete, some information in them may not be available to screen reader users, and the store map may be difficult to use with a keyboard.
  • Small targets. The opening-hours grid and the contribution heatmap use targets smaller than 24 by 24 CSS pixels. A larger alternative is in progress.
  • Hold-to-confirm actions. Some destructive actions are confirmed by holding a button for about two seconds. The button works with the keyboard (hold Space or Enter) and announces its state, but there is no alternative that does not require holding.
  • Not-found page. On the dashboard not-found page, keyboard focus can move to navigation hidden behind the page.
  • Content written by organizations. Names and text entered by an organization, such as counter types and exposition names, are shown as written. They may appear in Polish regardless of the language you choose for the interface, and they are not marked with their language.
  • Support chat. Optional support chat is provided by Intercom, a third party. We do not control or remediate its accessibility. You can decline it in the cookie preferences and contact us by email instead.
  • Map tiles. Map tiles and attribution are loaded from third-party providers and are outside our control.
  • Hover and focus content. Tooltips and other content shown on hover or focus have not been fully evaluated yet.

If you need information from any part of the service in a different format, contact us and we will provide it in an accessible alternative.

How we test

  • Automated checks with axe-core through Playwright on every dashboard route, in light and dark themes, plus open dialogs, the command palette, validation errors and the image review screens.
  • The same automated checks on a Pixel 7 mobile profile for every step of the public protocol upload flow, including upload failures and 200% text size.
  • Keyboard-only tests that complete sign-in, navigation, image review, dialogs, the command palette and the full public upload flow without a pointer.
  • Automated checks that pages reflow at 320 CSS pixels wide and keep text readable with increased text spacing.
  • Component-level automated checks for shared interface components.
  • Manual review of code, forms, focus order and content by the development team.

The automated tests run in continuous integration. A clean automated result is not a conformance claim: automated tools find only part of the possible barriers, so manual testing with assistive technologies is still planned.

Feedback and contact

Please tell us if you find an accessibility barrier, need content in another format, or have a suggestion. Include the page address, what you were trying to do, and the browser and assistive technology you use.

We aim to acknowledge accessibility feedback within [TODO: confirm response time, for example 5 working days] and to propose a solution or alternative within [TODO: confirm resolution time].

Enforcement and complaints

If you are not satisfied with our response, you can escalate your complaint.

[TODO: add national enforcement body and complaints procedure — legal review required]

Preparation of this statement

This statement was prepared on 6 October 2026 based on a self-assessment by ASAI Labs. The evaluation used automated testing, keyboard-only testing and manual review against WCAG 2.2 Level AA. It has not yet been verified by a third party, and it will be reviewed again after screen reader testing and after the remediation listed above is completed.