Accessibility statement

Our commitment

AirOrSeaTravel is built to conform with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Travel information is exactly the kind of content people need regardless of how they browse, and a page nobody can read is a page that has failed whatever it scores elsewhere.

This statement was last reviewed on 11 September 2026.

What has been done

• Keyboard. Every control — navigation, the menu button, the guide filters, the search box and the contact form — is reachable and operable by keyboard alone, in a logical order, with a visible focus ring that meets contrast requirements.
• Skip link. A “Skip to main content” link is the first thing in the tab order on every page.
• Colour contrast. Every text and background pair in the design was checked before it was used. Body text sits at 8.6:1 against white, headings at 15.4:1, and the primary button at 8.3:1 — all well above the 4.5:1 Level AA requirement.
• Text alternatives. Photographs carry descriptive alt text; purely decorative images carry empty alt text so screen readers skip them rather than announcing a filename.
• Headings and landmarks. One h1 per page, headings in order without skipped levels, and proper header, nav, main, aside and footer landmarks.
• Links. Every link has text that makes sense out of context. Links that open a new tab say so to screen reader users. There are no “click here” links and no links with no accessible name.
• Forms. Every field has a visible, associated label. Errors are announced with aria-invalid and tied to the field with aria-describedby, described in words rather than by colour alone.
• Zoom and reflow. Text scales to 200% and the layout reflows to a 320 px viewport without horizontal scrolling or loss of content.
• Motion. The site honours prefers-reduced-motion; there is no autoplaying media, no carousel and nothing that flashes.
• Tables. Comparison tables use proper header cells with scope, and captions that explain what is being compared.
• Without JavaScript. Every page is readable and navigable with scripting disabled.

Display and reading tools

Every page has a Display & reading tools panel in the footer. It is not a third-party accessibility overlay — those are widely criticised for fighting the assistive technology people already use, and this site does not load one. These are plain controls that change this site’s own stylesheet and nothing else:

• Text size — normal, large or largest. The whole layout scales with it, because the design is built in relative units.
• Higher contrast — removes soft greys and shadows and strengthens every border and body colour.
• Underline links — underlines every link and outlines every button, for anyone who cannot rely on colour alone.
• More text spacing — increases line height, letter, word and paragraph spacing, meeting the WCAG 1.4.12 text-spacing metrics.
• Reduce motion — switches off transitions and smooth scrolling. The site already honours your operating system’s reduced-motion setting; this is for when you want it here but not everywhere.

Your choices are saved in your browser’s local storage on that device, are applied before the page paints so nothing flickers, and are never transmitted to us. They are described on the cookies page.

These tools are an addition, not a substitute. The site is built to be usable with none of them switched on, and with your own browser zoom, stylesheet or screen reader instead.

How it has been tested

Two ways, and we are specific about this because “accessible” is easy to claim:

• Automated. Every page on the site is run through the axe-based accessibility audit in Lighthouse, and every page scores 100. Automated tools catch perhaps a third of real barriers, so this is a floor, not a result.
• Manual. Keyboard-only navigation of every page type, focus-order and focus-visibility checks, contrast measured numerically for every colour pair in the design system, and layout checked at 320 px and at 200% zoom.

Known limitations

Stating these is the point of a statement like this one:

• No independent audit. The site has not been assessed by a third-party accessibility specialist, and no conformance certification is claimed.
• No formal screen reader testing programme. The markup is built to the relevant standards and checked with automated tooling, but we have not run structured testing sessions with JAWS, NVDA or VoiceOver users.
• External websites. Provider and source links lead to sites we do not control. Their accessibility is their own.
• Photographs. Alt text describes what is in the image; it is not a full long description of a complex scene, because these images are illustrative rather than informational.

Tell us when something does not work

If any part of this site is difficult or impossible for you to use, we want to hear about it. Use the contact form and include the page address and what happened. You do not need to know the technical cause.

We aim to acknowledge accessibility reports within five working days and to tell you what we intend to do and roughly when. Access problems are treated as defects and fixed in the normal course of work, not queued as feature requests.

Formal complaints

If you are not satisfied with our response, you are entitled to raise the matter with the relevant authority for your jurisdiction — in the United States the Department of Justice Civil Rights Division, and in the European Union or United Kingdom the national body designated under the Web Accessibility Directive or the Equality Act.

Common questions

What standard does this site aim for?

WCAG 2.2 Level AA. That is the level referenced by the ADA in US Department of Justice guidance, by Section 508, and by EN 301 549 in Europe.

Has the site been audited by a third party?

No. Testing so far is our own: automated checks on every page plus manual keyboard and contrast testing. An independent audit has not been carried out, and we say so rather than imply a certification we do not hold.

What do I do if I cannot use part of the site?

Tell us through the contact form and describe the page and what went wrong. We treat access problems as bugs, not requests, and we will tell you what we are doing about it.

Is the accessibility menu an overlay widget?

No. Overlay widgets inject a parallel interface and frequently conflict with the screen reader or magnifier someone already uses. The Display & reading tools in the footer only toggle this site’s own stylesheet — no third-party script is loaded and nothing intercepts your assistive technology.

Does the site work without JavaScript?

Yes. Every page reads and navigates normally with JavaScript off. Only three things are enhanced by it: the mobile menu, the guide filter, and inline form validation — and each has a working fallback.

Are the external sites you link to accessible?

We cannot guarantee it. Once you follow a provider link you are on another company’s website, subject to their accessibility practices, which we do not control and cannot test on your behalf.