Policies and disclosures
Product terms, privacy details, and operational disclosures that match how Tripanomics works today.
Tripanomics aims to meet WCAG 2.2 AA across the public site, authentication flows, itinerary generation, sharing, pricing, checkout return paths, settings, export, and deletion flows.
Tripanomics is working toward WCAG 2.2 AA and is currently best described as partially conformant. Some parts of the product have been audited and remediated, while other areas are still being reviewed and improved.
This statement applies to the Tripanomics website at https://tripanomics.com.
We are actively testing keyboard navigation, focus visibility, semantic labels, error messaging, responsive reflow, and reduced-motion behavior across core journeys.
Because Tripanomics includes generated and third-party travel content, itinerary text may include venue names, addresses, descriptions, or links supplied by external sources. We work to render that content through accessible product components, but we do not control the accessibility of third-party websites, venues, maps, booking flows, or external content.
Our current process includes internal manual review of core flows, keyboard testing, focused automated testing, and targeted follow-up after major UI changes.
The current public statement reflects a May 2026 internal review cycle. We aim to review this Accessibility Statement at least annually and after major changes to key user journeys.
Our current launch baseline includes a manual audit workstream that is still being refreshed across every core journey. If you find a barrier, we want the report even if the issue is already on our checklist.
Known limitations may include third-party map interactions, external booking or affiliate pages, third-party OAuth and checkout flows, and the accuracy or completeness of accessibility details supplied by venues or travel-data providers.
If you need assistance or want to report an accessibility issue, email support@tripanomics.com with:
If you cannot access a feature, we will do our best to provide the needed information or a reasonable alternative support path by email.
We aim to acknowledge accessibility reports within 5 business days and prioritize high-severity barriers before launch or in the next available fix window.