1. Our commitment
Kaia is built to be used by everyone, regardless of ability. As a two-sided marketplace, that commitment covers both sides: the traveler flows (searching, building an itinerary, booking, paying) and the operator panel (managing experiences, bookings, and payouts). Accessibility is an ongoing effort, not a finished state — and we treat it as part of building the product, not an afterthought.
2. The standard we aim for
We target WCAG 2.2 Level AA (the Web Content Accessibility Guidelines published by the W3C) as our conformance goal across the site.
Kaia is based in Costa Rica, where accessibility is protected by Law 7600 on Equal Opportunities for Persons with Disabilities and its regulations. Because we also serve international travelers, we align with the accessibility frameworks they rely on — the European Accessibility Act and its technical standard EN 301 549 for visitors from the EU, and the ADA and Section 508 for visitors from the United States.
3. What we've done so far
- Text and interface colors reviewed against the WCAG AA contrast minimums, with tertiary text corrected where it fell short.
- Alternative text on meaningful images and accessible names (aria-labels) on icon-only buttons.
- Labels tied to every form field, with clear, text-based error messages.
- Keyboard operability and visible focus states on interactive controls.
- Motion and animation gated behind prefers-reduced-motion: nothing essential depends on movement, and reduced-motion visitors get a fully static experience.
- Semantic structure (landmarks, headings) so screen readers can navigate the page.
- Bilingual interface (Spanish and English, with more languages), so content is available in the visitor's language.
4. Known limitations
Kaia is actively being built, and some areas are not yet fully conformant. Rich interactive surfaces — the itinerary builder and the animated marketing homepage — are still being hardened for assistive technology, and some third-party embeds (maps, payment fields) follow their providers' own accessibility roadmaps. We'd rather tell you this plainly than claim a level of conformance we haven't finished verifying.
5. Tell us about a barrier
If you hit an accessibility barrier anywhere on Kaia, we want to know — it's the fastest way for us to fix it. Write to accesibilidad@kaia.cr in Spanish or English with the page, what you were trying to do, and the assistive technology you use if relevant. We aim to respond promptly and to offer an alternative way to complete anything you couldn't.
6. Ongoing work
We review accessibility as we ship new features and revisit it regularly. This statement is updated as our conformance improves and as the standards evolve; the last-updated date appears at the top.