Kolaboro / Accessibility
Accessibility statement
We want every buyer to be able to use Kolaboro, including people who use a screen reader, only a keyboard, zoom or high contrast.
Our target
Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, for every public page of kolaboro.com.
We do not claim full conformance. The automated results below still list open issues, and automated tests alone cannot prove conformance.
How we test
- Every night: axe-core runs in Chrome on every page in our sitemap with the rules tagged WCAG 2.0, 2.1 and 2.2 A and AA. The results are published in /data/a11y.json and on /status. Our goal is zero serious or critical findings.
- Every day: Lighthouse checks accessibility on our 20 key pages on mobile and desktop (/data/lighthouse.json), a crawl checks every page on a phone and a desktop for broken links, script errors and sideways scrolling, and visual tests compare the key pages at 390 and 1440 px with the day before.
- When we change a page: we check it in a browser at 390 and 1440 px for keyboard focus, tap target size and text that overflows.
Results of the latest automated run
Latest automated run: 2026-11-04 10:00 UTC, axe-core 4.14.0 in Chrome, rules tagged wcag2a, wcag2aa, wcag21a, wcag21aa, wcag22aa, viewport 1280x900, 458 s. Source: /data/a11y.json. This block was refreshed by the daily quality job on 2026-11-05 07:24 UTC.
Goal not met yet: our goal is zero serious or critical findings on every page. The open issues are listed below and in the table.
Known issues from the latest run
| Rule | Impact | Pages | Elements | Example pages |
|---|---|---|---|---|
| scrollable-region-focusable Scrollable region must have keyboard access | serious | 4 | 12 | /docs/api/ /docs/mcp/ /docs/webhooks/ /docs/partners/ |
| aria-prohibited-attr Elements must only use permitted ARIA attributes | serious | 1 | 20 | /investors/dossier/ |
| color-contrast Elements must meet minimum color contrast ratio thresholds | serious | 1 | 24 | /report/state-of-off-plan-2026/live/ |
Recent runs
| Run | Pages | Clean pages | Critical | Serious | Moderate | Minor |
|---|---|---|---|---|---|---|
| 2026-11-04 10:00 UTC | 190 | 184 | 0 | 56 | 0 | 0 |
| 2026-11-03 13:48 UTC | 116 | 111 | 2 | 56 | 0 | 0 |
| 2026-11-03 13:32 UTC | 116 | 106 | 2 | 39 | 0 | 0 |
| 2026-11-03 13:14 UTC | 116 | 87 | 2 | 87 | 0 | 0 |
Known limitations
- Automated tools find only part of what WCAG covers. Whether a text alternative is meaningful, or whether a complex widget makes sense with a screen reader, needs a person to judge.
- The nightly axe run uses one desktop window size (1280 x 900). Phone layouts are covered by the crawl and the visual tests, which do not check every WCAG rule.
- Maps on some pages are hard to use without a mouse or without sight. The data behind them is open: /data/bali-cases.json and the open data API.
Report a problem
If something on Kolaboro is hard or impossible for you to use, email [email protected] with the page address, what you were trying to do, and, if you like, the browser and assistive technology you use. We will reply and tell you what we will do about it. If you need a report or a document in another format, ask in the same email.
This statement was written on 5 November 2026. The results above are refreshed every day by our quality job from the latest nightly run.