Accessibility

Last updated 4 August 2026

We build this site to meet WCAG 2.1 Level AA. As a one-person operation we fall below the employee threshold at which Ontario's Accessibility for Ontarians with Disabilities Act makes that standard a legal requirement — we hold ourselves to it anyway, because travel information is useless to someone who cannot read it. If something here does not work for you, tell us and we will fix it and send you the information another way in the meantime.

What we have done

Keyboard access. Every interactive control can be reached and operated without a mouse. The booking dialog traps focus while open, returns focus to where you left it, and closes on Esc.
Screen readers. Pages use real landmarks (header, nav, main, footer), a single h1, headings in order, labelled form fields, and alt text on meaningful images. Decorative images are marked as decorative so they are skipped.
Contrast. Text meets the 4.5:1 minimum. We measured this rather than eyeballed it, and fixed four combinations that failed — white on coral was 2.59:1 — without changing the brand colours.
The airport autocomplete is a proper combobox: arrow keys move through options, Enter selects, Escape dismisses, and the option count is announced.
Zoom and reflow. Text scales to 200% and the layout reflows to narrow screens without a horizontal scrollbar. Wide tables scroll inside their own container instead of forcing the page sideways.
Motion. No auto-playing video, no flashing content, nothing that moves faster than you can read it.

What we know is not perfect yet

An accessibility statement that claims everything is fine is usually not worth reading. Known gaps, honestly:

The live flight-search widget on Compare is third-party software that we embed but do not control, so we cannot guarantee its accessibility. If it blocks you, contact us — we will look up the same flights and send you the results.
The map on Plan a trip is inherently visual. Every stop you add is also shown in a text list with its name, time and notes, and the whole itinerary can be copied as plain text — so the map is never the only way to get the information.
We have tested with keyboard navigation and automated checks. We have not yet run testing with users of assistive technology, which is the test that actually counts. We would rather say so than imply otherwise.

Getting content another way

You can ask for anything on this site in an accessible format or with communication support, and we will provide it in a timely way at no extra cost. If a page, table or comparison on this site is not usable for you, email privacy@looknbooks.com and say what you need — plain text, large print, or simply the answer written out — and we will send it.

Telling us about a problem

Email privacy@looknbooks.com. It helps if you can say which page, what you were trying to do, and what browser or assistive technology you use — but please do not let missing details stop you writing. We aim to reply within a few business days.

Feedback about accessibility is treated as a bug report, not a complaint.