Accessibility
What we are aiming at
WCAG 2.2 Level AA. We are not there, and this page says where we are not rather than claiming a conformance we have not measured. A statement that overclaims is worth less than no statement, because somebody relies on it.
Known barriers, as of today
Text below 11px appears in places, and there are surfaces where the type is smaller than it should be for a screen read in bright terminal light. The ranked board does not yet carry list semantics, so a screen reader announces it as loose text rather than as a set of options. Focus styling is inconsistent across components. Every one of these is a defect with a queue row, not a design decision.
Mobility, and a claim we have not earned
Our return-buffer estimate assumes a traveller who can walk the route it describes. We do not yet hold step-free routing or airport mobility-assistance times, which means the number is not correct for every traveller and we would rather say so than let it read as universal. Do not rely on our timings if you need assistance; add your airline's own assistance window on top.
What already works
The airport picker is a full keyboard combobox with proper listbox semantics. Reduced-motion preferences are respected throughout. Absence is stated in words rather than shown only as an empty space, so a missing number reads as missing rather than as zero.
Telling us about a barrier
Barrier reports go to a monitored inbox and are answered by a person, not filed. Say what you were trying to do and what stopped you. We will tell you whether it is fixable and when.
support@layover.ingApproved by the owner on 2026-08-21. Maintained by hand and honest as of the last deploy. It has not been through a formal accessibility audit and there is no VPAT; when there is, that will be said here rather than implied. Barrier reports are answered by a person.