Accessibility statement
Last updated: 24 September 2026
Kalma is committed to making its web application accessible to everyone, including people who use a screen reader, a keyboard only, voice control or magnification. This statement describes how far the application currently conforms to EN 301 549 and the Web Content Accessibility Guidelines (WCAG).
1. Compliance status
The reference standard is EN 301 549 (v3.2.1), which points to WCAG 2.1 level AA. We also assess against WCAG 2.2 level AA, required by version 4.1.1 of the standard.
Kalma is partially compliant with that standard: most content conforms, and the known exceptions are listed in the next section.
2. Non-accessible content
These are the limitations we know about and what we are doing about each one:
| Area | Limitation | Criterion | Plan |
|---|---|---|---|
| PDF report | The MIDP register PDF is untagged: a screen reader reads it without heading or table structure. | EN 301 549 cl. 10 · WCAG 1.3.1 | The same content is available in Excel, which is the accessible alternative. We are assessing tagged PDF output. |
| Screen readers | We have not yet completed manual screen reader testing (VoiceOver, NVDA) of every flow. Current verification is automated and keyboard-based. | Several | Manual testing of project creation and the drawings board. |
| Languages | The English and French text, including screen reader labels, has not yet been reviewed by a native speaker. | WCAG 2.4.6 · 3.1.2 | Native review of the English and French versions. |
| Third-party services | Signing in with Google and authorising Autodesk Forma/ACC® happen on those providers' pages. | — | Outside the scope of this statement. |
3. How we assessed it
This statement was prepared on 24 September 2026, based on a self-assessment by the Kalma team.
The public pages and the application screens (dashboard, projects, drawings board, TIDP, reports, alerts, settings and the new-project wizard) are tested with axe-core against WCAG 2.1 and 2.2 level AA, in light and dark themes and at 320 pixels wide.
Every code change goes through automated accessibility rules and a test that computes the actual contrast of every colour pair in the interface.
Automated tools only find part of the problems, which is why manual screen reader testing is listed as outstanding in the table above.
4. Accessibility features
Every feature can be used with a keyboard, including reordering columns and naming segments.
Single-key shortcuts can be turned off in Settings.
Every page has a link to skip straight to the main content.
The interface follows the browser's text size and the system's dark mode, and fits screens 320 pixels wide without horizontal scrolling.
Form errors are announced to screen readers and linked to the field that failed.
5. Feedback and contact
If you find an accessibility barrier in Kalma, or need any content in another format, email info@kalma.build with the page and what you were trying to do.
We reply within 10 working days at most.
6. Tenders and supplier assessments
If your organisation needs the detail of this assessment for a tender or a supplier questionnaire, ask for it at the same address.