Legal · Accessibility

Built accessible. by design.

Effective: March 26, 2026 · Last updated: September 29, 2026

Our Commitment

This accessibility statement is Trueleveler’s account of what works today, the problems it knows about, and how to report a barrier it has missed.

Short version: We build Trueleveler to work from the keyboard and with a screen reader, and it is not there yet. This page says what works, lists the problems we know about, and tells you how to report one we have missed. Fixes for the known problems are in progress.

Trueleveler believes that the internet should be accessible to all people, including those with disabilities, and we want the widest possible audience to be able to use it.

Our target is the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level. We have not been audited against it, and we do not claim conformance. These guidelines provide a framework for making web content more accessible to people with a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

Standards

Trueleveler targets conformance with WCAG 2.1 Level AA. WCAG 2.1 is the internationally recognised standard for web accessibility, developed by the World Wide Web Consortium (W3C). It defines how to make web content more accessible to people with disabilities.

The four core principles of WCAG require content to be:

Accessibility Features

We build in the following accessibility features. The gaps we know about are listed under Known Limitations.

Keyboard navigation

We build interactive elements — buttons, links, form controls, dialogs, and navigation menus — to work from the keyboard with Tab, Shift+Tab, Enter, Escape, and the arrow keys. A few parts don’t yet; they are listed under Known Limitations below.

ARIA labels and roles

We use WAI-ARIA (Web Accessibility Initiative — Accessible Rich Internet Applications) attributes to provide semantic meaning to dynamic content and custom interface components. This includes appropriate role, aria-label, aria-expanded, aria-live, and other ARIA attributes on interactive elements such as dropdown menus, modal dialogs, tab panels, and status notifications.

Colour contrast

We aim for WCAG 2.1 AA minimum contrast ratios (4.5:1 for normal text, 3:1 for large text and UI components), and we pair colour with text or icons to show status and meaning. The exceptions we know of are listed under Known Limitations below.

Screen reader support

We design for popular screen readers, including NVDA, JAWS, and VoiceOver, but we have not tested with all of them (see Assistive Technology Compatibility below). Semantic HTML elements (<nav>, <main>, <header>, <footer>, <section>) are used to provide document structure. Most form fields have a visible label and most images that carry meaning have alt text. Some changes, such as notifications, are announced through ARIA live regions; others are not yet, and some controls have no accessible name at all. Those gaps are listed under Known Limitations below.

Focus management

Interactive elements show a visible focus indicator. Our standard dialogs move focus into the dialog when they open, keep it there while they are open, and return it to the element that opened them when they close. Some older pop-ups in the app don’t do this yet (see Known Limitations).

Responsive design

The platform adapts to different screen sizes, orientations, and zoom levels. The public pages we have checked reflow at 320 pixels wide (the equivalent of 400% zoom) without horizontal scrolling; the app itself has not yet been checked at that size. Some buttons and links are smaller than the recommended 44 by 44 pixels (see Known Limitations).

Text and content

We design for text to be resizable up to 200% without loss of content or functionality; we have not tested every screen of the app at that size. We avoid using images of text. Link text is descriptive and meaningful out of context. Page titles and headings are descriptive and follow a logical hierarchy.

Assistive Technology Compatibility

We aim for Trueleveler to work with the following assistive technologies. We have not yet tested with each of them:

Automated accessibility checks (axe-core) run on our main public pages as part of our test suite. We have not yet completed a formal audit with each of the assistive technologies listed above.

Known Limitations

We do not yet meet WCAG 2.1 AA everywhere. These are the problems we know about:

Fixes for these are in progress. We have not set dates, and we will update this page as each one is fixed.

Feedback & Contact

We welcome your feedback on the accessibility of Trueleveler. If you encounter accessibility barriers, have suggestions for improvement, or need assistance using any part of our platform, please contact us:

We aim to respond to accessibility feedback within 3 business days. When reporting an issue, please include:

Voluntary Product Accessibility Template (VPAT)

A Voluntary Product Accessibility Template (VPAT) is a document that explains how information and communication technology (ICT) products conform to the Revised Section 508 Standards for IT accessibility. VPATs are commonly requested by government agencies and large enterprises during procurement.

VPAT status: We have not completed a VPAT yet, and we have not set a date for one. When one is published, it will be available for download on this page.

In the interim, if you require a VPAT or other accessibility documentation for procurement purposes, please contact support@trueleveler.com with the subject line "Accessibility Documentation Request" and we will provide the information you need to support your evaluation.

Enforcement

If you are not satisfied with our response to your accessibility concern, you may contact the relevant authority in your jurisdiction. In the United States, you may file a complaint with the U.S. Department of Justice. In the European Union, contact your national enforcement body under the European Accessibility Act or the Web Accessibility Directive.

This statement was last reviewed and updated on September 29, 2026.