Accessibility statement

This is a translation provided for convenience. In case of any discrepancy, the Spanish version prevails.

BIOMAG, S.L.U. is committed to making AIM CODEX accessible in accordance with Spanish Law 11/2023 of 8 May, which transposes Directive (EU) 2019/882 (European Accessibility Act) into Spanish law.

Compliance status

AIM CODEX is partially compliant with the EN 301 549 standard, which refers to the WCAG 2.1 level AA guidelines; we also review the criteria added by WCAG 2.2 (see below). “Partially compliant” means that most requirements are met, with the exceptions detailed below.

We do not declare full compliance because we have not carried out a certified external audit or tests with real users of assistive technologies. We prefer to say what we have checked and how, rather than claim a compliance we could not support.

How we checked

Self-assessment, run automatically on every change to the product:

• axe-core (Deque Systems’ open-source audit engine, which applies the W3C’s WCAG criteria) on the public surfaces, with the WCAG 2.0, 2.1 and 2.2 A/AA criteria: zero failures detected.
• Manual review of what axe-core does not measure in WCAG 2.2: that the fixed header does not hide what receives focus (2.4.11), that sign-in fields can be filled in by a password manager and allow pasting (3.3.8), and that no action requires dragging (2.5.7).
• A real keyboard walkthrough in a browser, because axe-core does not assess navigation: we check that everything reachable with the Tab key shows its focus (WCAG 2.4.7), that the console can be operated without a mouse (WCAG 2.1.1) and that the page the recipient sees declares its language, heading and image alternatives.
• Inspection of the accessibility tree: we check that each action is announced with its correct role (button, link) and with a name, which is what a screen reader user hears.
• These checks are part of continuous integration: a change that breaks accessibility stops the release.

The keyboard assessment tool is herramientas/probar_accesibilidad.py, inside the product itself.

Non-accessible content

We are aware of these limitations:

• Customers’ documents. CODEX seals and transmits files created by users themselves (PDF, images, text). We cannot guarantee the accessibility of someone else’s document. The documents that CODEX generates are issued in PDF/A-3b (ISO 19005-3), a format designed for long-term preservation, with selectable text and embedded fonts.
• No tests with real users of assistive technologies. We do inspect the accessibility tree automatically —the structure a screen reader announces— and that is how we detected and fixed six product actions, including “Accept and sign”, that were exposed as text rather than as buttons. But we have not validated with commercial screen readers (JAWS, NVDA, VoiceOver) or with people who use them every day. This is the limitation we most want to fix.
• Hand-drawn signature. The “draw” signature mode requires a pointer or touch screen. There is a “type” alternative that works with the keyboard alone.

If you find a barrier

Write to us at hola@aim-codex.ai telling us the page and what prevented you from completing the task. We reply within 20 working days at most. If you are not satisfied with the reply, you can file a complaint with the competent market surveillance authority for accessibility.

Date

Statement prepared on 12 August 2026 and reviewed on 24 October 2026, through automated self-assessment and manual review. It is reviewed with every change to the product.