Technical draft

Accessibility

What works on this site, what does not work yet and how to tell us. We prefer a short true list to a conformity badge nobody has audited.

Last updated: October 20, 2026

1. Status of this statement

This statement describes the real state of the accessibility of the product on the date shown at the top. It is not an audit report: we have not run a formal review with assistive technology users or with specialist tools, and that is why we do not claim to meet a specific level of the standard. We prefer saying it this way.

The goal of the product is to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. It is a goal, not a certification, and this page is where we will report what has been done and what is missing.

2. What already works

Keyboard navigation: the interface controls (buttons, links, fields and menus) are native browser elements, so they are reachable with the tab key and can be activated with the keyboard.
Visible focus: the focused element is clearly distinguished from the rest, so you always know where you are.
Accessible labels on controls without text (icons, menu buttons, day switches), with names a screen reader can read out.
Reduced motion preference: if your system asks for fewer animations, transitions and smooth scrolling are switched off.
Light and dark mode on the map: the map can switch theme from its own controls, and the focus outline stays visible in both.
Correct heading structure on the product pages, with a single main heading per page and a hierarchy of headings that lets you navigate by section.
Contrast between the letter colour and the background has been worked on in the main interface components.
The data tables on these legal pages have column headers and can be read with a screen reader instead of being an image or a block of text.

3. What is still unresolved

Being honest about this part is more useful than a badge. These are the points we know are not resolved yet:

The interactive map of the itinerary relies on gestures and a canvas. It has a text alternative with the list of places, but that alternative is still not as complete as the map.

The PDF export is generated on the server and does not carry the same accessibility labels as the web version.

The contrast of some secondary states (dimmed text, separator borders) is below the target on high-contrast backgrounds.

We have not tested the product with screen readers across every combination of browser and operating system, nor with users with visual, motor or cognitive disabilities.

The interface does not follow the system's colour scheme preference automatically: the map theme is changed by hand, and the rest of the interface is always the light theme.

The contrast of price text in some itineraries depends on the colour the data provider supplies.

4. How to report an accessibility problem

You can write to us at the support address listed in the legal notice. The more information the better: the exact page or flow, what you were trying to do, which browser and assistive technology you were using, and a screenshot if you are comfortable with that.

We commit to acknowledging receipt within two working days and to giving you an answer with the next step within five working days. If the fix takes longer than it should, we tell you and keep you updated on where it stands.

5. Technical reference

The technical reference for this product is the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, and the semantic HTML model the application uses. Every fix we make will be reflected on this page, with its date and its status.