TRIP.COM ACCESSIBILITY STATEMENT
Trip.com is committed to providing a digital experience that is accessible to the widest possible audience, regardless of technology or ability. We are continuously working to improve the accessibility and usability of our website and mobile applications, guided by applicable standards and user feedback.
This statement applies to the Trip.com website and Trip.com mobile apps (iOS and Android) used within the European Union as well as the United Kingdom, Switzerland, Turkey and Ukraine.
Conformance Status
Trip.com substantially conforms to WCAG 2.1 Level AA and continues to work toward full conformance, in line with EN 301 549, the European accessibility standard applicable under the EU Web Accessibility Directive and European Accessibility Act.
Current Status & Progress
We have made significant progress in improving the accessibility of our digital platforms. Most of previously identified accessibility gaps have been successfully resolved across our website and mobile applications. Our technical teams have completed comprehensive remediation work on core user journeys, ensuring that essential booking functionality meets accessibility standards.
Recent accessibility improvements include enhanced color contrast across all interfaces, improved text scaling and responsive layout functionality, and strengthened screen reader compatibility for critical user flows, including search, booking selection, payment processing, and booking confirmation. Navigation structures have been simplified and tab order optimized to improve usability for keyboard-only users.
These improvements reflect our ongoing commitment to accessible design and demonstrate substantial progress toward full compliance with WCAG 2.1 Level AA standards.
Planned Enhancements
While the majority of accessibility work has been completed, we continue to refine specific aspects of our digital environment. Our development teams are addressing remaining technical items that have been identified as minor or having minimal impact on user experience. These include fine-tuning accessible focus states across certain interface elements and further optimizing form field validation and error messaging for screen reader users.
A smaller set of enhancements involving complex third-party integrations or legacy system dependencies remains scheduled for completion throughout 2026 as technical solutions become available.
Known Limitations
Despite our substantial progress, some minor limitations remain in our digital environment. Technical assessments have determined these to be of minimal impact on overall accessibility. Current limitations include certain legacy interface elements where minor enhancements to keyboard navigation or screen reader support are still in development, embedded third-party modules where accessibility may not be fully controllable by Trip.com, and specific combinations of older app versions or browser configurations where accessibility feature support may be limited.
We are actively monitoring and addressing these remaining items. Our technical teams regularly review known limitations and prioritize updates based on user impact and technical feasibility.
Supported Environments
The accessibility features of Trip.com are supported in the following environments:
Feedback and Contact
We welcome feedback on the accessibility of Trip.com. If you encounter an accessibility barrier or would like to report an issue, please contact us at GBEN_Accessibility@trip.com. We aim to respond within a reasonable timeframe and prioritise issues based on user impact.
Legal Disclaimers
This Accessibility Statement is published in accordance with the European Accessibility Act and relevant European accessibility standards, including EN 301 549 on the accessibility of the websites and mobile applications of public sector bodies, where voluntarily applicable to private platforms under best-practice standards and the European Accessibility Act (effective 28 June 2025).
While accessibility is continuously monitored and improved, some accessibility limitations may occur due to technical updates or third-party dependencies.
Date of Publication: July 10, 2025
Last Updated: June 10, 2026
Next Scheduled Review: 30 October 2026